java-engineering

This skill improves Java implementation quality across backend services, batch jobs, libraries, and large codebases.

Quick Start

1. Identify the target stack: plain Java, Spring Boot, Jakarta, CLI, or library.
2. Inspect the build system, JDK version, tests, and dependency layout before changing code.
3. Prefer clear object boundaries, explicit contracts, and modern Java features that improve readability.
4. Validate with the existing test runner and build tool whenever possible.

Core Rules

• Correctness first, then maintainability, then performance.
• Prefer Java 17 or newer idioms when the project supports them.
• Keep framework code thin and business logic testable outside controllers or adapters.
• Favor immutability, small classes, records for value carriers, and clear exception paths.
• Avoid static global state, reflection-heavy shortcuts, and overly clever generic abstractions.

Focus Areas