tdd-testing

To implement Test-Driven Development, this Skill guides you through a mandatory Red-Green-Refactor cycle using Vitest and React Testing Library, providing specific templates and commands to write unit, store, and component tests before writing implementation code.

The Red-Green-Refactor cycle enforces writing failing tests first, then implementing code to pass those tests, and finally refactoring. This TDD workflow prevents regressions by ensuring all critical code paths in directories like src/lib and src/stores are validated before implementation.

For unit testing, you should set specific minimum acceptable code coverage percentages tailored to different code modules. This Skill defines distinct coverage targets for libraries, stores, components, and pages to ensure robust code quality across your project architecture.

Yes, you can use this TDD workflow for both utility functions and UI components. It includes specific testing templates and commands for unit tests in src/lib, store tests, and component testing using Vitest and React Testing Library to cover critical code paths.

You should not use Test-Driven Development for non-critical code paths outside specified directories like src/lib and src/stores. This Skill enforces TDD specifically for critical logic to prevent regressions, meaning trivial or highly exploratory code might not require this strict workflow.