400-frameworks-quarkus-create-project
This Claude Code skill creates a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI tooling. Use it when bootstrapping a Quarkus service with explicit project coordinates, extensions, and Java version selection, with built-in verification through Maven wrapper commands to ensure reproducible project generation.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/400-frameworks-quarkus-create-project && cp -r /tmp/400-frameworks-quarkus-create-project/skills/400-frameworks-quarkus-create-project ~/.claude/skills/400-frameworks-quarkus-create-projectSKILL.md
# Create Quarkus Maven Project Create a new Quarkus Maven project through SDKMAN-managed tooling, aligned with Java 25 and the repository's Quarkus 3.x baseline. **What is covered in this Skill?** - Verify SDKMAN and Java availability before project creation - Install or select the required Java and Quarkus CLI candidates through SDKMAN - Gather project coordinates, package name, Java version, extensions, and target directory - Create a Maven project with the Quarkus CLI - Prefer Maven wrapper commands for validation - Verify the generated project with Maven before reporting completion ## Constraints Project creation must be explicit, reproducible, and Maven-based. - **PREREQUISITE**: Verify SDKMAN is installed with `sdk version`; if missing, stop and provide setup guidance instead of installing it silently - **JAVA BASELINE**: Prefer Java 25 unless the user requests another supported version - **FRAMEWORK BASELINE**: Target the current Quarkus 3.x line by default - **BUILD TOOL**: Generate a Maven project, not Gradle - **SAFETY**: Do not overwrite an existing non-empty target directory without explicit user confirmation - **VERIFY**: Run `./mvnw clean verify` from the generated project when the Maven wrapper exists; otherwise run `mvn clean verify` - **BEFORE APPLYING**: Read the reference for the full SDKMAN and Quarkus CLI workflow ## When to use this skill - Create a Quarkus Maven project - Bootstrap Quarkus project with SDKMAN - Generate a new Quarkus service ## Workflow 1. **Read reference and gather project inputs** Read `references/400-frameworks-quarkus-create-project.md`, then gather project directory, group, artifact, package name, Java version, and desired Quarkus extensions. 2. **Verify SDKMAN-managed tooling** Check SDKMAN, Java, and Quarkus CLI availability. Install or switch candidates only after confirming the intended versions with the user. 3. **Create the Maven project** Use the Quarkus CLI to create a Maven project, keeping extensions explicit and the Quarkus 3.x baseline as the default. 4. **Verify and report** Run Maven verification in the generated project and summarize commands used, selected options, generated path, and any follow-up setup. ## Reference For detailed guidance, examples, and constraints, see [references/400-frameworks-quarkus-create-project.md](references/400-frameworks-quarkus-create-project.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project