code-style git:20260515.b58240cA

Immutable. This exact content is served forever at /api/v1/blob/d0d92f9583b511c0.

---
name: code-style
description: "Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes."
---

# Code Style: Mirror, Reuse, Symmetry

When writing new code in an existing codebase, follow these principles:

1. **Mirror the surrounding code exactly**: Match brace style, comment style, naming conventions, blank line spacing, code density, and level of detail by reading nearby code first.
2. **Reuse existing patterns**: Find the closest analogous feature and replicate its structure (method decomposition, control flow, annotations, guard clauses). Don't introduce new patterns when an existing one fits.
3. **Reuse existing code**: Before writing a new helper, check if an existing method can be reused or generalized. If a new helper is needed, model it after its closest sibling.
4. **Maintain symmetry**: If adding `fooB()` parallel to `fooA()`, ensure naming, parameter order, and structure are symmetric. Rename `fooA()` if needed.
5. **Logical ordering**: Place new methods, switch cases, and fields in the order that mirrors the existing grouping or business lifecycle, not just appended at the end.
6. **Comment only the WHY**: Don't paraphrase what well-named code already says. A comment earns its place when it captures a hidden constraint, workaround, spec reference, or surprising behavior. Keep each comment to one concern; lift broader rationale to design docs or commit messages.