tdd-workflow

Guide Test-Driven Development workflows with Jest, Vitest, and Playwright.

1|Updated Jan 24, 2026

Search Tags:#code quality #unit tests #testing #tdd #integration tests #e2e tests #playwright

Ready to run

npx skills add https://github.com/ShunmeiCho/claude-config --skill tdd-workflow-shunmeicho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ShunmeiCho/claude-config/tree/main/config/skills/tdd-workflow
Command: npx skills add https://github.com/ShunmeiCho/claude-config --skill tdd-workflow-shunmeicho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process to ensure high-quality, well-tested code, reducing bugs and improving maintainability.

Core Features & Use Cases

Enforces TDD: Guides users to write tests before writing implementation code.
Comprehensive Testing: Mandates unit, integration, and E2E tests with a minimum of 80% coverage.
Use Case: When developing a new API endpoint, use this skill to first define the expected request/response and error scenarios in tests, then write the minimal code to pass those tests.

Quick Start

Activate this skill when starting any new feature development or bug fix.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema

How do I start test-driven development for a new API endpoint?▼

To enforce test-driven development, write unit, integration, and E2E tests before implementation code, achieving a minimum of 80% test coverage across the entire project.

Can I use Playwright for E2E tests while following a TDD workflow?▼

Yes, Playwright is fully supported for writing E2E tests alongside Jest and Vitest, covering unit, integration, and end-to-end testing layers in the TDD workflow.

How do I mock dependencies when writing tests before implementation code?▼

You mock dependencies by organizing test files and using framework-specific mocking examples provided by the workflow to isolate units before writing the implementation code.

What is the minimum test coverage required for TDD?▼

The minimum test coverage required for TDD is 80%, enforced across unit, integration, and E2E tests to reduce bugs and improve code maintainability.

Does a TDD workflow support Vitest and Jest for unit testing?▼

Yes, both Vitest and Jest are supported for unit testing, providing specific examples for mocking dependencies and organizing test files within the TDD workflow.