- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jdubois/boot-ui --skill bootui-java-development -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jdubois/boot-ui --skill bootui-java-development -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jdubois/boot-ui --skill bootui-java-development -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jdubois/boot-ui --skill bootui-java-development -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/jdubois/boot-ui/tree/HEAD/.github/skills/bootui-java-developmentDo publicador
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.mdVisão geral
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.
Perguntas frequentes
Baixe .github/skills/bootui-java-development/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/jdubois/boot-ui.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.