302-frameworks-spring-boot-rest

Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code. 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 clean, concise overview with strong progressive disclosure and a validation-backed workflow, weakened mainly by actionability since the concrete design rules live in the reference rather than the body. Workflow clarity and structure are solid.

Suggestions

Add one or two short, executable inline code snippets (e.g., a minimal @RestController with @Valid DTO and Pageable return) so the body is actionable without requiring the reference.

Tighten the abstract workflow step "Implement or refactor configuration/code following the reference patterns and project conventions" into specific, checkable sub-actions.

Reduce redundancy between the description's capability list and the "What is covered in this Skill?" list to free token budget for the inline example above.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized: topical lists, terse constraints, and a short workflow with no explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It provides concrete build commands ("./mvnw compile", "mvn clean verify") and edge-case handling, but the core design guidance is deferred to the reference and the workflow steps are abstract ("Implement or refactor configuration/code following the reference patterns"), leaving key details inline-missing.	2 / 3
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints (MANDATORY compile-before, SAFETY stop-on-failure, VERIFY after), giving feedback loops for the risky build/edit/build cycle.	3 / 3
Progressive Disclosure	The SKILL.md is an overview pointing to a single, real, well-signaled one-level-deep reference (references/302-frameworks-spring-boot-rest.md, linked in both the workflow and a dedicated Reference section), so navigation is easy.	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, comprehensive description with explicit what/when guidance and natural trigger terms, narrowly held back only by its second-person voice. It is clearly distinguishable and unlikely to conflict with other skills.

Suggestions

Rewrite the description in third person (e.g., "Use when designing, reviewing, or improving REST APIs…") to avoid the second-person voice penalty and restore the specificity score.

The closing phrase "Part of cursor-rules-java project" is project metadata that does not aid triggering; consider moving it out of the description.

Dimension	Reasoning	Score
Specificity	The description lists many concrete capabilities ("design, review, or improve REST APIs", HTTP methods, DTOs, versioning, ETags, problem details) which would normally anchor at 3, but it uses second-person voice ("Use when you need to…") which the rubric penalizes by reducing specificity by one.	2 / 3
Completeness	It clearly answers both what (design/review/improve Spring Boot REST APIs) and when (explicit "Use when…" clause plus "This should trigger for requests such as…"), matching the top anchor.	3 / 3
Trigger Term Quality	It includes explicit natural phrases users would say ("Review Java code for Spring Boot REST API", "Apply best practices for Spring Boot REST API in Java code"), giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	The skill occupies a clear niche (Spring Boot REST APIs) with distinct triggers, making it 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.