java-coding-standards

The Java Coding Standards skill provides a comprehensive framework for writing, reviewing, and maintaining clean, scalable code within Spring Boot services. Designed for developers working with Java 17 and above, it ensures consistency across naming conventions, exception handling, and modern language feature utilization. By prioritizing clarity and immutability, this skill helps teams reduce technical debt and build more robust, observable backend systems. Whether you are scaffolding a new microservice or refactoring legacy components, this tool acts as an automated architectural guide to ensure your code remains idiomatic, type-safe, and production-ready.

• Enforces strict naming conventions for classes, records, and methods, along with clear PascalCase and camelCase standards.

• Promotes immutability by encouraging the use of Java records, final fields, and the avoidance of shared mutable state.

• Provides best practices for modern Java features, including effective Optional handling, stream pipelining, and pattern matching.

• Guides the structure of Maven and Gradle projects into logical domains such as config, controller, service, repository, and dto layers.

• Sets clear expectations for error management, favoring domain-specific unchecked exceptions and meaningful logging patterns.

• Supports integration with JUnit 5, AssertJ, and Mockito to promote deterministic, fluent, and maintainable unit testing.

• Use this skill during active development to validate method signatures and package layout against standard project structures.

• Input your code snippets or pull requests to receive feedback on anti-patterns like long parameter lists, deep nesting, or magic numbers.

• Apply this as a baseline for peer reviews to ensure consistent use of Bean Validation, nullable annotations, and dependency injection.

• Constraints include a strong emphasis on Java 17+ features; older legacy versions may require specific adjustments. The skill assumes a standard Spring Boot ecosystem; custom frameworks might require minor configuration tweaks to match the suggested project layout.