← ClaudeAtlas

spring-boot-scaffoldinglisted

Use when creating a new Spring Boot application with a verified build, tests and minimal CI. Select compatible Spring Initializr metadata and the requested build tool; not for migrating or overwriting an existing application.
rrezartprebreza/spring-boot-skills · ★ 362 · AI & Automation · score 89
Install: claude install-skill rrezartprebreza/spring-boot-skills
# Spring Boot 3 Scaffolding Create a minimal application for the requested use case, not a fixed enterprise stack. Target Boot 3; never silently switch major versions because a template is easier to obtain. ## Establish the generation contract Confirm a new destination, project coordinates/package, Java level, Maven or Gradle and required capabilities. Ask only for missing consequential choices. Preserve the requested database, servlet/reactive stack, language and response contract. Do not add JPA, Redis, Lombok, JWT issuance, AI providers or telemetry services without a requirement. Read [the generation procedure](references/generation.md) before fetching or extracting an archive. Record the approved provider, metadata timestamp and exact requested inputs. A request to generate does not authorize publishing project details to an arbitrary provider. ## Version-specific checks Select an advertised stable Boot 3 release and compatible Java/build-tool options. Do not substitute Boot 4 when the public Initializr no longer advertises the requested Boot 3 version. Offer an approved provider or a version-pinned manual build, clearly labeled as an alternate path; do not downgrade a Boot 4 archive by merely changing its parent. Keep Framework 6/Jackson 2 and Boot 3 test dependency conventions. Never select an RC, milestone or snapshot unless explicitly requested. Version identifiers must come from metadata; do not assume stable releases end with `.RELEASE`. Check the effective