521-frameworks-micronaut-testing-unit-tests

Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests. 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 overview skill with strong workflow validation checkpoints and clean one-level progressive disclosure; its single weakness is that executable test-code examples live only in the reference, leaving the body's actionability incomplete.

Suggestions

Include one minimal copy-paste-ready test snippet in the body (e.g. a Mockito-first @ExtendWith example) so the skill is actionable before the reference is opened.

Consider a one-line 'good vs bad' example contrasting @MicronautTest overuse with a Mockito-first test to anchor the 'Reduce unnecessary @MicronautTest usage' trigger.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: terse structured lists and bullet constraints with no explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Provides concrete, executable commands (./mvnw compile, mvn clean verify) and names specific patterns, but the actual copy-paste-ready test code examples are deferred to the reference file rather than appearing in the body.	2 / 3
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints and an error-recovery feedback loop: MANDATORY compile before changes, 'If compilation fails, stop immediately', and VERIFY with mvn clean verify afterward.	3 / 3
Progressive Disclosure	A concise overview that points to a single one-level-deep, clearly signaled reference (references/521-frameworks-micronaut-testing-unit-tests.md, verified to exist) referenced both in the Workflow and a dedicated Reference section.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 with explicit triggers and clear disambiguation from a sibling skill; its only flaw is second-person phrasing ('you need to'), which costs it the top specificity anchor.

Suggestions

Rewrite the opening in third person to avoid the second-person penalty, e.g. 'Use when writing unit tests for Micronaut applications' instead of 'Use when you need to write unit tests…'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (Mockito-first with @ExtendWith, @MicronautTest with @MockBean, @Property overrides, @ParameterizedTest, Test vs IT naming), which would be a 3, but the rubric penalizes second-person voice ('Use when you need to write unit tests') by reducing specificity by 1.	2 / 3
Completeness	Clearly answers both what (Mockito-first unit testing patterns for Micronaut) and when via an explicit 'Use when…' clause plus 'This should trigger for requests such as…'.	3 / 3
Trigger Term Quality	Good coverage of natural trigger phrases users would say: 'write unit tests for Micronaut applications', 'Add or improve unit tests in a Micronaut project', and 'Reduce unnecessary @MicronautTest usage with Mockito-first tests'.	3 / 3
Distinctiveness Conflict Risk	Clear Micronaut-specific niche with distinct triggers, and it explicitly disambiguates from framework-agnostic Java by redirecting to @131-java-testing-unit-testing.	3 / 3
	Total	11 / 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.