Java Coding Standards

Enforces Java 17+ conventions across Spring Boot and Quarkus projects, with automatic framework detection from your build file. Covers the practical stuff: naming (PascalCase classes, camelCase methods), immutability defaults with records, Optional instead of nulls, constructor injection patterns, and Quarkus-specific bits like Panache entities with public fields and reactive Uni/Multi pipelines. Also handles exception mappers, project layout, and the subtle differences between Spring's @Service/@RestController and Quarkus's @ApplicationScoped/@Path resources. Useful during code reviews or when onboarding developers who need consistent patterns without memorizing framework quirks. The Quarkus reactive guidance alone saves you from common blocking mistakes in event loop contexts.

skills.sh installs: 6.2K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill java-coding-standards --agent claude-code

Installs into .claude/skills of the current project.

Files

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; minimize shared mutable state
Fail fast with meaningful exceptions
Consistent naming and package structure
[QUARKUS]: Favor build-time over runtime processing; avoid runtime reflection where possible