300-frameworks-spring-boot-create-project

Use when you need to create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling. This should trigger for requests such as Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot service. 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

57%

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

The content is a well-structured overview with strong progressive disclosure and present validation, but it trades some actionability and conciseness by keeping the executable creation command and the error-recovery loop in the reference while repeating trigger and scope information inline.

Suggestions

Inline the concrete `spring init --build=maven ...` example (or at least its key flags) so the core creation step is actionable without opening the reference.

Add an explicit fix-and-retry loop to the Verify step (e.g., "if `mvnw clean verify` fails, fix the reported goal and re-run") rather than delegating it to the reference.

Remove the redundant "What is covered in this Skill?" and "When to use this skill" sections, which restate the Workflow and the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is terse and avoids explaining concepts Claude already knows, but the "What is covered in this Skill?" bullets preview the Workflow and the "When to use this skill" section duplicates the frontmatter description, so it could be tightened.	2 / 3
Actionability	Some concrete commands appear ("sdk version", "./mvnw clean verify", "mvn clean verify"), but the core creation step is described abstractly ("Use Spring Boot CLI project creation backed by Spring Initializr") with the executable `spring init` command deferred to the reference.	2 / 3
Workflow Clarity	A clear four-step sequence with an explicit VERIFY checkpoint and safety constraints is present, but the fix-and-retry feedback loop for verification failures lives in the reference rather than being stated in the body.	2 / 3
Progressive Disclosure	The body is a well-organized overview that signals a single one-level-deep reference (references/300-frameworks-spring-boot-create-project.md, verified to exist) via a clear markdown link, with content appropriately split between overview and detail.	3 / 3
	Total	9 / 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 well-constructed with explicit what-and-when guidance, natural trigger terms, and a clearly scoped niche. Its only weakness is that it centers on a single concrete action rather than enumerating multiple specific operations.

Dimension	Reasoning	Score
Specificity	It names a concrete domain and action ("create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling") but describes essentially one task with tooling context rather than a list of multiple distinct concrete actions.	2 / 3
Completeness	It explicitly states what the skill does (create a Maven-based Spring Boot 4.0.x project) and when to use it via both an explicit "Use when..." clause and "This should trigger for requests such as...".	3 / 3
Trigger Term Quality	The triggers "Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot service" are natural phrasings a user would actually say, with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to SDKMAN-managed tooling, Maven build, and Spring Boot 4.0.x, making it unlikely to trigger for unrelated skills despite the somewhat broad "Generate a new Spring Boot service" phrasing.	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.