Use when you need to create a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI tooling. This should trigger for requests such as Create a Quarkus Maven project; Bootstrap Quarkus project with SDKMAN; Generate a new Quarkus service. Part of cursor-rules-java project
56
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/400-frameworks-quarkus-create-project/SKILL.mdCreate 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?
Project creation must be explicit, reproducible, and Maven-based.
sdk version; if missing, stop and provide setup guidance instead of installing it silently./mvnw clean verify from the generated project when the Maven wrapper exists; otherwise run mvn clean verifyRead references/400-frameworks-quarkus-create-project.md, then gather project directory, group, artifact, package name, Java version, and desired Quarkus extensions.
Check SDKMAN, Java, and Quarkus CLI availability. Install or switch candidates only after confirming the intended versions with the user.
Use the Quarkus CLI to create a Maven project, keeping extensions explicit and the Quarkus 3.x baseline as the default.
Run Maven verification in the generated project and summarize commands used, selected options, generated path, and any follow-up setup.
For detailed guidance, examples, and constraints, see references/400-frameworks-quarkus-create-project.md.
b73c9d3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.