Micronaut Standards

Plugin micronaut-standards from marketplace onelitefeather-claude-marketplace in OneLiteFeatherNET/onelitefeather-claude-marketplace. Commands read from the repo's manifest — 17 days ago.

Skills (14)

• configuration

  OneLiteFeather's convention for typed application configuration in a Micronaut REST API — one @ConfigurationProperties class per functional area in a dedicated config/ package, instead of ad-hoc properties scattered across the application entry point. Use this whenever a Micronaut backend needs a ne

• dependency-management

  OneLiteFeather's Gradle/Micronaut dependency-management conventions for REST API backends — the Micronaut Application and AOT plugins, reading the Micronaut version from gradle.properties instead of hardcoding it, the mn.* platform catalog, the private OneLiteFeather Maven repo, and the optional Cyc

• dto

  OneLiteFeather's request-DTO conventions for Micronaut REST APIs — records with @Serdeable/@Introspected, one shared Create/Update DTO controlled by JSR-380 validation groups instead of separate DTO types per action, and entity conversion methods living on the DTO itself. Use this whenever adding a

• entity-design

  OneLiteFeather's JPA/Micronaut Data entity conventions for Micronaut REST APIs — entities as a pure persistence layer with no Bean Validation annotations, the internal-UUID-vs-external-identifier pattern, custom AttributeConverters for complex column types, and why entities are plain Java beans rath

• exception-handling

  OneLiteFeather's global exception-handling convention for Micronaut REST APIs — exactly one org-wide ExceptionHandlerAdvice that maps exception types to the correct HTTP status code and returns the shared ErrorResponse type from response-modeling, plus dedicated domain exception classes instead of g

• liquibase

  OneLiteFeather's mandatory Liquibase database-migration convention for Micronaut REST APIs — always XML changelogs (never YAML/SQL/JSON), the master-changelog-plus-versioned-files structure, and why this replaces Hibernate's hbm2ddl.auto=update. Use this whenever a Micronaut backend needs a schema c

• logging

  OneLiteFeather's logging conventions for Micronaut REST APIs — one SLF4J logger per class with no exceptions, structured JSON logging with OpenTelemetry trace/span correlation, log-level guidelines, and what must never be logged (PII, secrets, full request bodies). Use this whenever adding a new cla

• observability

  Metrics and tracing infrastructure for a OneLiteFeather Micronaut REST API — Micrometer with Prometheus, OpenTelemetry tracing for HTTP and JDBC, and Kubernetes service discovery (inert outside a cluster). Use this whenever wiring up metrics/tracing dependencies or the /metrics endpoint in a Microna

• openapi

  OneLiteFeather's OpenAPI documentation convention for Micronaut REST APIs — a doc-only *Api interface per controller carrying @Operation/@ApiResponse (never routing annotations), operationId/tags naming, @ApiResponse schemas referencing the response-modeling skill's success/error records, and enabli

• response-modeling

  OneLiteFeather's sealed-interface response-DTO pattern for Micronaut REST APIs — a per-resource sealed interface with a success record and an error record, both implementing a shared org-wide ErrorResponse marker interface, plus static createDTO(entity) factory methods for entity-to-DTO conversion.

• routing

  OneLiteFeather's HTTP routing conventions for Micronaut REST API controllers — resource-based paths with real HTTP verbs instead of action URLs, blocking HttpResponse<T> as the standard return type, and the Pageable/Page pagination convention. Use this whenever adding a new endpoint or reviewing a c

• security

  OneLiteFeather's Micronaut Security baseline for REST APIs — deny-by-default access control with explicit per-endpoint @Secured annotations. Use this whenever adding a new controller endpoint and deciding who is allowed to call it, or when reviewing an existing endpoint that has no @Secured annotati

• service-layer

  OneLiteFeather's mandatory service-layer convention for Micronaut REST APIs — a service interface plus a service/impl implementation package, constructor injection only, business logic kept out of controllers. Use this whenever adding a new resource/feature to a Micronaut backend and deciding where

• testcontainers

  OneLiteFeather's mandatory Testcontainers integration-test convention for Micronaut REST APIs — MariaDB and PostgreSQL containers via micronaut-test-resources, JUnit 5 lifecycle conventions, and the boundary between unit tests (no container) and integration tests (container required). Use this whene

Similar plugins