What problem does it solve?
Establishes clear, consistent conventions to reduce bugs, improve readability, and make Spring Boot Java services easier to review and maintain across teams.
Core Features & Use Cases
- Naming & Structure: Conventions for types, methods, constants, and a recommended Maven/Gradle project layout to keep projects predictable.
- Immutability & Types: Guidance to prefer immutable types, records, final fields, and safe Optional handling to minimize shared mutable state.
- Robust Error Handling & Testing: Recommendations for meaningful unchecked domain exceptions, wrapping technical errors with context, and testing expectations (JUnit 5, AssertJ, Mockito).
- Use Case: Apply these standards when authoring or reviewing Java 17+ Spring Boot services to enforce immutability, sensible Optional usage, clean stream pipelines, and conventional package organization.
Quick Start
Use the java-coding-standards skill to review MarketService.java for naming, immutability, Optional usage, stream clarity, and exception handling.