What problem does it solve? Writing tests after implementation often produces shallow happy-path checks that miss regressions and encode poor structure. This Skill enforces a disciplined red-green-refactor cycle so every behavior gets a failing test first, then minimal implementation, then refactoring. ## Core Features & Use Cases - Red-Green-Refactor Cycle: Write one failing test, confirm it fails for the right reason, implement the minimum code to pass, then refactor while tests stay green. - Test Naming & Structure Rules: Enforces describe('when <scenario>') / it('<present-tense behavior>') conventions, one assertion focus per test, no should/when/if in it titles, and no multi-phase tests. - Bug Fix TDD: Reproduce a bug with a failing regression test before fixing it, ensuring the fix is verified and guarded against recurrence. - Use Case: When asked to add a new feature to a Vue component, write a failing test for the new behavior first, implement the minimal code to pass, then refactor — repeating vertically per behavior rather than writing all tests upfront. ## Quick Start Use test-driven development to implement this feature, writing a failing test for each behavior before the code that makes it pass.
