Test-driven development — the red/green/refactor loop, what makes a test worth keeping (behavior through public interfaces, not implementation details), where tests go (seams agreed up front), and the anti-patterns that make tests lie (implementation-coupled, tautological, horizontal-sliced). Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests written well.
