mcpField
4
400-frameworks-quarkus-create-project

400-frameworks-quarkus-create-project

github.com/jabrenaDevelopment456199 installsUpdated 1d ago
Repository

About 400-frameworks-quarkus-create-project

A skill that scaffolds Quarkus Maven projects using SDKMAN-managed tooling. It gathers project settings, creates the project with the Quarkus CLI, and verifies the result with Maven.

Key features

  1. 01Check SDKMAN and Java availability
  2. 02Select Java and Quarkus CLI versions
  3. 03Gather project coordinates and extensions
  4. 04Generate a Quarkus Maven project
  5. 05Verify with Maven

Use cases

  1. 01Bootstrap a new Quarkus service
  2. 02Create a Quarkus 3 Maven project
  3. 03Set up a Java 25 project scaffold

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jabrena/plinth --skill 400-frameworks-quarkus-create-project

After installing, type/400-frameworks-quarkus-create-projectin Claude Code to confirm it loaded.

Bundled filesreferences/400-frameworks-quarkus-create-project.md

Details

From the project README

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.

  1. Verify SDKMAN-managed tooling

Check SDKMAN, Java, and Quarkus CLI availability. Install or switch candidates only after confirming the intended versions with the user.

  1. 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.

  1. 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.

Comments

Markdown supported