Code Comments

This is the antidote to documentation that lives in a wiki somewhere and rots while the code evolves. It teaches Claude to write comments that explain *why* code exists, not what it does, across four levels: file headers that show how pieces fit together, function docs that describe contracts and edge cases, inline comments for non-obvious decisions, and architectural notes for big tradeoffs. The philosophy is simple: write for future you, your teammates, and AI assistants who only see one file at a time. Includes language-specific patterns for TypeScript, Swift, Python, and React. Best for teams who've learned the hard way that separate documentation drifts but comments next to code get updated together.