300-frameworks-spring-boot-create-project
About 300-frameworks-spring-boot-create-project
A skill that scaffolds Spring Boot projects as Maven projects using SDKMAN-managed tooling. It defaults to Java 25 and Spring Boot 4.0.x, then verifies the generated project with Maven.
Key features
- 01Check SDKMAN and Java availability
- 02Select SDKMAN-managed tools
- 03Gather project settings and dependencies
- 04Generate a Spring Boot Maven project
- 05Verify with Maven
Use cases
- 01Create a Spring Boot Maven project
- 02Bootstrap a Spring Boot service
- 03Scaffold a Java 25 application
- 04Generate a project with selected dependencies
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ jabrena/ plinth --skill 300-frameworks-spring-boot-create-projectAfter installing, type/300-frameworks-spring-boot-create-projectin Claude Code to confirm it loaded.
Bundled filesreferences/300-frameworks-spring-boot-create-project.md
Details
From the project READMECreate 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 verifyfrom the generated project when the Maven wrapper exists; otherwise runmvn 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
- Create Spring Boot 4 Maven project
- Scaffold Spring Boot service with Java 25
Workflow
- 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.
- 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.
- 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.
- 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.