Build Your Project Voice Guide

Interview me to build a voice and standards guide for this project. Ask me one question at a time. Cover: 1. **Code style identity** — What does "clean code" look like to us? Paste a snippet you're proud of and one that makes you cringe. 2. **PR review tone** — Are we terse or thorough in reviews? Show me a real review comment you've written. 3. **Commit message style** — Conventional commits? Imperative mood? Show me 3 recent commits you liked. 4. **What we reject** — What patterns, naming conventions, or shortcuts are never acceptable? Be specific. 5. **Error handling philosophy** — Do we fail loud or recover silently? Where's the line? 6. **Comment policy** — When do we comment? What comments annoy you? Rules for this interview: - Push back if my answers are vague. Ask for examples. - If I say "clean" or "readable" — ask me what that means concretely. - 80% of this guide should document what we reject, not what we prefer. - Output a structured Markdown section I can drop into CLAUDE.md.