dotnet-tdd

GREEN phase - Write minimal code to make failing tests pass

RED phase - Write failing tests for a feature before implementation

REFACTOR phase - Improve code design while keeping tests green

Review code for TDD best practices and clean code principles compliance

Execute complete TDD cycle (RED-GREEN-REFACTOR) for implementing a feature with integrated feedback loops

TDD implementation specialist. Use to write minimal code that makes tests pass (GREEN phase). Focuses on simplest solution that satisfies tests without over-engineering.

TDD refactoring specialist. Use to improve code design while keeping tests green (REFACTOR phase). Applies SOLID, DRY, KISS, YAGNI, and CQS principles.

Code review specialist for TDD and clean code principles. Use proactively after implementation to review code for SOLID, DRY, KISS, YAGNI, CQS compliance and test quality.

TDD test design specialist. Use to design failing tests before implementation (RED phase). Creates comprehensive test cases following AAA pattern, proper naming conventions, and test doubles.

Clean code principles including DRY, KISS, and YAGNI for .NET. Use when writing or reviewing code to ensure maintainability and simplicity.

Command Query Separation (CQS) and CQRS patterns for .NET. Use when designing methods, handlers, and application architecture. Ensures predictable, testable code.

Requirements clarification for TDD. Use BEFORE RED phase to understand WHAT to test. Asks targeted questions to uncover ambiguities, edge cases, and acceptance criteria.

SOLID design principles for .NET. Use when designing classes, interfaces, and object relationships. Ensures maintainable, testable, and extensible code.

Test-Driven Development workflow for .NET. Use when implementing features, fixing bugs, or writing new code. Guides RED-GREEN-REFACTOR cycle with proper test design.