503-frameworks-micronaut-validation — Claude Code skill
503-frameworks-micronaut-validation guides validation setup in Micronaut applications, from Bean Validation annotations to HTTP 400 error payloads.
Apache-2.0 280 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a claude-codeWhat 503-frameworks-micronaut-validation does
This skill establishes clear standards for validating payloads at HTTP boundaries in Micronaut. It details Bean Validation annotations on DTOs, controller method arguments using @Valid or @Validated, nested models, and @ConfigurationProperties classes.
The workflow enforces verification safety guards around Maven tasks. It requires running ./mvnw compile or mvn compile before any edits. If compilation fails, the agent stops immediately without touching the code. Once changes are in place, the instructions dictate running ./mvnw clean verify.
Guidance relies directly on references/503-frameworks-micronaut-validation.md. The agent expects reference examples to be present within the repository context to align with patterns.
What it helps with
- configure Bean Validation on Micronaut controllers and nested DTOs
- validate configuration settings inside @ConfigurationProperties
- build custom validation constraints and validation groups
- standardize constraint violation mapping into safe HTTP 400 responses
Example prompts for the agent
- Review Micronaut validation rules across our REST controllers
- Add custom validation constraints for nested DTOs in Micronaut
- Improve constraint violation handling to return clean 400 responses
How to install 503-frameworks-micronaut-validation
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a claude-code2Manually: put the files in place
~/.claude/skills/503-frameworks-micronaut-validation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/503-frameworks-micronaut-validation/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a codex2Manually: put the files in place
.agents/skills/503-frameworks-micronaut-validation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a cursor2Manually: put the files in place
.cursor/skills/503-frameworks-micronaut-validation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/503-frameworks-micronaut-validation2Manually: put the files in place
.github/skills/503-frameworks-micronaut-validation/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/503-frameworks-micronaut-validationManually: put the files in place
.devin/skills/503-frameworks-micronaut-validation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 503-frameworks-micronaut-validation
How to install 503-frameworks-micronaut-validation in Claude Code?
Run npx skills add jabrena/plinth --skill 503-frameworks-micronaut-validation -a claude-code in your terminal.
What does 503-frameworks-micronaut-validation do?
It guides the agent through designing, reviewing, and applying Bean Validation patterns and exception handling in Micronaut REST services.
What build checks does the skill require?
The workflow mandates ./mvnw compile before applying edits and ./mvnw clean verify immediately after.
Source text
SKILL.md · Apache-2.0
--- name: 503-frameworks-micronaut-validation description: Use when you need to design, review, or improve validation in Micronaut applications — including Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and ExceptionHandler mapping for constraint violations. This should trigger for requests such as Add validation support in Micronaut; Review Micronaut validation rules; Improve request validation in Micronaut REST APIs; Add custom validation constraints in Micronaut; Validate Micronaut configuration properties. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Micronaut Validation Guidelines Apply Micronaut validation best practices at HTTP API boundaries. **What is covered in this Skill?** - Bean Validation annotations on DTOs and command models - @Valid / @Validated usage in Micronaut controllers - Validation groups and custom validators - Consistent mapping of validation failures to 400 responses - Safe and predictable validation error payloads **Scope:** Apply recommendations based on the reference rules and good/bad examples. ## Constraints Before applying validation changes, ensure the project compiles. After improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and examples ## When to use this skill - Add validation support in Micronaut - Review Micronaut validation rules - Improve request validation in Micronaut REST APIs - Add custom validation constraints in Micronaut - Validate Micronaut configuration properties - Improve constraint violation handling in Micronaut ## Workflow 1. **Read reference and assess project context** Read `references/503-frameworks-micronaut-validation.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor validation-related configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/503-frameworks-micronaut-validation.md](references/503-frameworks-micronaut-validation.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth