How does the 80% coverage requirement work?

The skill guides the AI to run coverage reports and identify specific lines or branches that lack tests, ensuring the final implementation meets the 80% threshold.

Does it support End-to-End (E2E) testing?

Absolutely. It includes dedicated workflows for Playwright to ensure critical user journeys and UI interactions are verified in a real browser environment.

Does this skill work with any testing framework?

While the skill provides specific patterns for Jest, Vitest, and Playwright, its core TDD principles and workflow can be adapted to any modern testing stack.

Can it help with mocking external APIs?

Yes, it includes built-in patterns for mocking common services like Supabase, Redis, and OpenAI to ensure your tests remain fast, isolated, and cost-effective.

When is the best time to activate the TDD Workflow?

You should activate it at the start of any task involving code changes, including feature development, bug fixes, or architectural refactors.

TDD Workflow

Name: TDD Workflow
Author: pmeneres-uneidades

bypmeneres-uneidades

Security & Testing

Enforces test-driven development principles and mandatory 80% coverage across unit, integration, and E2E testing layers.

About

The TDD Workflow skill transforms Claude into a disciplined software engineer by mandating a 'tests-first' approach for all new features, bug fixes, and refactorings. It guides the development process through a rigorous cycle of writing user journeys, defining failing tests, implementing minimal code, and refactoring, while ensuring a minimum 80% code coverage threshold is met. This skill is indispensable for developers prioritizing code reliability, long-term maintainability, and regression prevention in modern JavaScript and TypeScript environments.

Key Features

0 GitHub stars
Automated TDD cycle enforcement (Red-Green-Refactor)
Predefined mocking patterns for external services like Supabase, Redis, and OpenAI
Mandatory 80% code coverage validation across all code paths
Semantic selector and user-centric testing best practices
Multi-tier testing support for Unit, Integration, and Playwright E2E tests

Use Cases

Standardizing testing patterns and coverage requirements across a development team
Building new application features with guaranteed regression safety
Refactoring legacy codebases while maintaining functional integrity

About

Key Features

0 GitHub stars
Automated TDD cycle enforcement (Red-Green-Refactor)
Predefined mocking patterns for external services like Supabase, Redis, and OpenAI
Mandatory 80% code coverage validation across all code paths
Semantic selector and user-centric testing best practices
Multi-tier testing support for Unit, Integration, and Playwright E2E tests

Use Cases

Standardizing testing patterns and coverage requirements across a development team
Building new application features with guaranteed regression safety
Refactoring legacy codebases while maintaining functional integrity