305-frameworks-spring-boot-modulith

Use when you need to design, review, or improve modular monoliths with Spring Modulith in Spring Boot applications - including application module package structure, ApplicationModules verification, named interfaces, allowed dependencies, domain events, @ApplicationModuleTest, Scenario-based module tests, generated documentation, actuator exposure, observability, and event publication registry choices. This should trigger for requests such as Add Spring Modulith to a Spring Boot application; Review Spring Modulith module boundaries; Improve modular monolith architecture in Spring Boot; Add @ApplicationModuleTest tests; Generate Spring Modulith documentation. 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.

The body is a well-organized overview with strong workflow validation checkpoints and clean one-level-deep progressive disclosure. Its main weakness is actionability: the implementation steps are abstract and lack executable code or annotation examples, relying on the reference file for the concrete details.

Suggestions

Add a short, copy-paste code snippet in the Workflow (e.g., a package-info.java showing @org.springframework.modulith.ApplicationModule with named interfaces, or a minimal @ApplicationModuleTest example) so the body is actionable without forcing a reference read.

The 'What is covered in this Skill?' list substantially duplicates the frontmatter description's capability enumeration; consider trimming it to avoid redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive — no padding explaining what a modular monolith or Spring Modulith is, and every section (Constraints, When to use, Workflow, Reference) earns its place assuming Claude's competence.	3 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify', 'ApplicationModules.verify()', '@ApplicationModuleTest'), but the core modeling steps are abstract ('Identify business-capability modules', 'Add or refine Spring Modulith dependencies, package annotations') with no executable code or annotation examples — detailed guidance is deferred to the reference.	2 / 3
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints and feedback loops: MANDATORY compile before changes, SAFETY 'stop immediately' on compilation failure, and VERIFY 'mvn clean verify' afterward — matching the highest anchor for risky operations.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing to a single real, one-level-deep reference (references/305-frameworks-spring-boot-modulith.md), clearly signaled via a markdown link in both the Workflow and Reference sections.	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.

The description is comprehensive and well-triggered, clearly answering both what the skill does and when to use it with realistic request phrasings. The only issue is second-person voice ('Use when you need to'), which the rubric penalizes on specificity.

Suggestions

Rephrase the opening to third person (e.g., 'Use when designing, reviewing, or improving modular monoliths with Spring Modulith...') to avoid the second-person specificity penalty.

Tighten the long capability list — several items (e.g., 'actuator exposure, observability, and event publication registry choices') could be condensed to reduce length without losing trigger value.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ('design, review, or improve modular monoliths', 'ApplicationModules verification, named interfaces, allowed dependencies, domain events, @ApplicationModuleTest, Scenario-based module tests, generated documentation, actuator exposure, observability, and event publication registry choices'), which would anchor at 3, but the second-person phrasing 'Use when you need to' triggers the rubric's -1 specificity penalty.	2 / 3
Completeness	Both 'what' (the enumerated capabilities) and 'when' ('Use when you need to...', 'This should trigger for requests such as...') are explicitly stated with an explicit trigger clause, satisfying the highest anchor.	3 / 3
Trigger Term Quality	Natural user phrasings are spelled out explicitly — 'Add Spring Modulith to a Spring Boot application', 'Review Spring Modulith module boundaries', 'Improve modular monolith architecture in Spring Boot', 'Add @ApplicationModuleTest tests', 'Generate Spring Modulith documentation' — covering the realistic ways a user would request this skill.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined — Spring Modulith modular monoliths in Spring Boot — with distinct, specific triggers unlikely to fire for unrelated skills.	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: 86eb63d

Reviewed: 4 days 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.