agentleFS
eugnmueller-87eugnmueller-87/claude-blueprint/.claude/skills/tdd/SKILL.md

tdd

Skill1 starsChanged 5 months agoMITView on GitHub

Drive a Python change test-first — red/green/refactor, one behavior at a time. Write the failing pytest, watch it fail, write the minimal code to green, then refactor with the test as a net. Use when building new behavior where the spec is clear enough to express as a test. Trigger phrases "do this test-first", "tdd this", "build this with tests first".

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 187 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the ask has several behaviors, list them and do the first — one at a time.

    line 19
  2. Distinctive:

    GREEN — minimal code: Write the least code that makes the test pass.

    line 26
  3. Distinctive:

    REFACTOR — clean with the net: Remove duplication, improve names, extract only if it earns its keep (no premature abstraction).

    line 30
  4. Distinctive:

    Loop or stop: If more behaviors remain, go back to step 1 for the next one.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 187 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

tdd

Trigger: "do this test-first" / "tdd this" / "build this with tests first"

Standing rules: ../_conventions.md.

Design by test. Write the test before the code, one behavior per cycle. Never skip the red step — a test you never saw fail proves nothing. Never write ahead of the current failing test.

Steps

  1. Pick ONE behavior. State it as a single sentence: given X, when Y, then Z. If the ask has several behaviors, list them and do the first — one at a time.
  2. RED — write the failing test. A real pytest test naming the behavior (test_<behavior>), Arrange-Act-Assert, one assertion. Run it: pytest path/to/test_x.py::test_behavior. Confirm it FAILS, and fails for the right reason (assertion, not an import error). Show the failure.
  3. GREEN — minimal code. Write the least code that makes the test pass. Hardcode if that's genuinely the smallest step — the next test will force generality. Run the test: it passes. Show it green.
  4. REFACTOR — clean with the net. Remove duplication, improve names, extract only if it earns its keep (no premature abstraction). Re-run the test file after each change; it stays green. No new behavior in this step.
  5. Loop or stop. If more behaviors remain, go back to step 1 for the next one. Otherwise run the full test file once to confirm all green.
  6. Report (terse): behaviors covered · tests added · all green (with the run output). Never report green you didn't watch pass.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.