312-frameworks-spring-data-jdbc

Use when you need to use Spring Data JDBC with Java records — including entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. This should trigger for requests such as Review Java code for Spring Data JDBC; Apply best practices for Spring Data JDBC 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

70%

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

A well-structured overview skill: strong workflow sequencing with real validation feedback loops and clean one-level reference disclosure. It loses points on conciseness (content duplicating the description) and actionability (concrete code patterns live only in the reference, not the body).

Suggestions

Remove or compress the 'What is covered in this Skill?' and 'When to use this skill' sections, since they repeat the frontmatter description, to improve token efficiency.

Add one short representative code snippet (e.g. a record entity with @Id/@Table or an immutable with*-update) in the body so actionable patterns are visible without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'What is covered in this Skill?' list and the 'When to use this skill' section largely duplicate the frontmatter description's capabilities and trigger phrases verbatim, so not every token earns its place.	2 / 3
Actionability	Concrete build commands ('./mvnw compile', 'mvn clean verify') are present, but the core guidance ('Implement or refactor configuration/code following the reference patterns') is abstract and delegates actual patterns to the reference rather than giving executable examples in the body.	2 / 3
Workflow Clarity	A clearly sequenced 4-step workflow is paired with explicit validation checkpoints and a feedback loop in Constraints ('MANDATORY: Run ./mvnw compile before applying', 'If compilation fails, stop immediately', 'VERIFY: Run mvn clean verify after'), matching the top anchor.	3 / 3
Progressive Disclosure	The body is a concise overview that points to a single, clearly signaled one-level-deep reference (references/312-frameworks-spring-data-jdbc.md, verified to exist) via both the Workflow step and a dedicated Reference link section.	3 / 3
	Total	10 / 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 what-and-when triggers and a clear niche; its only weakness is the second-person 'you need' phrasing, which the rubric penalizes on specificity.

Suggestions

Rewrite the trigger clause in third person to avoid the specificity penalty, e.g. 'Use when working with Spring Data JDBC and Java records' instead of 'Use when you need to use...'.

The trailing 'Part of cursor-rules-java project' adds little trigger value and could be moved to metadata to keep the description focused.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities ('entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems'), which would merit a 3, but the second-person phrasing 'Use when you need to use' triggers the rubric's -1 specificity penalty for non-third-person voice.	2 / 3
Completeness	Explicitly answers both what (the enumerated capability areas) and when (an explicit 'Use when...' clause plus 'This should trigger for requests such as...'), matching the top anchor.	3 / 3
Trigger Term Quality	Natural trigger phrasing is present and reinforced with example user requests ('Review Java code for Spring Data JDBC; Apply best practices for Spring Data JDBC in Java code'), terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The narrow niche 'Spring Data JDBC with Java records' with distinct, specific triggers makes it unlikely to fire for an unrelated skill.	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: 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.