tdd-expert

Enforce Test-Driven Development for .NET projects using TUnit, NSubstitute, and Verify.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/MCrank/code-compress --skill tdd-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-expert
Source: https://github.com/MCrank/code-compress/tree/main/.claude/skills/tdd-expert
Command: npx skills add https://github.com/MCrank/code-compress --skill tdd-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces rigorous Test-Driven Development (TDD) practices within the CodeCompress .NET project, ensuring code quality and maintainability through a strict Red-Green-Refactor cycle.

Core Features & Use Cases

  • TDD Enforcement: Guides users through the Red-Green-Refactor cycle for all new code.
  • Test Framework Expertise: Provides deep knowledge of TUnit, NSubstitute, and Verify for writing effective tests, mocks, and snapshots.
  • Code Quality: Enforces project conventions, including naming, structure, and build warnings.
  • Use Case: When developing a new feature, use this Skill to write failing tests first, then the minimum code to pass, and finally refactor, ensuring robust and well-tested code from the outset.

Quick Start

Use the tdd-expert skill to write a new failing test for the CSharpParser class.

Frequently Asked Questions about tdd-expert

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

FAQPage Schema
How do I enforce Test-Driven Development in a .NET project?

To enforce Test-Driven Development in .NET, follow a strict Red-Green-Refactor cycle by writing failing tests first, implementing minimal code to pass, and then refactoring while adhering to project conventions and quality standards.

What is the best way to write unit tests using TUnit and NSubstitute?

Writing effective unit tests with TUnit and NSubstitute requires looking up API documentation, writing failing tests first, creating minimal implementation code to pass them, and refactoring to ensure quality and maintainability.

Can I use the Verify library for snapshot testing in .NET TDD?

Yes, Verify is used within the TDD workflow for .NET projects to manage snapshots, ensuring that new code adheres to the Red-Green-Refactor cycle and maintains strict project conventions and quality standards.

How do I start writing a failing test first for a new .NET feature?

Start writing a failing test first for a new .NET feature by utilizing TUnit and NSubstitute to draft the test, ensuring it fails before writing the minimum implementation code required to pass it and then refactoring.

Does strict TDD methodology enforce .NET project conventions and build warnings?

Yes, strict TDD methodology enforces .NET project conventions, including naming and structure, while ensuring code quality and maintainability throughout the Red-Green-Refactor cycle without introducing build warnings.