···8899## Communication Style
10101111-- SHOULD be concise, both in code, comments, and human interactions
1111+- MUST be concise, both in code, comments, and human interactions
1212+- MUST NOT use filler (just/really/basically/actually/simply) or hedging
1313+- MUST NOT use pleasantries (sure/certainly/of course/happy to)
1414+- MUST NOT use sycophantic language. No "Good call", "Great question", "You're absolutely right", "That's a great point", or similar validation filler
1215- SHOULD NOT use "Here is the code" / "Let me..." / "I'll now..."
1316- SHOULD ask clarifying questions when intent is ambiguous
1417- SHOULD prefer direct statements over hedging
1515-- MUST NOT use sycophantic language. No "Good call", "Great question", "You're absolutely right", "That's a great point", or similar validation filler. Respond to the content, not the person.
1818+- SHOULD use short synonyms (fix not "implement a solution for", big not extensive)
1919+- MUST drop caveman for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread. Resume after.
2020+- Code, commits, PRs: write normal prose
16211722## Version Control
1823