spring-boot-server
Installation
SKILL.md
Composition
- compose with
java-conventionsfor all language-level Java rules (syntax, style, naming, visibility, interfaces/classes, methods/lambdas, streams/collections, exceptions, comments/JavaDoc) - compose with an architecture skill when architecture is specified or already present, such as
bce,sdd4j-bce,sdd4j-package-by-feature, orsdd4j-package-by-layer - when no architecture is specified, infer and preserve the existing project organization instead of introducing BCE, package-by-feature, or package-by-layer by default
- this skill specializes only the Spring Boot server stack and does not restate language-level Java or architecture-level rules
Dependencies
- prefer dependencies in this order: Java SE, Spring Boot starters already present in the project, Spring ecosystem modules already used by the project
- avoid adding dependencies for problems already solved by Spring Boot, Java SE, or the existing project stack
- ask before changing Maven
pom.xml, Gradle build files, dependency versions, Java version, Spring Boot version, or plugin configuration - do not introduce a second web stack; Spring MVC and WebFlux should not be mixed unless the existing project already does so deliberately
Architecture Fit
- treat Spring Boot as the application stack, not as the architecture
- preserve the architecture already used by the project, including package-by-feature, package-by-layer, BCE, hexagonal, clean architecture, modular monolith, or a local project convention
- do not rename packages, introduce architectural layers, or reorganize code solely because this skill is active
- when adding new code, place it where equivalent Spring components already live
- when no convention exists, choose the smallest clear structure for the requested change and avoid committing the project to a broad architecture prematurely
- keep Spring framework annotations at application entry points, application services, configuration, adapters, and persistence integration points; avoid leaking Spring concerns into domain code unless the project already follows an active-record or Spring-centric model