agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/06-test/tdd/SKILL.md

tdd

Skill3 starsChanged 29 days agoMITView on GitHub

Implement behavior through a focused red-green-refactor loop. Triggers on "tdd", "测试驱动开发".

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-Vibe-CompanySkill

    capture-learning-tools

    Turn technical conversations, bugs, CI failures, review comments,

    Also in 5 projects that use this

  • The-Vibe-CompanySkill

    design-frontend-dev

    Clean Impeccable frontend design skill. Use when the user wants to

    Also in 5 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 14 projects that use this

  • jaydubya818Skill

    figure-it-out

    Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.

    Also in 54 projects that use this

  • jaydubya818Skill

    principle-laziness-protocol

    Apply when a refactor is adding wrappers or abstractions instead of simplifying.

    Also in 45 projects that use this

  • +2 more from The-Vibe-Company
  • +5 more from jaydubya818

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 1

    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:

    Write one behavior test, run it and confirm failure from missing or incorrect behavior rather than harness errors.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 186 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

Test-Driven Development

When to use

  • Implement behavior through a focused red-green-refactor loop.

Not for: implement for planned delivery; test-generation for existing behavior.

Steps

  1. Find real commands, layout and public seam; use real code and controlled data, disclosing external substitutes.
  2. Write one behavior test, run it and confirm failure from missing or incorrect behavior rather than harness errors.
  3. Implement minimally, run the focused test and relevant regressions, and refactor while green.
  4. Repeat for the next behavior and finish relevant verification; report observed red/green evidence and commit only on request.

Verify

  • A meaningful failure preceded the passing fix; assertions use independent expected behavior and checks are not disabled.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • references/test-strategy.md — test pyramid, test-double hierarchy (Real > Fake > Stub > Mock), DAMP over DRY
  • references/testing-anti-patterns.md — mock misuse, test-only methods, partial mocks, gate functions
  • references/mocking.md — when to mock, designing for mockability
  • references/good-tests.md — good vs bad test examples, tautological tests

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.

Check your setup, free