tdd-workflow

Enforce test-driven development workflows with 80% code coverage requirements.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Zenobia000/ai-brainstorming --skill tdd-workflow-zenobia000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Zenobia000/ai-brainstorming/tree/main/.claude/custom-rule%26skill/skills/tdd-workflow
Command: npx skills add https://github.com/Zenobia000/ai-brainstorming --skill tdd-workflow-zenobia000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of shipping buggy code, inconsistent quality, and low test coverage when developing new features, fixing bugs, or refactoring existing code, by enforcing strict test-driven development principles across the entire development workflow.

Core Features & Use Cases

  • Test-First Enforcement: Requires writing failing tests before implementing any code for features, bug fixes, or refactors.
  • Comprehensive Coverage Requirements: Mandates minimum 80% test coverage across unit, integration, and end-to-end test suites.
  • Ready-to-Use Test Patterns: Includes pre-built templates for Jest/Vitest unit tests, API integration tests, and Playwright E2E tests for common scenarios.
  • External Service Mocking: Provides mock configurations for common tools like Supabase, Redis, and OpenAI to isolate tests. Use case: For example, when building a new user authentication API endpoint, this skill guides you to write test cases for success, validation, and error scenarios first, implement the endpoint to pass the tests, and verify coverage meets the required threshold.

Quick Start

Use the tdd-workflow skill to build the new user profile update API endpoint with full test coverage following TDD principles.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce test-driven development when building new API endpoints?

Test-driven development for API endpoints requires writing failing tests for success, validation, and error scenarios before implementation. This workflow enforces that sequence and verifies minimum 80% code coverage for components and API routes.

What is the best way to maintain 80% code coverage during refactoring?

Maintaining 80% code coverage during refactoring requires running unit, integration, and E2E test suites before modifying code. This workflow mandates test-first execution for refactors to ensure production reliability and prevent regressions.

How do I isolate unit tests when mocking external services like Supabase and Redis?

Isolating unit tests with external services like Supabase and Redis requires pre-built mock configurations. This workflow provides mock setups for common tools to ensure test isolation and prevent external dependencies from affecting results.

Can I use Playwright E2E testing alongside Jest unit tests in a full-stack project?

Playwright E2E testing and Jest unit tests are supported through ready-to-use test patterns. This workflow applies comprehensive test coverage requirements across full-stack scenarios, covering critical user flows and component logic.

Does test-driven development work for fixing bugs in existing code?

Test-driven development for bug fixes mandates writing a failing test that reproduces the bug before implementing the patch. This workflow enforces strict test-first principles across bug fixes and feature development to ensure consistent quality.

Why should I write failing tests before implementing new features?

Writing failing tests before implementing features ensures the test accurately validates the new logic and eliminates the risk of shipping buggy code. This workflow enforces the test-first sequence to achieve minimum 80% test coverage and production reliability.