tdd-workflow

Enforce Test-Driven Development with 80% coverage using Jest and Playwright.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/venables/dotfiles --skill tdd-workflow-venables
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/venables/dotfiles/tree/main/ai/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/venables/dotfiles --skill tdd-workflow-venables

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures all code development adheres to Test-Driven Development (TDD) principles, leading to more robust, maintainable, and higher-quality software by enforcing comprehensive test coverage.

Core Features & Use Cases

  • Enforces TDD: Guides users to write tests before writing implementation code.
  • Mandates Coverage: Requires a minimum of 80% test coverage across unit, integration, and E2E tests.
  • Comprehensive Testing: Supports various test types including unit, integration, and end-to-end (E2E) tests using tools like Jest, Playwright, and Vitest.
  • Use Case: When developing a new API endpoint, use this skill to first define the expected request/response and error scenarios with tests, then implement the endpoint logic to satisfy those tests, ensuring reliability from the start.

Quick Start

Activate this skill to develop a new feature, ensuring all tests are written first and achieve at least 80% 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 test-driven development when writing new API endpoints?

To enforce test-driven development for new APIs, write tests defining expected requests, responses, and error scenarios before implementation, then build the endpoint logic to satisfy those tests.

What is the minimum code coverage required for TDD workflows?

The minimum code coverage required for TDD workflows is 80%, which must be maintained across unit, integration, and end-to-end tests to ensure robust and maintainable software.

How do I write tests before implementation using Jest and Playwright?

Write tests before implementation using Jest and Playwright by first defining edge cases, error scenarios, and critical user flows, then developing the code necessary to pass those specific test cases.

Does this TDD workflow support both unit and end-to-end testing?

Yes, this TDD workflow supports both unit and end-to-end testing, specifically integrating tools like Jest, Playwright, and Vitest to cover comprehensive testing scenarios.

When should I use end-to-end tests in a test-driven development cycle?

Use end-to-end tests in a test-driven development cycle to validate critical user flows and comprehensive integration scenarios, ensuring the entire application path functions reliably from start to finish.

Why does TDD require writing tests before writing the actual implementation code?

TDD requires writing tests before implementation code to ensure all edge cases and error scenarios are defined upfront, guiding the development of more reliable, maintainable, and higher-quality software.