tdd_workflow

Coordinate unit, integration, and e2e tests with Vitest, Testing Library, and Playwright.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill tdd-workflow-denish12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd_workflow
Source: https://github.com/denish12/codex-ai-agent-and-skills/tree/main/locales/en/.agents/skills/tdd_workflow
Command: npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill tdd-workflow-denish12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formulates and enforces a disciplined test-driven development process by providing a clear RED→GREEN→REFACTOR cycle, structured test templates, and practical guidance for building reliable software.

Core Features & Use Cases

  • Structured RED→GREEN→REFACTOR workflow for feature development and refactoring.
  • Guidance on writing unit tests, integration tests, and e2e tests with Vitest, Testing Library, and Playwright.
  • Best practices for naming tests, isolating test cases, and reviewing test quality across teams.

Quick Start

Ask the AI to outline and execute a complete RED→GREEN→REFACTOR cycle for a simple feature.

Frequently Asked Questions about tdd_workflow

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

FAQPage Schema
What is the RED GREEN REFACTOR cycle in test-driven development?

The RED GREEN REFACTOR cycle is a test-driven development workflow where you write a failing test, make it pass with minimal code, then refactor safely while maintaining test coverage.

How do I coordinate unit, integration, and e2e testing using Vitest and Playwright?

Coordinate unit, integration, and e2e testing by using Vitest for unit and integration tests, Testing Library for component validation, and Playwright for end-to-end tests within a structured TDD workflow.

How do I write effective test cases that isolate behavior and catch regressions early?

Write effective test cases by enforcing consistent naming conventions, isolating test cases to prevent dependencies, and establishing clear guardrails to catch regressions early during the feature development cycle.

Can I use Testing Library with Vitest for component testing?

Yes, Testing Library works with Vitest for component testing, allowing you to validate UI components and integration points while following a structured test-driven development workflow.

When should I use Playwright e2e tests instead of Vitest unit tests?

Use Playwright e2e tests for validating complete user workflows across the application, and Vitest unit tests for isolated logic and component behavior verification within the TDD cycle.

What is the best way to review test quality and maintainability across a team?

Review test quality by applying consistent naming conventions, verifying test isolation, and using structured test templates during test reviews to improve maintainability and catch regressions.