Loading...
Loading...
Found 2 Skills
Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership.
Explain how a subsystem works or where code should live. Use for runtime walkthroughs, architectural ownership, layering questions, and architecture critique; use why for historical motivation.