Claude Cursor Skill

tdd-workflow

Test-driven development discipline: RED (failing test) → GREEN (minimal code) → REFACTOR, delete-and-restart if production code was written first, and the test-type taxonomy (integration for API surfaces, unit for business logic, property for edge-case-heavy code). Load before st

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-internal_builtins_universal_testing_skills_tdd-workflow-ca967ad.zip · 0 KB

goldziher/ai-rulez 162 16 forks MIT Updated 5h ago

Part of goldziher/ai-rulez — 151 skills

Install

skills CLI npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/testing/skills/tdd-workflow

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart

Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Write the test before the code. Update the test when changing behaviour.
Fixing a bug: write the failing test first, then fix. RED → GREEN → REFACTOR.
Wrote production code before the test? Delete it and start over — no exceptions, don't keep it as reference.
Integration tests for API surfaces, unit tests for business logic, property tests for edge-case-heavy code.
Run the full test suite before committing — never push untested code.
Run the new test and confirm it fails for the right reason before writing the fix.
If a test cannot be made to pass after three attempts, stop and report rather than skipping or weakening it.

Files (ai-rulez)

SKILL.md 1.1 KB

---
name: tdd-workflow
description: "Test-driven development discipline: RED (failing test) → GREEN (minimal code) → REFACTOR, delete-and-restart if production code was written first, and the test-type taxonomy (integration for API surfaces, unit for business logic, property for edge-case-heavy code). Load before starting a feature or bug fix, when reproducing a reported bug, or when deciding which kind of test a change needs."
---

- Write the test before the code. Update the test when changing behaviour.
- Fixing a bug: write the failing test first, then fix. RED → GREEN → REFACTOR.
- Wrote production code before the test? Delete it and start over — no exceptions, don't keep it as reference.
- Integration tests for API surfaces, unit tests for business logic, property tests for edge-case-heavy code.
- Run the full test suite before committing — never push untested code.
- Run the new test and confirm it fails for the right reason before writing the fix.
- If a test cannot be made to pass after three attempts, stop and report rather than skipping or weakening it.