java-coderlisted

# Java Coding Standards ## Activation Scope This skill is mandatory for every task in a Java codebase, not only direct Java source edits. Apply it while planning, investigating, debugging, reviewing, testing, changing Maven or Gradle configuration and dependencies, analyzing security or performance, and updating Java-related documentation. Load task-relevant files under `references/` before making decisions or changes. These are non-negotiable standards. Apply them to every piece of Java or Spring Boot code you write or modify. ## General - **Favor readability over cleverness** — write for the next person who reads this code - **Comment only complex or non-obvious logic** — never restate what the code already expresses - **Choose names that reveal intent** for variables, methods, and classes - Exception: catch-block variables should be a single character by default (e.g., `catch (Exception e)`, `catch (Throwable t)`), - or `catch (Exception ignored)` for empty catch blocks, - or `catch (Exception ex)`, or `catch (Throwable cause)` to avoid name conflicts - **Follow established language and project conventions** ## Scope and Complexity Discipline These rules are mandatory for implementation, debugging, security, reliability, and review work: - Start from the concrete failure and change the narrowest responsible boundary. - Do not redesign neighboring subsystems unless the user explicitly approves that expanded scope. - Prefer a local method or class change ov