512-frameworks-micronaut-data

Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc. This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, concise skill body with strong workflow validation and clean single-level progressive disclosure. Its weakest point is actionability: the workflow steps are somewhat abstract and lack in-body executable examples, relying on the reference for concrete code.

Suggestions

Add one small inline code snippet (e.g., a minimal @MappedEntity + CrudRepository pair) so the body demonstrates executable patterns rather than only pointing to the reference.

Tighten step 3 of the workflow from generic 'implement or refactor... following the reference patterns' to a concrete decision or action the model takes, even if briefly.

Dimension	Reasoning	Score
Conciseness	The body is lean: a short coverage list, terse constraints, and a single reference link, with no explanation of concepts Claude already knows. Each section earns its place, though the coverage list mildly echoes the description.	3 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify'), but the core workflow steps are abstract ('Implement or refactor configuration/code following the reference patterns and project conventions') with no executable code examples in the body — detail is delegated to the reference.	2 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced with explicit validation checkpoints — 'MANDATORY: Run ./mvnw compile', 'SAFETY: If compilation fails, stop immediately', 'VERIFY: Run ./mvnw clean verify' — forming a validate-then-act feedback loop.	3 / 3
Progressive Disclosure	A concise overview links to a single one-level-deep reference (references/512-frameworks-micronaut-data.md, which exists), clearly signaled and easy to navigate, with detail appropriately split out of the body.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that states concrete capabilities, explicit trigger phrasings, and clear routing to adjacent skills. It answers both what and when without padding or first/second-person voice.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and annotations: '@MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers' — concrete and comprehensive rather than vague.	3 / 3
Completeness	Both 'what' (data access with Micronaut Data, the listed annotations) and 'when' ('Use when you need data access with Micronaut Data', plus the explicit trigger examples) are clearly present.	3 / 3
Trigger Term Quality	Natural request phrasings are explicitly given — 'This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer' — matching what a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Micronaut Data niche is clearly scoped, and related cases are routed to sibling skills ('For raw java.sql access... use @511-frameworks-micronaut-jdbc'), reducing the chance of triggering the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 159e7ce

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.