Test Driven Development

This is TDD with zero tolerance for shortcuts. It enforces the full red-green-refactor cycle and makes you watch every test fail before writing implementation code. Write code first? Delete it and start over, no exceptions. The skill catches common rationalizations like "I'll test after" or "keep it as reference" and shuts them down with specific arguments about why test-after doesn't prove your tests work. It includes verification steps at both red and green phases, good and bad examples for each stage, and a table of excuses mapped to reality checks. Uncompromising but clear about why the discipline matters.