TDD-discipline

What problem does it solve?

Developers often skip writing tests first, leading to code that is hard to test, poorly designed, and prone to regressions, increasing technical debt and slowing down development.

Core Features & Use Cases

• Sacred Cycle Enforcement: Guides and enforces the strict RED → GREEN → REFACTOR cycle, ensuring a failing test always precedes implementation, leading to robust, well-tested code.
• Minimal Implementation Principle: Promotes writing only the absolute minimal code to pass a test, preventing feature creep, premature optimization, and unnecessary complexity.
• Git History Validation: Mandates specific Git commit patterns (TEST:, FEAT:, REFACTOR:) to prove TDD adherence and block merges for violations, ensuring a verifiable development process.
• Use Case: When starting a new feature, use this skill to guide you through writing a failing test, verifying its failure, implementing the minimal code to pass, and then refactoring, ensuring each step is committed correctly and demonstrably.

Quick Start

Start implementing user authentication by writing a failing test for valid credentials, then verify it fails for the correct reason.