Create Quarkus Maven Project
SkillDev toolsUse 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; Create Quarkus 3 Maven project; Scaffold Quarkus service with Java 25. Part of Plinth Toolkit
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Create Quarkus Maven Project skill
What this skill tells your AI
The instructions your AI receives, as published by jabrena/plinth in skills/400-frameworks-quarkus-create-project/SKILL.md and read by ahel’s review.
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 verifyfrom the generated project when the Maven wrapper exists; otherwise runmvn 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
- Create Quarkus 3 Maven project
- Scaffold Quarkus service with Java 25
Workflow
- 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.
- Verify SDKMAN-managed tooling
Check SDKMAN, Java, and Quarkus CLI availability. Install or switch candidates only after confirming the intended versions with the user.
- 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.
- 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.
Signals
- GitHub stars
- 439
- Forks
- 92
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
x-400-frameworks-quarkus-create-project- Source
- github.com/jabrena/plinth