- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jdubois/boot-ui --skill bootui-java-development -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jdubois/boot-ui --skill bootui-java-development -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jdubois/boot-ui --skill bootui-java-development -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jdubois/boot-ui --skill bootui-java-development -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/jdubois/boot-ui/tree/HEAD/.github/skills/bootui-java-development게시자 제공
Use this skill for substantive Java maintenance in this repository. It provides an investigation and implementation workflow, not a replacement for repository instructions or a requirement to delegate work.
Follow repository instructions and the relevant path-scoped instructions. Consult the module map when locating ownership. Build and delivery requirements remain authoritative in CONTRIBUTING.md and, when selected, the vertical-PR agent.
This skill develops BootUI itself. The separate consumer skill teaches agents to install and use BootUI in another application. Dr JSkill's application-creation workflow is not required here.
Read the request, working-tree changes, relevant implementation, and nearby tests before editing. Identify:
For a simple lookup or local edit, use direct tools. For a larger task, delegate only independent scopes with explicit file ownership and acceptance boundaries. Tell Java subagents to load this skill; avoid concurrent Maven builds in the same worktree. Loading it does not authorize committing, publishing, or spawning additional sessions.
Find the file using a known path or a narrow glob. Read the implementation and its tests together, then trace the relevant call chain. Search for an existing helper or SPI before adding one.
Use Java LSP when it answers a semantic question:
Use the actual symbol position in the current file, not a guessed or pre-edit line number. Before relying on cross-module results, compare them with one known declaration or caller. An empty workspace search or references limited to the declaration's file do not establish absence. If results are suspect, use a narrow glob/text search across the expected modules and inspect the matching code. Do not repeatedly retry the same query or install a new language server as part of an unrelated fix.
LSP is an aid, not a gate: continue with targeted searches when it is unavailable. A successful tool call or symbol outline proves neither complete indexing nor compilation. Semantic renames also require checking string-based registrations, resources, configuration keys, and public contracts that LSP cannot safely rename.
Load only the relevant section of change recipes:
Keep the regression case close to the behavior's owner. Prefer deterministic fixtures, fake providers, and controlled clocks to real network calls, host-dependent observations, sleeps, or an entire application context for pure logic. Exercise the failure and absence paths as well as the positive case. Wire every affected adapter; do not compensate for a missing binding with a silent fallback.
Load validation and debugging before choosing Maven commands. Start with the smallest relevant selection, then satisfy the required integration and delivery gates. Inspect reports to confirm that the intended tests and framework augmentation actually ran.
When a run fails, classify the first actionable failure before editing: dependency resolution, compilation, framework bootstrap, assertion failure, or environment limitation. Preserve its diagnostic and reproduce it at the smallest useful scope. Do not respond to each failure with another full build or unrelated source changes.
Review the final diff against the acceptance boundary and report any remaining blocker honestly. Do not claim compilation, cross-stack compatibility, or absence safety from an LSP response or a skipped test run.
Use when implementing, debugging, refactoring, or testing existing BootUI Java code, including framework-neutral engine logic, Spring MVC and WebFlux adapters, Quarkus runtime and deployment integrati
---name: bootui-java-developmentdescription: Use when implementing, debugging, refactoring, or testing existing BootUI Java code, including…---# .github/skills/bootui-java-development/SKILL.md개요
Use when implementing, debugging, refactoring, or testing existing BootUI Java code, including framework-neutral engine logic, Spring MVC and WebFlux adapters, Quarkus runtime and deployment integration, optional dependencies, DTO contracts, and Maven build failures. Not for frontend-only work, creating unrelated applications, or release operations.
FAQ
게시자에게서 .github/skills/bootui-java-development/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/jdubois/boot-ui에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.