tdd

Enforce a test-driven development workflow with failing tests, minimal code, and coverage verification.

Updated Feb 10, 2026

Search Tags:#code quality #testing #tdd #development workflow #refactoring #test-driven development

Ready to run

npx skills add https://github.com/ihj04982/my-cursor-settings --skill tdd-ihj04982

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/ihj04982/my-cursor-settings/tree/main/skills/tdd
Command: npx skills add https://github.com/ihj04982/my-cursor-settings --skill tdd-ihj04982

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a strict Test-Driven Development (TDD) workflow, ensuring code quality and maintainability by prioritizing test creation before implementation.

Core Features & Use Cases

Scaffold Interfaces: Define types and interfaces first.
Generate Tests First: Write failing tests before writing any code.
Implement Minimal Code: Write just enough code to pass the tests.
Refactor: Improve code quality while maintaining passing tests.
Verify Coverage: Ensure a minimum of 80% test coverage.
Use Case: When building a new feature, use /tdd to guide the process from interface definition to refactoring, ensuring robust and well-tested code.

Quick Start

Use the tdd command to implement a function that calculates market liquidity score.

Frequently Asked Questions about tdd

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

FAQPage Schema

How do I enforce a test-driven development workflow for new features?▼

To enforce test-driven development, scaffold interfaces first, write failing tests before implementation, write minimal code to pass, refactor, and verify at least 80% test coverage.

What is the correct sequence for writing failing tests before implementation?▼

The correct sequence for test-driven development is defining types and interfaces first, generating failing tests, implementing minimal code to pass, and refactoring while maintaining passing tests.

How do I verify test coverage for critical code during refactoring?▼

Verify test coverage for critical code by enforcing a minimum 80% coverage requirement after refactoring, ensuring all unit, integration, and E2E tests pass.

Can I use test-driven development for integration and E2E tests?▼

Yes, test-driven development supports various test types including unit, integration, and E2E tests, with specific coverage requirements enforced for critical code paths.

What's the best way to start test-driven development when building a new function?▼

The best way to start test-driven development is scaffolding the interface first, then writing failing tests before writing any implementation code to ensure robust and well-tested results.

Why does test-driven development require writing minimal code to pass tests?▼

Test-driven development requires writing minimal code to pass tests to ensure code quality and maintainability by prioritizing test creation before full implementation.