300-frameworks-spring-boot-create-project
This Claude Code skill automates the creation of Maven-based Spring Boot 4.0.x projects using SDKMAN-managed Java and Spring Boot CLI tooling. Use it when you need to bootstrap a new Spring Boot service, gather project coordinates and dependencies, verify SDKMAN and Java availability, generate the project through Spring Initializr, and validate the setup with Maven verification commands before reporting completion.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/300-frameworks-spring-boot-create-project && cp -r /tmp/300-frameworks-spring-boot-create-project/skills/300-frameworks-spring-boot-create-project ~/.claude/skills/300-frameworks-spring-boot-create-projectSKILL.md
# Create Spring Boot Maven Project Create a new Spring Boot Maven project through SDKMAN-managed tooling, aligned with Java 25 and the repository's Spring Boot 4.0.x baseline. **What is covered in this Skill?** - Verify SDKMAN and Java availability before project creation - Install or select the required Java and Spring Boot CLI candidates through SDKMAN - Gather project coordinates, package name, Java version, packaging, and dependencies - Create a Maven project with Spring Initializr-backed Spring Boot CLI commands - Prefer Maven wrapper commands for validation - Verify the generated project with Maven before reporting completion ## Constraints Project creation must be explicit, reproducible, and Maven-based. - **PREREQUISITE**: Verify SDKMAN is installed with `sdk version`; if missing, stop and provide setup guidance instead of installing it silently - **JAVA BASELINE**: Prefer Java 25 unless the user requests another supported version - **FRAMEWORK BASELINE**: Target Spring Boot 4.0.x by default - **BUILD TOOL**: Generate a Maven project, not Gradle - **SAFETY**: Do not overwrite an existing non-empty target directory without explicit user confirmation - **VERIFY**: Run `./mvnw clean verify` from the generated project when the Maven wrapper exists; otherwise run `mvn clean verify` - **BEFORE APPLYING**: Read the reference for the full SDKMAN and Spring Boot CLI workflow ## When to use this skill - Create a Spring Boot Maven project - Bootstrap Spring Boot project with SDKMAN - Generate a new Spring Boot service ## Workflow 1. **Read reference and gather project inputs** Read `references/300-frameworks-spring-boot-create-project.md`, then gather project directory, group, artifact, package name, Java version, packaging, and initial dependencies. 2. **Verify SDKMAN-managed tooling** Check SDKMAN, Java, and Spring Boot CLI availability. Install or switch candidates only after confirming the intended versions with the user. 3. **Create the Maven project** Use Spring Boot CLI project creation backed by Spring Initializr, making Maven the selected build tool and Spring Boot 4.0.x the default baseline. 4. **Verify and report** Run Maven verification in the generated project and summarize commands used, selected options, generated path, and any follow-up setup. ## Reference For detailed guidance, examples, and constraints, see [references/300-frameworks-spring-boot-create-project.md](references/300-frameworks-spring-boot-create-project.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project