What problem does it solve?
It prevents enterprise teams from producing Spring Boot 4 code that violates project-wide contracts, uses deprecated APIs, or breaks compilation and testing conventions.
Core Features & Use Cases
- Opinionated SB4 development rules covering nullability (JSpecify), Jackson 3 usage, modular starters, compiler lint/werror expectations, and Java 25 safe feature guidance.
- Spec-driven REST development that enforces OpenAPI-first workflows and ensures controllers implement generated interfaces for compile-time conformance.
- Mandatory SB4 testing patterns including RestTestClient defaults, correct slice selection, AssertJ-only assertions, and layered test topology aligned to a narrow-test pyramid.
- Provider-side Pact verification wiring for contract testing that validates HTTP responses against consumer pacts during
tasks.check.
Quick Start
Use the spring-boot-4 skill when you’re generating or reviewing any Spring Boot code so the output follows the project’s mandatory SB4 rules and test/contract expectations.