You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add extension skills support and MCP server instructions
- SkillReader: reads extension skills from the aggregated
quarkus-extension-skills JAR instead of per-extension deployment JARs.
Auto-downloads from Maven repos if not in local .m2, respecting
mirrors from ~/.m2/settings.xml, ${MAVEN_HOME}/conf/settings.xml,
and .mvn/maven.config.
- Server instructions: configures quarkus.mcp.server.server-info.instructions
to direct AI agents to use quarkus-agent tools (skills, searchDocs,
callTool) over generic alternatives like Context7.
- CLAUDE.md generation: quarkus/create now generates a CLAUDE.md in every
new project with Quarkus-specific workflow rules, including running
tests via subagents for non-blocking test execution.
- DevMcpProxyTools: quarkus/skills tool updated to use the new
SkillReader that reads from the single aggregated JAR.
Depends on:
- quarkusio/quarkus#53195 (aggregate-skills mechanism)
- quarkusio/quarkus#53196 (extension skill files)
- quarkusio/quarkus#53182 (one-shot testing)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This is a Quarkus application. Follow these rules when working on this project.
292
+
293
+
## Required Workflow
294
+
295
+
1. **Use quarkus/update (via subagent) when returning to this project** — checks if the Quarkus version is up-to-date and suggests upgrades.
296
+
2. **Use quarkus/skills BEFORE writing any code or tests** — it contains extension-specific patterns, testing approaches, and common pitfalls that prevent mistakes.
297
+
3. **Use quarkus/searchDocs for Quarkus documentation** — do NOT use generic documentation tools (Context7, web search). The Quarkus doc search is version-aware and more accurate.
298
+
4. **Use quarkus/searchTools to discover Dev MCP tools** on the running app for testing, config changes, and extension management.
299
+
5. **Use quarkus/callTool to invoke Dev MCP tools** — run tests, add extensions, update configuration. Do NOT run Maven/Gradle commands manually.
300
+
6. **Hot reload is automatic** — the app recompiles when accessed. Do NOT restart the app after code changes.
301
+
302
+
## Rules
303
+
304
+
- NEVER implement features manually when a Quarkus extension exists — search for and add the right extension first.
305
+
- ALWAYS write tests for every feature — no exceptions.
306
+
- ALWAYS keep README.md updated with app description, features, endpoints, and Quarkus guide links.
307
+
- Use `@QuarkusTest` for integration tests — Dev Services auto-starts backing services (databases, messaging, etc.).
308
+
- Use `%dev.` and `%test.` profile prefixes for dev/test configuration — never hardcode connection URLs without a profile prefix.
309
+
310
+
## Testing
311
+
312
+
ALWAYS run tests using a **subagent** so the main conversation stays responsive:
313
+
314
+
```
315
+
Use the Agent tool to launch a subagent with this prompt:
316
+
"Run the Quarkus tests for project <projectDir> using quarkus/callTool
317
+
with toolName 'devui-testing_runTests'. Analyze the results and report
318
+
which tests passed, failed, or errored. If tests fail, include the
319
+
failure messages and suggest fixes."
320
+
```
321
+
322
+
- Use `devui-testing_runTests` to run all tests.
323
+
- Use `devui-testing_runTest` with arguments `{"className":"com.example.MyTest"}` to run a specific test class.
324
+
- Do NOT run Maven/Gradle test commands manually — the Dev MCP test tools handle compilation, hot reload, and result reporting.
325
+
- After fixing test failures, re-run tests with a subagent to verify the fix.
0 commit comments