savant-code: Skill for Claude Code

Java Coding Standards

Naming Conventions

Element	Convention	Example
Classes	PascalCase	UserProfile, GameState
Interfaces	PascalCase	Serializable, Renderable
Methods	camelCase	calculateDistance, spawnUnit
Variables	camelCase	playerCount, isValid
Constants	UPPER_SNAKE_CASE	MAX_PLAYERS, TILE_SIZE
Enums	PascalCase (class), UPPER_SNAKE_CASE (values)	TileType.GRASSLAND
Packages	lowercase, reversed domain	com.example.gameengine
Files	PascalCase.java (match class name)	UserProfile.java

Patterns

Error Handling

• Use custom exception hierarchy extending Exception
• Catch specific exceptions, never bare Exception
• Use try-with-resources for AutoCloseable
• Log at catch points with context

Concurrency

• Prefer ExecutorService over raw threads
• Use synchronized or ReentrantLock for shared state
• Immutable objects preferred over synchronization
• Use CompletableFuture for async composition

Imports

• Group: java → javax → external → internal
• No wildcard imports
• Use IDE auto-import management

File Structure

src/main/java/com/example/
├── Application.java         # Entry point
├── config/
│   └── AppConfig.java       # Configuration
├── exception/
│   └── AppException.java    # Custom exceptions
├── model/
│   └── [Domain].java        # Data classes
├── service/
│   └── [Domain]Service.java # Business logic
src/test/java/
└── [Mirror structure]

Anti-Patterns to Flag

• Bare catch (Exception e)
• Mutable static fields
• God classes (one class dominating a file near the 400-line ceiling)
• Deep inheritance hierarchies (>3 levels)
• null returns instead of Optional
• Magic numbers (extract to constants)

Quality Limits

protocol.config.yaml owns the file-length ceiling, and scripts/quality-report.ts enforces it against every project-owned source file: max_file_lines (400 today). There is no per-language override mechanism — no Java-specific ceiling is enforced anywhere — so the rows below are style guidance, not gates.