OpenParable
Skip to content
← Back to skills

TDD Guide

Testing & Quality
tdd-guide

TDD Guide is an Agent Skill for testing & quality published in the foryourhealth111-pixel/Vibe-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Test-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/HEAD/bundled/skills/tdd-guide/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/tdd-guide, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

tdd-guide (Codex Compatibility)

Use this skill for all feature work, bug fixes, and refactors that change behavior.

Routing Boundary

Use this skill when the user wants to build or change behavior through tests:

  • TDD / test-driven development
  • write failing tests first
  • test-first implementation
  • RED -> GREEN -> REFACTOR

Do not use it when tests are already failing and the user wants root cause; route that to systematic-debugging. Do not use it when the user only wants a test/coverage report; route that to generating-test-reports.

Core Rule

No production code before a failing test.

Workflow

  1. RED
  • Write one failing test for one behavior.
  • Confirm the failure is expected.
  1. GREEN
  • Implement the minimal code to pass.
  • Re-run tests and keep scope narrow.
  1. REFACTOR
  • Improve structure/naming without changing behavior.
  • Keep all tests green.
  1. COVERAGE
  • Verify coverage target (recommended >=80% for lines/functions/branches).
  • Add missing tests for edge/error paths.

Minimum Test Set

  • Unit: public functions and core logic.
  • Integration: API/data/service boundaries.
  • E2E: critical user path only when relevant.

Required Edge Cases

  • Null/undefined input
  • Empty values
  • Invalid types
  • Boundary values
  • Error paths (network/DB/file)
  • Concurrency-sensitive behavior

Vibe Integration

  • Primary coding skill in M-grade flow.
  • Compatible fallback target for everything-claude-code:tdd-guide.
  • For richer TDD patterns, combine with test-driven-development.