mcpField
5
502-frameworks-micronaut-rest

502-frameworks-micronaut-rest

github.com/jabrenaDevelopment456306 installsUpdated 1d ago
Repository

About 502-frameworks-micronaut-rest

A coding skill for designing and improving REST APIs in Micronaut HTTP applications. It covers endpoint semantics, validation, errors, pagination, and API contracts, with compile-first and post-change verification requirements.

Key features

  1. 01HTTP methods and response status design
  2. 02Request validation and centralized errors
  3. 03Pagination and OpenAPI contract guidance
  4. 04Security, caching, and versioning patterns
  5. 05Compile-first changes and full verification

Use cases

  1. 01Review Micronaut REST controllers and DTOs
  2. 02Add request validation or error handling
  3. 03Align pagination and APIs with OpenAPI

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jabrena/plinth --skill 502-frameworks-micronaut-rest

After installing, type/502-frameworks-micronaut-restin Claude Code to confirm it loaded.

Bundled filesreferences/502-frameworks-micronaut-rest.md

Details

From the project README

Micronaut REST API Guidelines

Apply REST design principles for Micronaut HTTP applications.

What is covered in this Skill?

  • Semantic HTTP with @Get/@Post/@Put/@Patch/@Delete and HttpResponse status control
  • Resource-oriented paths and stable DTO contracts
  • @Valid on request bodies with Bean Validation
  • Centralized error mapping (ExceptionHandler / problem JSON when applicable)
  • Pagination with Pageable and bounded sizes
  • OpenAPI contract file (API-first) and OpenAPI Generator for server stubs
  • Security annotations (@Secured) on sensitive routes
  • Idempotency-Key for retried writes
  • ETag / If-Match for optimistic concurrency
  • Cache-Control discipline
  • API versioning patterns
  • ISO-8601 time types in DTOs

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Compile before REST refactors; verify after.

  • 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
  • EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
  • EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

When to use this skill

  • Review or improve Micronaut @Controller REST APIs
  • Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer
  • Design Micronaut controllers and DTO validation
  • Add Micronaut exception handlers and Problem Details responses
  • Improve pagination filtering or OpenAPI alignment in Micronaut APIs

Workflow

  1. Read reference and assess project context

Read references/502-frameworks-micronaut-rest.md and inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

  1. 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/502-frameworks-micronaut-rest.md.

Comments

Markdown supported