tdd-workflow

Enforce test-driven development with unit, integration, and E2E tests.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/sumeetonline90/fitup_all --skill tdd-workflow-sumeetonline90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/sumeetonline90/fitup_all/tree/main/.cursor/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/sumeetonline90/fitup_all --skill tdd-workflow-sumeetonline90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent testing practices, low code coverage, and production bugs caused by skipping test-first development workflows, ensuring all code changes are validated before deployment.

Core Features & Use Cases

  • Test-First Enforcement: Requires writing unit, integration, and E2E tests before implementing any new feature, bug fix, or refactor.
  • Coverage Guarantees: Mandates 80%+ test coverage across all code changes, with built-in verification steps.
  • Reusable Testing Patterns: Provides pre-built templates for common test scenarios, including API integration tests, component unit tests, and Playwright E2E tests, plus mocking examples for external services like Supabase and Redis.
  • Use Case: When building a new user authentication flow, this skill guides you to write login/logout test cases first, implement the flow to pass those tests, then verify coverage meets the 80% threshold before merging.

Quick Start

Use the tdd-workflow skill to implement a new password reset feature with passing tests and 80%+ code coverage.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a test-driven development workflow to eliminate undetected bugs?

To enforce test-driven development, this skill requires writing unit, integration, and E2E tests before implementing new features, bug fixes, or refactoring tasks. It validates all code changes against predefined tests to eliminate undetected bugs and ensure production readiness.

How do I ensure 80%+ code coverage when building new API endpoints?

To ensure 80%+ code coverage for API endpoints, this skill mandates built-in verification steps that check test coverage thresholds. It provides pre-built templates for API integration tests and mocking examples for external services like Supabase and Redis to validate endpoint changes.

What is the best way to start writing tests before implementing a user authentication flow?

The best way to start test-driven development for an authentication flow is to write login and logout test cases first. This skill guides you to implement the flow to pass those initial tests, then verifies that code coverage meets the 80% threshold before merging.

Can I use pre-built test patterns for Playwright E2E testing and component unit tests?

Yes, you can use pre-built test patterns for Playwright E2E testing and component unit tests. This skill provides reusable testing templates for common scenarios, including mocking examples for external services like Supabase and Redis, to accelerate test creation.

Does test-driven development work for refactoring legacy code and bug fixes?

Yes, test-driven development works for refactoring and bug fixes. This skill applies a test-first enforcement workflow to all development tasks, ensuring that code changes for refactoring or fixing bugs are validated by unit, integration, and E2E tests before deployment.

Why does my software project have low code coverage and inconsistent testing practices?

Low code coverage and inconsistent testing practices are caused by skipping test-first development workflows. This skill solves the problem by mandating 80%+ test coverage across all code changes and enforcing comprehensive unit, integration, and E2E testing before deployment.