Java Coding Standards

This enforces modern Java conventions for Spring Boot and Quarkus services, automatically detecting your framework from the build file and applying the right idioms. It covers the basics you'd expect (naming, immutability, Optional and stream usage) plus framework-specific patterns like constructor injection in Spring versus field injection in Quarkus, Panache entity conventions, and reactive Uni/Multi pipelines. The reactive section is solid, calling out common mistakes like blocking inside async flows or double-subscribing to shared Unis. Useful if your team keeps mixing Spring and Quarkus idioms or needs consistent guardrails around Java 17+ features like records and sealed classes.

skills.sh installs: 6.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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