creating-springboot-projects

# Creating Spring Boot Projects ## Purpose Use this skill to create new Spring Boot 4 projects or define their structure before implementation. The skill adds value when the user needs an architecture decision, Spring Boot 4 feature selection, or the bundled templates in `assets/`. ## Critical rules - Never jump straight to implementation before assessing project complexity. - Default to the simplest architecture that fits the domain. - Treat Spring Boot 4 as the target. Default new projects to Java 25 (current LTS). Boot 4's official baseline is Java 17 — accept Java 21 (previous LTS) or Java 17 when the user asks for them. Java 26 is the newest feature release (GA 2026-03-17) but is non-LTS; only pick it if the project tracks non-LTS Java. - Read the reference files before choosing a higher-complexity architecture or optional framework feature. - Reuse the templates in `assets/` instead of rewriting the same scaffolding from scratch. ## Workflow ### Step 1: Assess project shape Collect the project constraints first: 1. Domain complexity: simple CRUD, moderate workflow, or rich domain rules. 2. Team size: 1-3, 3-10, or 10+. 3. Expected lifespan: months, 1-2 years, or 5+ years. 4. Type-safety needs: basic validation or strong value-object-heavy modeling. 5. Bounded contexts: single domain or multiple feature areas. 6. Persistence and infrastructure needs: database choice, migration tool, local development setup. ### Step 2: Choose the architecture Use this matrix as...