How does this skill enforce the TDD process?

It directs Claude to write failing test cases based on user journeys before any implementation code is generated, strictly following the Red-Green-Refactor cycle.

Does it support mocking external services?

Yes, it provides specific, production-ready mocking patterns for common dependencies like Supabase, Redis, and OpenAI to keep tests fast and isolated.

What testing frameworks are supported?

The skill includes optimized patterns and snippets for major frameworks including Jest, Vitest, and Playwright for browser automation.

When is the best time to use the TDD Workflow skill?

It should be activated at the start of any new feature development, bug fix, or refactoring task where code reliability and maintainability are priorities.

Can I customize the 80% coverage requirement?

Yes, while the skill defaults to 80% to ensure quality, the workflow integrates with your project's existing configuration files like jest.config.json or vitest.config.ts.

TDD Workflow

Name: TDD Workflow
Author: WorldFlowAI

byWorldFlowAI

Security & Testing

Enforces a rigorous test-driven development cycle with standardized patterns for unit, integration, and E2E testing.

About

This skill streamlines the software development lifecycle by enforcing a strict 'Tests Before Code' methodology within the Claude Code environment. It guides developers through a structured 7-step process—from defining user journeys and writing failing test cases to implementation and refactoring—ensuring codebases maintain a minimum of 80% coverage. By providing standardized patterns for Jest, Vitest, and Playwright, it simplifies the creation of resilient unit tests, API integrations, and browser-based user flows while preventing common testing pitfalls and brittle selectors.

Key Features

Standardized patterns for Unit, Integration, and Playwright E2E tests
0 GitHub stars
Minimum 80% code coverage enforcement across all test types
Automated test file organization and coverage verification
Structured 7-step Red-Green-Refactor workflow guidance
Built-in mocking strategies for Supabase, Redis, and OpenAI

Use Cases

Safely refactoring legacy code with comprehensive regression suites
Implementing robust API endpoints with validated error handling
Building new features with a strict test-first approach

About

Key Features

Standardized patterns for Unit, Integration, and Playwright E2E tests
0 GitHub stars
Minimum 80% code coverage enforcement across all test types
Automated test file organization and coverage verification
Structured 7-step Red-Green-Refactor workflow guidance
Built-in mocking strategies for Supabase, Redis, and OpenAI

Use Cases

Safely refactoring legacy code with comprehensive regression suites
Implementing robust API endpoints with validated error handling
Building new features with a strict test-first approach