These are design constraints, not a checklist. The repository's documented Go standards and existing architecture govern Go syntax, naming, package layout, formatting, APIs, and tooling. Do not override them with a general design principle or local preference. When principles conflict, choose the option that lowers future cost in this repository while preserving correctness, clarity, and existing behavior.
When existing structure prevents a clean change:
- Make the smallest behavior-preserving refactor needed.
- Run the relevant tests and checks.