tdd

name	tdd
description	Implement a feature using strict test-driven development

Implement the following feature using Test-Driven Development: the task/scope the user described when invoking this skill (if none given, ask or infer from context)

Follow the RED → GREEN → REFACTOR cycle strictly.

Cycle

1. RED: Write a failing test that describes the desired behavior.
2. GREEN: Write the minimum code to make the test pass.
3. REFACTOR: Clean up while keeping tests green.

Process

1. Understand the requirement.
2. Identify the test framework already in use (jest, vitest, pytest, go test, etc.).
3. Write test cases covering: happy path, edge cases, error cases.
4. Run tests → confirm they fail.
5. Implement the minimum code to pass.
6. Run tests → confirm they pass.
7. Refactor if needed, keeping tests green.
8. Report test coverage for the new code.

Rules

• Never write implementation before tests.
• Each test checks ONE behavior.
• Descriptive test names: should [expected behavior] when [condition].
• Mock external dependencies, not internal logic.
• Aim for meaningful coverage, not 100% line coverage.