Skip to main content
skill CX Codex

400-frameworks-quarkus-create-project — Claude Code skill

400-frameworks-quarkus-create-project creates a Quarkus 3.x Maven project with the Quarkus CLI and SDKMAN-managed tools. Use it to scaffold a service with chosen coordinates and extensions.

Apache-2.0 215 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 400-frameworks-quarkus-create-project -a claude-code
Open on GitHub

What 400-frameworks-quarkus-create-project does

The skill checks SDKMAN, Java, and the Quarkus CLI, then collects the project directory, group, artifact, package name, Java version, and requested extensions. It generates a Maven project through the Quarkus CLI. Java 25 and the current Quarkus 3.x line are the defaults, and validation uses Maven wrapper commands when available.

SDKMAN must already be installed: the skill checks with sdk version and stops with setup guidance if the check fails. It only installs or switches Java and Quarkus CLI versions after the user confirms the intended versions. An existing non-empty target directory requires explicit approval before it can be overwritten. Once the project is generated, the skill runs ./mvnw clean verify, or mvn clean verify when there is no Maven wrapper.

What it helps with

  • scaffold a Quarkus 3.x Maven project
  • create a service with selected Quarkus extensions
  • check Java and Quarkus CLI before project generation
  • verify a generated project with Maven

Example prompts for the agent

  • Create a Quarkus 3.x Maven project in orders-api using Java 25.
  • Set up a Quarkus service with the group, artifact, and extensions I specify.
  • Check SDKMAN, generate the Quarkus project, and run Maven verification.

How to install 400-frameworks-quarkus-create-project

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 400-frameworks-quarkus-create-project -a claude-code

2Manually: put the files in place

~/.claude/skills/400-frameworks-quarkus-create-project/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/400-frameworks-quarkus-create-project/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 400-frameworks-quarkus-create-project

How do I install 400-frameworks-quarkus-create-project in Claude Code?

Run npx skills add jabrena/plinth --skill 400-frameworks-quarkus-create-project -a claude-code. The skill file is placed at ~/.claude/skills/400-frameworks-quarkus-create-project/SKILL.md.

What does 400-frameworks-quarkus-create-project do?

It gathers project settings, checks SDKMAN, Java, and the Quarkus CLI, then creates a Maven project and runs build verification.

Does the skill require SDKMAN?

Yes. It checks SDKMAN with sdk version; if the check fails, it stops and gives setup guidance rather than installing SDKMAN itself.

Source text

SKILL.md · Apache-2.0
---
name: 400-frameworks-quarkus-create-project
description: 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; Create Quarkus 3 Maven project; Scaffold Quarkus service with Java 25. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# 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
- Create Quarkus 3 Maven project
- Scaffold Quarkus service with Java 25

## 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).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Backend and APIs →

From the same set123

The whole set →
005-agents-installation The 005-agents-installation skill copies the project’s embedded agent definitions into a directory you choose. Use it to set up .claude/agents or another supported destination. CX Codex +1 219installs 705-technologies-nosql-mongodb 705-technologies-nosql-mongodb — a skill for Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI that covers MongoDB at the database layer, independent of Spring Boot, Quarkus or Micronaut. CX Codex +1 216installs 807-regulations-eu-digital-services-act 807-regulations-eu-digital-services-act reviews Java systems for Digital Services Act engineering controls across moderation, complaints, recommendations, advertising, and transparency. CX Codex +1 215installs 316-frameworks-spring-mongodb-migrations-mongock 316-frameworks-spring-mongodb-migrations-mongock is a Claude Code skill for adding and reviewing Mongock migrations in Spring Boot. It activates for MongoDB migration setup and reviews. CX Codex +1 215installs 804-regulations-eu-nis2 804-regulations-eu-nis2 reviews Java applications for NIS2 cybersecurity risk-management controls in essential entities, critical-sector services, and managed providers. Works from sanitized evidence inventory only. CX Codex +1 215installs 808-regulations-eu-digital-markets-act 808-regulations-eu-digital-markets-act guides engineering reviews of Java systems subject to EU Digital Markets Act gatekeeper rules. CX Codex +1 213installs 802-regulations-dora 802-regulations-dora is a Claude Code skill that checks Java systems for DORA operational resilience readiness, including incidents, backups, continuity, and third-party ICT risk. CX Codex +1 213installs 803-regulations-gdpr 803-regulations-gdpr inspects Java enterprise backends for GDPR technical requirements and guides engineers on privacy controls prior to production. CX Codex +1 213installs

Project sponsors

Companies that keep this analytics open