Huangleyang125207

Co-author doctrine for shared, half-hour-block daily schedules. Make sure to consult this skill whenever working in a dated daily log, journal, retro, or coordination file shared with a coworker — even if the user only says "log this at 11:00" or "what did we say last Tuesday." Default behavior of dumping procedural details, paraphrasing voice into corporate prose, or fragmenting one task across m

Coding doctrine for any task that creates, modifies, or refactors code in a programming language. Make sure to consult this skill whenever the user is about to write, edit, debug, or ship code, even if they don't explicitly ask for "best practices" — Claude's default of generating new code from scratch produces code no one can grep, copy, or ship next Friday, and this skill enforces a copy-paste-f

Test-pattern doctrine. Tests are copyable from ~/.claude/patterns/tests/, three categories: input boundary, contract, effect. Make sure to consult this skill whenever code changes touch a boundary where someone else's code meets yours, even if the user doesn't say "test" or "TDD" — Claude tends to ship untested boundary code, and this skill prevents the Saturday phone call. TRIGGER when: code unde