500 frameworks micronaut create project
Skill jabrena/plinth/skills/500-frameworks-micronaut-create-project
Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.
npx -y skills add jabrena/plinth --skill 500-frameworks-micronaut-create-projectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.0 KB, as published. Nobody here has run it
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 verifyfrom the generated project when the Maven wrapper exists; otherwise runmvn 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
- 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.
- Verify SDKMAN-managed tooling
Check SDKMAN, Java, and Micronaut CLI availability. Install or switch candidates only after confirming the intended versions with the user.
- 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.
- 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.