Skip to main content
skill CX Codex

500-frameworks-micronaut-create-project — Claude Code skill

The 500-frameworks-micronaut-create-project skill scaffolds a Micronaut 4.x Maven project with SDKMAN-managed tools and checks the generated build. Use it when starting a Micronaut service.

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

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

What 500-frameworks-micronaut-create-project does

The skill checks SDKMAN, Java, and Micronaut CLI, then gathers the project directory, Maven coordinates, package name, Java version, application type, and requested Micronaut features. Once the intended tool versions are confirmed, it creates the project with Micronaut CLI. Gradle is not an option here; the generated project uses Maven.

Java 25 and the current Micronaut 4.x line are the defaults. You can request another supported Java version. SDKMAN must already be installed: if sdk version fails, the skill stops and provides setup guidance rather than installing it silently. It also reads references/500-frameworks-micronaut-create-project.md before starting.

After generation, the skill runs ./mvnw clean verify when the Maven wrapper exists, or mvn clean verify otherwise. It won’t overwrite a non-empty target directory without explicit confirmation. Its completion report includes the selected options, commands, and project path.

What it helps with

  • scaffold a Micronaut 4.x Maven project
  • set up a service with Micronaut CLI
  • check SDKMAN and Java before project generation
  • verify a generated project with Maven

Example prompts for the agent

  • Create a Micronaut Maven project in orders-service and verify the build.
  • Set up a Micronaut service with Java 25 and the features I specify.
  • Check SDKMAN, then generate a Maven project for package com.example.service.

How to install 500-frameworks-micronaut-create-project

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 500-frameworks-micronaut-create-project -a claude-code

2Manually: put the files in place

~/.claude/skills/500-frameworks-micronaut-create-project/SKILL.md

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

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

Questions about 500-frameworks-micronaut-create-project

How do I install 500-frameworks-micronaut-create-project in Claude Code?

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

What does 500-frameworks-micronaut-create-project do?

It gathers project settings, checks SDKMAN and the Java and Micronaut CLI tools, creates a Maven project, and verifies the build.

Does the skill install SDKMAN if it is missing?

No. It checks sdk version first and stops with setup guidance if SDKMAN is unavailable.

Source text

SKILL.md · Apache-2.0
---
name: 500-frameworks-micronaut-create-project
description: Use when you need to create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling. This should trigger for requests such as Create a Micronaut Maven project; Bootstrap Micronaut project with SDKMAN; Generate a new Micronaut service; Create Micronaut 4 Maven project; Scaffold Micronaut service with Java 25. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Create Micronaut Maven Project

Create a new Micronaut Maven project through SDKMAN-managed tooling, aligned with Java 25 and the repository's Micronaut 4.x baseline.

**What is covered in this Skill?**

- Verify SDKMAN and Java availability before project creation
- Install or select the required Java and Micronaut CLI candidates through SDKMAN
- Gather project coordinates, package name, Java version, features, and target directory
- Create a Maven project with the Micronaut 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 Micronaut 4.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 Micronaut CLI workflow

## When to use this skill

- Create a Micronaut Maven project
- Bootstrap Micronaut project with SDKMAN
- Generate a new Micronaut service
- Create Micronaut 4 Maven project
- Scaffold Micronaut service with Java 25

## Workflow

1. **Read reference and gather project inputs**

Read `references/500-frameworks-micronaut-create-project.md`, then gather project directory, group, artifact, package name, Java version, application type, and desired Micronaut features.

2. **Verify SDKMAN-managed tooling**

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

3. **Create the Maven project**

Use the Micronaut CLI to create a Maven project, keeping features explicit and the Micronaut 4.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/500-frameworks-micronaut-create-project.md](references/500-frameworks-micronaut-create-project.md).

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

Similar skills

SKILL.md skills catalog →

From the same set123

The whole set →
416-frameworks-quarkus-mongodb-migrations-mongock 416-frameworks-quarkus-mongodb-migrations-mongock — a skill for setting up and verifying MongoDB migrations in Quarkus via Mongock. Adds @ChangeUnit classes, configures the quarkus-mongock extension, and validates migration order. CX Codex +1 212installs 801-regulations-eu-ai-act 801-regulations-eu-ai-act helps Java teams apply EU AI Act engineering controls to enterprise applications using LLMs, RAG, and AI agents before production deployment. CX Codex +1 212installs 805-regulations-eu-cyber-resilience-act The 805-regulations-eu-cyber-resilience-act skill reviews Java products and related components for engineering work tied to the EU Cyber Resilience Act. Use it when assessing a change or preparing a release. CX Codex +1 212installs 806-regulations-eu-data-act 806-regulations-eu-data-act is a Claude Code skill that checks Java services, APIs, and pipelines for EU Data Act controls before a data-sharing feature ships. CX Codex +1 212installs 054-design-tdd 054-design-tdd — a skill that walks Java developers through red-green-refactor cycles with test-driven development. Write a failing test first, implement just enough code to pass, then refactor while tests stay green. CX Codex +1 177installs 707-technologies-hexagonal-architecture 707-technologies-hexagonal-architecture is a Claude Code skill that reviews and improves Hexagonal architecture boundaries in Java projects without coupling to Spring Boot, Quarkus, or Micronaut. CX Codex +1 174installs 056-design-avoid-breaking-changes 056-design-avoid-breaking-changes reviews plans, OpenSpec changes, and APIs for breaking changes and migration risks before release. CX Codex +1 172installs 055-design-parallel-change The 055-design-parallel-change skill guides you through designing safe database schema changes when old and new application versions must run simultaneously. It breaks complex migrations into three separately deployable phases. CX Codex +1 172installs

Project sponsors

Companies that keep this analytics open