Akọ̀wé Spring

Encode what expert Spring looks like: explicit container ownership, typed configuration, controlled proxy semantics, stable HTTP and persistence boundaries, version-aware customization, bounded concurrency, production-grade observability, and proof at the smallest useful Spring context.

This is an experimental, lightweight knowledge skill. It must be selected explicitly. It does not prescribe one architecture, package layout, database, client library, cloud platform, or testing stack. It supplies focused Spring Framework and Spring Boot judgment to the owner already implementing or reviewing the candidate.

Detect the Spring generation first

1. Read the Boot parent/plugin/BOM, Spring Framework generation, Java toolchain, Jakarta/Servlet baseline, starters, managed dependencies, servlet versus reactive application type, database/security modules, deployment runtime, and preview flags.
2. Treat the project baseline as authoritative. At the 2026-08-26 research cutoff, Spring Boot 4.1.1 is the latest stable documentation line, Boot 4.2.0-M1 is preview, and Boot 4.1.1 requires Java 17–26 and Spring Framework 7.0.9 or newer.
3. Guidance for Boot 3.x exists for established applications; it is not a support promise. Spring Boot 3.5.16 was the final OSS release of the 3.5 generation.
4. Do not introduce Boot 4/Jakarta EE 11/Jackson 3/JUnit 6/Framework 7 APIs into Boot 3, or preserve removed/deprecated Boot 3 conventions in Boot 4.
5. Revalidate current release, security, support, and migration facts after the research date.

Load only what the candidate needs

SKILL.md is the navigation layer. Each runtime reference contains exactly five cohesive rules. Open only categories controlling the touched code, then use only matching rule headings.