A Claude Code plugin with production-ready skills and agents for building Spring Boot 4.x / Java 21+ applications. Install the plugin and start generating your app — the skills and agents guide Claude to follow best practices for REST APIs with Problem Details errors, JPA, Flyway database migrations, security, testing, cloud-native deployment, and Kubernetes.
Install from Anthropic marketplace
claude plugin install spring-boot-template@piominOr install directly from repository
claude plugin marketplace add piomin/claude-ai-spring-boot
claude plugin install spring-boot-template@piomin
Then run Claude Code and type:
/pluginTo test locally during development:
claude --plugin-dir /path/to/claude-ai-spring-bootSpecialized agents that Claude Code can invoke for specific tasks:
| Agent | Purpose |
|---|---|
spring-boot-engineer |
Build Spring Boot 4.x apps with layered architecture and Problem Details errors; adds the OpenAPI contract rules when the API is built for a UI |
code-reviewer |
Read-only review of a diff or branch: fixes the scope, loads the conventions and code-quality skills, reports cited findings by severity |
kubernetes-specialist |
K8s deployments, probes, ConfigMap/Secret, Prometheus, Skaffold |
devops-engineer |
CI/CD pipelines, Paketo Buildpacks, Skaffold |
docker-expert |
Multi-stage Dockerfiles, Paketo Buildpacks, image optimization |
security-engineer |
Spring Security, OWASP, input validation, SSL Bundles |
Reusable knowledge that Claude loads contextually:
| Skill | What it teaches |
|---|---|
conventions |
Mandatory project rules: No Lombok, constructor injection, RestClient, testing standards, conditional Flyway for relational databases, Problem Details, conditional OpenAPI contract rules for APIs built for a UI |
spring-boot |
Core Spring Boot development with 6 reference guides (web incl. Problem Details and paging, OpenAPI with springdoc 3, data incl. Flyway migrations, security, cloud, testing) |
code-quality |
Review checklist loaded on demand from 6 references (correctness, security, performance, Spring signals, REST semantics, code smells); points to conventions and other skills for project rules instead of repeating them |
design-patterns |
Classic patterns (Factory, Builder, Strategy) + enterprise (Saga, Outbox, CQRS) |
testing-patterns |
JUnit 5, Mockito, MockMvc, RestTestClient, Testcontainers with @ServiceConnection, relation and status-endpoint integration tests, Podman |
java-modern |
Java 21+ features: records, sealed classes, pattern matching, virtual threads |
jpa-patterns |
JPA/Hibernate pitfalls (N+1, lazy loading), Hibernate 6/7, optimistic locking across HTTP requests, relation writes with OSIV off, schema drift |
logging-patterns |
Structured JSON logging, SLF4J, MDC, AI-friendly formats |
The plugin enforces these rules via the conventions skill:
- No Lombok — explicit constructors, getters/setters,
LoggerFactory.getLogger() - Constructor injection — no
@Autowiredon fields - RestClient over RestTemplate/WebClient for blocking HTTP calls
- RestTestClient with
@AutoConfigureRestTestClientfor integration tests - Testcontainers with
@ServiceConnection(not@DynamicPropertySource) - Jakarta Persistence (not
javax.persistence) - Problem Details (RFC 9457) for every error; paged lists as
PagedModel; optimistic locking with@Versionand 409 - OpenAPI contract rules, only when the API is built for a UI (see below)
- Flyway owns the schema (
ddl-auto: validate) when the API persists to a Flyway-supported relational database; skipped for APIs without persistence, NoSQL-only APIs, or projects already using Liquibase - Maven with
pl.piomin.servicesgroup ID - CI pipeline — auto-detected from existing project config
- Docker Compose for local dependencies
The cloud.md reference covers:
- Spring Cloud (Config Server, Eureka, Gateway, Resilience4j, LoadBalancer)
- Distributed tracing with OpenTelemetry (OTLP) and Micrometer Observation API
- Virtual Threads, HTTP Interface Clients (
@HttpExchange), GraalVM Native Image - Kubernetes: ConfigMap/Secret with
envFrom, Prometheus annotations, startup/liveness/readiness probes,preStophook, graceful shutdown - TLS: cert-manager (Ingress TLS + pod-level mTLS), SSL Bundles with hot reload
- Config Tree for reading mounted secrets from files
- Paketo Buildpacks via
spring-boot:build-image - Skaffold for local K8s development loop
After installing, describe what you want to build — Claude will use the skills and agents automatically:
cd my-project
claude
> "Build a REST API for managing orders with PostgreSQL"For a relational database like PostgreSQL, the generated app includes Flyway migrations in src/main/resources/db/migration, ddl-auto: validate, and Testcontainers tests that verify all migrations were applied. APIs without persistence or with NoSQL stores get no Flyway configuration.
Some rules are required only when the API is built for a UI (or another client generated from its OpenAPI contract), for example a UI made from crud-ui-blueprint. Say so in your prompt ("the API backs a web UI generated from its OpenAPI contract") or in the project's CLAUDE.md. The conventions skill then loads skills/spring-boot/references/ui-contract.md, the single source of these rules:
/apibase path, same origin (no CORS), operationIds the UI's generated client relies on- an OpenAPI contract generated by springdoc 3, exported to
contract/openapi.jsonby a test and checked in CI, withinfo.versionfrom the build - Problem Details field errors with a fixed set of codes the UI translates,
PUTwith a requiredversion - typed list filters, relations as
{id, label}summaries, 409in-useinstead of cascading deletes - the Keycloak realm layout the UI logs in with, public
/actuator/healthand/actuator/info, and a README "Connect a UI" section
Without a UI, none of this is required: the generated API keeps Problem Details, paging and optimistic locking, and skips the contract export.
You can also invoke skills and agents directly:
# Invoke a skill
> /spring-boot-template:jpa-patterns
# Use an agent
> @agent-spring-boot-template:code-reviewer.
├── .claude-plugin/
│ └── plugin.json
├── agents/
│ ├── code-reviewer.md
│ ├── devops-engineer.md
│ ├── docker-expert.md
│ ├── kubernetes-specialist.md
│ ├── security-engineer.md
│ └── spring-boot-engineer.md
├── skills/
│ ├── conventions/SKILL.md
│ ├── code-quality/
│ │ ├── SKILL.md
│ │ └── references/
│ │ ├── api-contract.md
│ │ ├── correctness.md
│ │ ├── performance.md
│ │ ├── security.md
│ │ ├── smells.md
│ │ └── spring-conventions.md
│ ├── design-patterns/SKILL.md
│ ├── java-modern/SKILL.md
│ ├── jpa-patterns/SKILL.md
│ ├── logging-patterns/SKILL.md
│ ├── spring-boot/
│ │ ├── SKILL.md
│ │ └── references/
│ │ ├── cloud.md
│ │ ├── data.md
│ │ ├── ui-contract.md
│ │ ├── security.md
│ │ ├── testing.md
│ │ └── web.md
│ └── testing-patterns/SKILL.md
├── README.md
└── LICENSE
You can find a detailed explanation of this plugin in the post: Claude Code Template for Spring Boot.
Apache License 2.0
