311-frameworks-spring-jdbc

Use when you need to write or review programmatic JDBC with Spring — including JdbcClient (Spring Framework 7+) as the default API, JdbcTemplate only where batch/streaming APIs require JdbcOperations, NamedParameterJdbcTemplate for legacy named-param code, parameterized SQL, RowMapper mapping to records, batch operations, transactions, safe handling of generated keys, DataAccessException handling, read-only transactions, streaming large result sets, and @JdbcTest slice testing. This should trigger for requests such as Review Java code for Spring JDBC (JdbcTemplate, JdbcClient, NamedParameterJdbcTemplate); Apply best practices for Spring JDBC data access in Java code; Detect and fix SQL injection risks in JDBC code; Improve transaction boundaries or exception handling for JDBC operations. 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 well-organized, concise, and follows strong progressive-disclosure and workflow practices with explicit compile/verify checkpoints for risky database changes. Its main gap is actionability: it provides build commands but no in-body executable JDBC code examples, relying entirely on the bundled reference for the actual patterns.

Suggestions

Add 1-2 short executable JdbcClient/JdbcTemplate snippets (e.g., a parameterized query and a RowMapper-to-record example) directly in SKILL.md so the most common actions are copy-paste ready without opening the reference.

Tighten the duplicated capability lists: the 'What is covered in this Skill?' bullets overlap heavily with the frontmatter description and the 'When to use' triggers; consider consolidating to reduce redundancy.

Make the reference-pointer more navigable by noting what each major section of references/311-frameworks-spring-jdbc.md contains (e.g., 'good/bad code examples', 'transaction patterns') so readers know what they will find one level deep.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no explanatory padding about what JDBC or Spring is; every section (Constraints, When to use, Workflow, Reference) earns its place, matching the score-3 anchor for efficient, intelligence-respecting content.	3 / 3
Actionability	Concrete build commands are present ('./mvnw compile', 'mvn clean verify') but all actual JDBC/JdbcClient code examples are deferred to the reference file rather than included in the body, fitting the score-2 anchor of some concrete guidance that is incomplete and missing key details rather than fully copy-paste-ready code.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints — MANDATORY compile before changes, SAFETY stop on failure, and VERIFY clean verify after — matching the score-3 anchor for a clear sequence with explicit validation steps and error-recovery feedback loops for risky database operations.	3 / 3
Progressive Disclosure	SKILL.md acts as a concise overview with a single well-signaled one-level-deep reference (references/311-frameworks-spring-jdbc.md, a real file linked twice), matching the score-3 anchor for a clear overview with clearly signaled one-level-deep references and easy navigation.	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.

The description is highly specific, third-person, and provides explicit 'Use when' triggers with natural user phrasing, covering both what the skill does and when to use it. Its only weakness is verbosity: the long capability enumeration and repeated trigger list could be tightened without losing meaning.

Dimension	Reasoning	Score
Specificity	Lists many concrete specific actions such as 'parameterized SQL', 'RowMapper mapping to records', 'batch operations', 'safe handling of generated keys', and '@JdbcTest slice testing', matching the score-3 anchor for multiple concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what it does (the enumerated JDBC capabilities) and when to use it via 'Use when you need to write or review programmatic JDBC with Spring' plus 'This should trigger for requests such as ...', satisfying the score-3 anchor for explicit what-and-when triggers.	3 / 3
Trigger Term Quality	Includes natural trigger phrasing users would actually say such as 'Review Java code for Spring JDBC', 'Apply best practices for Spring JDBC', 'Detect and fix SQL injection risks', and 'Improve transaction boundaries', giving good coverage of natural terms rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (programmatic Spring JDBC with JdbcClient/JdbcTemplate/NamedParameterJdbcTemplate) with distinct triggers, making it unlikely to fire for unrelated skills; matches the score-3 anchor for a clear niche with distinct triggers.	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: 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.