- Keep changes focused and easy to review.
- Prefer clear names and straightforward structure.
- Remove dead code and avoid speculative abstractions.
- Explain the problem first, then the fix.
- Include validation steps (tests, commands, screenshots when relevant).
- Call out tradeoffs and follow-up work explicitly.
- Include a concise summary and reproducible context.
- State expected vs actual behavior.