java-coding-standards
Enforce consistent Java conventions across Spring Boot and Quarkus services with automatic framework detection. Covers naming, immutability, dependency injection, reactive patterns, exception handling, and project structure tailored to each framework's idioms.
java-coding-standards applies framework-aware conventions for Spring Boot and Quarkus projects covering naming, immutability, dependency injection, and reactive patterns.
AI-generated summary based on this skill's SKILL.md
Install
affaan-m/ECC/java-coding-standards · repository language: JavaScript
git clone https://github.com/affaan-m/ECC
cp -r ECC/skills/java-coding-standards ~/.claude/skills/java-coding-standardsnpx skillfed install affaan-m/ECC/java-coding-standardsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What java coding standards does this skill cover for Spring Boot?
java-coding-standards enforces consistent Java conventions tailored to Spring Boot projects, including naming conventions, immutability patterns, exception handling strategies, and dependency injection best practices. The skill applies framework-specific idioms to help you structure Spring Boot services with proper bean configuration, REST controller naming, and centralized exception mapping aligned with Spring's ecosystem.
How does java-coding-standards handle Quarkus best practices?
java-coding-standards detects Quarkus projects and applies framework-specific patterns including CDI dependency injection, reactive Uni/Multi patterns, Panache entity conventions, and dev services testing approaches. It enforces naming and immutability standards within Quarkus's lightweight, container-native context while respecting the framework's distinct architectural choices.
What java 17 naming conventions are recommended?
java-coding-standards reviews and enforces modern Java 17 naming conventions including sealed classes, records for immutable data structures, and consistent package/class/method naming patterns. It validates that naming reflects intent clearly, follows camelCase for methods and variables, PascalCase for classes, and UPPER_SNAKE_CASE for constants across your codebase.
How does java-coding-standards structure Java projects with best practices?
java-coding-standards guides project layout organization covering package hierarchies, separation of concerns (controllers, services, repositories, entities), configuration management, and resource placement. It ensures your Spring Boot or Quarkus project follows industry-standard directory structures that scale with team size and promote maintainability.
Does java-coding-standards cover exception handling and null validation?
Yes. java-coding-standards enforces centralized exception mapping, proper exception hierarchy usage, and null handling strategies including Optional usage patterns and validation frameworks. It promotes fail-fast approaches, meaningful error messages, and framework-appropriate exception handlers for both Spring Boot and Quarkus environments.
What reactive patterns and dependency injection does this skill teach?
java-coding-standards covers reactive programming with streams and Optional, Spring's @Autowired/@Inject patterns, and Quarkus CDI conventions. It validates correct dependency injection configuration, reactive type usage (Uni/Multi in Quarkus, Mono/Flux in Spring), and helps avoid common code smells in both frameworks.
SKILL.md
rendered from the published skill — quoted content, verbatim
Java Coding Standards
Standards for readable, maintainable Java (17+) code in Spring Boot and Quarkus services.
When to Use
- Writing or reviewing Java code in Spring Boot or Quarkus projects
- Enforcing naming, immutability, or exception handling conventions
- Working with records, sealed classes, or pattern matching (Java 17+)
- Reviewing use of Optional, streams, or generics
- Structuring packages and project layout
- [QUARKUS]: Working with CDI scopes, Panache entities, or reactive pipelines
How It Works
Framework Detection
Before applying standards, determine the framework from the build file:
- Build file contains
quarkus→ apply [QUARKUS] conventions - Build file contains
spring-boot→ apply [SPRING] conventions - Neither detected → apply shared conventions only
Core Principles
- Prefer clarity over cleverness
- Immutable by default;
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/java-coding-standards/SKILL.md