skills.rest
reynalivan
reynalivanCOMMUNITY
Explore all skills by this author →
GitHub

tdd

Enforce red-green-refactor workflows with mandatory failing tests before production code.

Updated Feb 15, 2026
Search Tags:#testing#tdd#react#rust#red-green-refactor#test-driven-development
One-click install
npx skills add https://github.com/reynalivan/EMMM2 --skill tdd-reynalivan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/reynalivan/EMMM2/tree/main/.agent/skills/tdd
Command: npx skills add https://github.com/reynalivan/EMMM2 --skill tdd-reynalivan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test-driven development enforces building tests before production code, reducing regressions and ensuring the intended behavior is verified from the start.

Core Features & Use Cases

  • Red-Green-Refactor workflow: write a failing test, implement the minimal code to pass, and then refactor for clarity and maintainability.
  • Mandatory testing discipline: ensure code changes are validated by tests before they are considered complete.
  • Cross-language applicability: usable across Rust, React, and other languages to maintain consistent quality.

Quick Start

Create a failing test for the intended behavior, implement the simplest code that makes the test pass, and then refactor for clarity.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce test-driven development in my feature workflow?▼

Test-driven development is enforced by satisfying the red-green-refactor workflow, requiring a mandatory failing test before any production code is implemented. This prevents unverified code changes and reduces regressions.

What is the red-green-refactor workflow for test-driven development?▼

The red-green-refactor workflow involves writing a failing test for intended behavior, implementing the minimal code to pass, and then refactoring for clarity and maintainability. This ensures intended behavior is verified from the start.

Can I apply test-driven discipline to both Rust and React projects?▼

Yes, test-driven discipline applies across Rust, React, and general software projects to maintain consistent quality. It enforces test-first validation for feature development, bug fixes, and refactoring across these languages.

Does test-driven development work for bug fixes and refactoring?▼

Yes, test-driven development applies to bug fixes and refactoring by enforcing a test-first discipline. It ensures code changes are validated by mandatory failing tests before they are considered complete.

Why write a failing test before implementing production code?▼

Writing a failing test before production code ensures the intended behavior is verified from the start and reduces regressions. It enforces the test-first discipline required for reliable development.

What are the limitations of strict test-driven development patterns?▼

Strict adherence to test-driven patterns requires writing mandatory failing tests for every code change, which may slow down initial feature delivery but ensures all changes are validated before completion.

Related Skills

Explore More Software Engineering Skills→
jmstar85jmstar85
153

tdd

Enforce red-green-refactor cycles by writing failing tests before implementation.

Community
Intermediate
axiomanticaxiomantic
8

test-driven-development

Enforce a red-green-refactor workflow by writing failing tests before production code.

Official
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
hydrosolutionshydrosolutions
1

test-driven-development

Guide feature development with a failing test before production code.

Official
Advanced