java-coding-standards

To enforce Java coding standards for Spring Boot services, apply consistent naming conventions, refactor to records and final fields, simplify streams, model domain-specific exceptions, and organize Maven or Gradle project layouts for predictable code.

Handle Optional and immutability in Java 17+ projects by using records, final fields, and sensible Optional handling to reduce shared mutable state and NPEs, ensuring safer and more maintainable Spring Boot code.

Yes, this coding standards skill works with both Maven and Gradle project layouts. It defines package structure, resource placement, and test expectations specifically for Spring Boot Java projects to validate architecture guidance.

The best way to model exceptions in Spring Boot Java applications is to use domain-specific unchecked exceptions that include context. This approach improves safety and makes code easier to maintain during reviews.

Review Java streams and generics for maintainability by validating stream simplicity and ensuring type-safe generics. This process yields concrete refactoring recommendations to simplify complex stream pipelines.

You should not use Optional for null handling in Spring Boot when Bean Validation annotations are more appropriate for input safety. For general null handling, structured logging and sensible Optional usage reduce NPEs without overcomplicating domain logic.