tdd-workflow

Implement test-driven development with 80% coverage across unit, integration, and end-to-end tests.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/iDako7/SmartGroceryAssistant --skill tdd-workflow-idako7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/iDako7/SmartGroceryAssistant/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/iDako7/SmartGroceryAssistant --skill tdd-workflow-idako7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces test-driven development practices to ensure features are implemented with comprehensive tests and intentional design, delivering reliable code with 80%+ test coverage.

Core Features & Use Cases

  • Test-First Development: Write tests before code to guide implementation and catch regressions early.
  • Comprehensive Coverage: Target at least 80% coverage across unit, integration, and end-to-end tests, including edge cases.
  • Structured Testing Patterns: Use unit, API integration, and Playwright end-to-end patterns to validate components, services, and user flows.

Quick Start

Write a failing test for a new feature, then implement the minimal code to pass.

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 for feature development?

To enforce test-driven development, write failing tests before implementation, add minimal code to pass, and validate across unit, integration, and e2e stages to guarantee reliable code with 80%+ coverage.

Can I use Playwright for end-to-end testing within a TDD workflow?

Yes, Playwright is used for end-to-end testing patterns within the workflow to validate user flows, alongside unit and API integration tests, ensuring comprehensive coverage during feature development and refactoring.

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

The best way to maintain 80% test coverage is to follow structured unit, integration, and e2e testing patterns, writing tests first to catch regressions early and validate edge cases before modifying existing code.

Does test-first development apply to bug fixes and API creation?

Yes, test-first development applies to bug fixes, API creation, and component development, requiring you to write failing tests that define the expected behavior before implementing the minimal code to pass.

Why should I write tests before code when building components?

Writing tests before code guides intentional implementation and catches regressions early, ensuring features are validated through unit, integration, and e2e patterns before functional code is finalized.