Akọ̀wé Java

Encode what expert modern Java looks like: explicit contracts, strong value semantics, baseline-aware API choices, controlled concurrency, observable failure, and proof proportionate to risk.

This is an experimental lightweight knowledge skill. It must be selected explicitly while its rule coverage, retrieval shape, and interaction with project/framework conventions are evaluated. It does not prescribe one architecture, framework, build tool, testing library, or application shape. It supplies focused Java language and JDK judgment to the owner already implementing or reviewing the candidate.

Apply the baseline before the advice

1. Read the repository's Java toolchain, compiler --release, CI/runtime image, library consumer baseline, enabled preview/incubator flags, and framework constraints.
2. Treat the project baseline as authoritative. Java 25 is the current LTS and Java 26 is the current feature release at this skill revision; neither fact authorizes newer syntax or APIs in an older project.
3. Do not introduce preview or incubator features unless the repository explicitly accepts their flags, runtime coupling, and migration risk.
4. Preserve established framework and repository conventions when they deliberately specialize a language-level rule. Challenge them only with concrete evidence, not fashion.

Load only what the candidate needs

SKILL.md is the navigation layer. Each reference contains five cohesive rules; open only the categories relevant to the code in front of you, then use only the matching rule headings.