# Coding conventions

- Automate anything repeatable. If done manually twice, it belongs in a script, hook, or pipeline step.
- No comments unless the why is genuinely non-obvious. Names carry meaning; git history carries context.
- No defensive code at internal boundaries. Validate only at system edges: user input, external APIs, git hooks.
- Prefer explicit over implicit. Code must be readable without inferring intent from convention.
- No abstractions, features, or cleanup beyond what the task requires.