skills.rest
HexAI-inc
HexAI-incOFFICIAL
Explore all skills by this author →
GitHub

tdd-mastery

Enforce the TDD Iron Law by writing failing tests before production code.

Updated Oct 30, 2025
Search Tags:#code quality#testing#tdd#refactoring#software development#test-driven development
One-click install
npx skills add https://github.com/HexAI-inc/v0-futuristic-website-design --skill tdd-mastery-hexai-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-mastery
Source: https://github.com/HexAI-inc/v0-futuristic-website-design/tree/main/.agents/skills/maestro/skills/tdd-mastery
Command: npx skills add https://github.com/HexAI-inc/v0-futuristic-website-design --skill tdd-mastery-hexai-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) methodology, ensuring that all production code is written only after a failing test has been created, thereby improving code quality and reliability.

Core Features & Use Cases

  • Strict Red-Green-Refactor Cycle: Guides users through writing a failing test, implementing minimal code to pass, and then refactoring.
  • Bug Fix Protocol: Mandates writing a failing test that reproduces a bug before any fix is implemented.
  • Use Case: When developing a new feature, you will first write a test that describes the desired outcome. This test will initially fail. Then, you will write the smallest amount of code necessary for the test to pass. Finally, you will refactor the code while ensuring the test still passes.

Quick Start

Use the tdd-mastery skill to write a failing test for the new 'calculate_discount' function.

Frequently Asked Questions about tdd-mastery

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

FAQPage Schema
How do I enforce test-driven development when writing new software features?▼

Test-driven development is enforced by mandating a strict Red-Green-Refactor cycle, requiring you to write a failing test before any production code is written. This ensures code integrity by validating desired outcomes first.

What is the best way to fix bugs using test-driven development?▼

The best way to fix bugs using test-driven development is following a strict bug fix protocol that mandates writing a failing test reproducing the bug before implementing any code fix, ensuring the issue is accurately validated.

Can I use test-driven development with AI agents for software development?▼

Yes, test-driven development can be integrated with AI agents. The methodology provides specific protocols for AI agent integration, ensuring automated development workflows adhere to the Red-Green-Refactor cycle and code reliability standards.

How does the Red-Green-Refactor cycle improve code quality?▼

The Red-Green-Refactor cycle improves code quality by guiding you to write a failing test, implement minimal code to pass it, and then refactor safely. This process prevents over-engineering and maintains continuous test validation.

Do I need to write a test before refactoring existing code?▼

Yes, you must write a failing test before writing or refactoring production code. The Test-Driven Development Iron Law mandates creating tests first to ensure your refactoring maintains code integrity and reliability without breaking functionality.

Related Skills

Explore More Software Engineering Skills→
GadaaLabsGadaaLabs
67

sculptor

Enforce test-driven development with a failing baseline test before skill implementation.

Community
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
taewook486taewook486

moai-workflow-tdd

Guide software development through the RED-GREEN-REFACTOR TDD cycle.

Community
Advanced
nashgaonashgao
3

TDD Retrofit

Audit, classify, and rewrite confirmation-style tests into specification-first TDD tests.

Community
Advanced