Scaffolds Java 25 + Spring Boot 4 projects for REST APIs, services, and modular backends. Selects architectures like layered, modular monolith, or hexagonal DDD based on complexity.
npx claudepluginhub a-pavithraa/springboot-skills-marketplace --plugin springboot-architectureThis skill uses the workspace's default tool permissions.
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/`.
assets/api-versioning-config.javaassets/base-entity.javaassets/controller.javaassets/docker-compose.ymlassets/exception-handler.javaassets/flyway-migration.sqlassets/http-service-client.javaassets/modularity-test.javaassets/package-info-jspecify.javaassets/pom-additions.xmlassets/repository.javaassets/resilience-service.javaassets/resttestclient-test.javaassets/rich-entity.javaassets/service-cqrs.javaassets/spring-converter.javaassets/testcontainers-test.javaassets/value-object.javareferences/architecture-guide.mdreferences/spring-boot-4-features.mdScaffolds Spring Boot 3.x/4.x projects from Spring Initializr with DDD or Layered architecture, JPA, SpringDoc OpenAPI, and Docker Compose for PostgreSQL/Redis/MongoDB. Use for new Java backends or microservices.
Builds Spring Boot 4.x applications following best practices: MVC REST APIs, Data JPA entities/repositories/services, Modulith, Security, Thymeleaf views, Maven config, ArchUnit/REST tests, Docker Compose, Taskfile.
Generates Spring Boot projects interactively via Spring Initializr API: fetches metadata, selects Boot/Java versions, language, artifact/package, dependencies; downloads, extracts, and runs Gradle Kotlin DSL build. Activates on Spring Boot creation requests.
Share bugs, ideas, or general feedback.
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/.
assets/ instead of rewriting the same scaffolding from scratch.Collect the project constraints first:
Use this matrix as the default decision aid. If the choice is not obvious, read references/architecture-guide.md before proceeding.
| Pattern | Use when | Complexity |
|---|---|---|
layered | CRUD services, prototypes, MVPs | Low |
package-by-module | 3-5 distinct features with moderate growth | Low-Medium |
modular-monolith | Module boundaries matter and Spring Modulith is justified | Medium |
tomato | Rich domain modeling, value objects, stronger type safety | Medium-High |
ddd-hexagonal | Complex domains, CQRS, strong infrastructure isolation | High |
Use Spring Initializr and capture the baseline:
Baseline dependencies for most projects:
Optional dependencies based on architecture or features:
Read references/spring-boot-4-features.md before selecting:
Use the bundled templates from assets/ and replace placeholders only after the package and module names are settled.
Core project templates:
assets/controller.javaassets/repository.javaassets/rich-entity.javaassets/value-object.javaassets/service-cqrs.javaassets/exception-handler.javaassets/flyway-migration.sqlassets/docker-compose.ymlBoot 4 and modularity templates:
assets/http-service-client.javaassets/api-versioning-config.javaassets/resttestclient-test.javaassets/package-info-jspecify.javaassets/modularity-test.javaassets/resilience-service.javaassets/pom-additions.xmlassets/testcontainers-test.javaRead references/architecture-guide.md for package structure and apply the matching templates:
layered: keep modules simple and avoid premature DDD abstractionspackage-by-module: group by feature and keep shared code minimalmodular-monolith: add Modulith verification and explicit module APIstomato: add value objects and rich domain entities where they protect important invariantsddd-hexagonal: separate application, domain, and infrastructure explicitlyspring-data-jpa when the user needs deeper query, projection, repository, or relationship decisions.springboot-migration for upgrades of existing applications rather than new-project setup.references/architecture-guide.mdreferences/spring-boot-4-features.mdWhen the user asks for a plan or scaffold recommendation, return:
## Recommended architecture
- Pattern:
- Why:
## Initial setup
- Build tool:
- Java version:
- Spring Boot version:
- Core dependencies:
## Assets to apply
- `assets/...`
## Next implementation steps
1. ...
2. ...
3. ...