Claude Skills for Quarkus
Overview
Use this skill when a Java repository needs Quarkus and domain-driven design guidance from jeremyrdavis/claude-skills-for-quarkus. The upstream project focuses on building Quarkus applications with DDD-oriented agent support.
Compatibility: Quarkus, Java, domain-driven design, Maven, REST services, and modernization workflows.
Workflow
- Identify the Quarkus version, Java version, extension set, persistence layer, and runtime target.
- Map the domain model before generating resources, services, repositories, or adapters.
- Keep Quarkus idioms intact: configuration, CDI, REST endpoints, Panache or repository patterns, and test profiles.
- For modernization, define the source framework and target Quarkus boundary before conversion.
- Validate with the repository's Maven or Gradle commands and Quarkus tests.
Guardrails
- Do not flatten domain boundaries into CRUD-only services unless the project already follows that style.
- Preserve API contracts, database migrations, and configuration property semantics.
- Check the upstream README before reusing Quarkus-specific instructions because supported patterns may change.
- Keep native-image assumptions separate from standard JVM runtime behavior.
Expected Output
Return a Quarkus-focused plan or implementation with domain boundaries, affected files, validation commands, and migration risks.
1---2name: claude-skills-for-quarkus3description: Use Claude skills for Quarkus to build domain-driven Quarkus applications and Java modernization workflows.4license: MIT5---67# Claude Skills for Quarkus89## Overview1011Use this skill when a Java repository needs Quarkus and domain-driven design guidance from [jeremyrdavis/claude-skills-for-quarkus](https://github.com/jeremyrdavis/claude-skills-for-quarkus). The upstream project focuses on building Quarkus applications with DDD-oriented agent support.1213Compatibility: Quarkus, Java, domain-driven design, Maven, REST services, and modernization workflows.1415## Workflow16171. Identify the Quarkus version, Java version, extension set, persistence layer, and runtime target.182. Map the domain model before generating resources, services, repositories, or adapters.193. Keep Quarkus idioms intact: configuration, CDI, REST endpoints, Panache or repository patterns, and test profiles.204. For modernization, define the source framework and target Quarkus boundary before conversion.215. Validate with the repository's Maven or Gradle commands and Quarkus tests.2223## Guardrails2425- Do not flatten domain boundaries into CRUD-only services unless the project already follows that style.26- Preserve API contracts, database migrations, and configuration property semantics.27- Check the upstream README before reusing Quarkus-specific instructions because supported patterns may change.28- Keep native-image assumptions separate from standard JVM runtime behavior.2930## Expected Output3132Return a Quarkus-focused plan or implementation with domain boundaries, affected files, validation commands, and migration risks.
autohandai