agentleFS
Sign inStart free
JustineDevsJustineDevs/meta-architect/skills/tdd/SKILL.md

tdd

Skill5 starsChanged 7 months agoMITView on GitHub

Use when the user wants regression-first or test-first scaffolding before implementation work expands.

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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill inside Codex when implementation should start by locking behavior with tests.

    line 8
  2. Distinctive:

    Prefer the smallest failing test that proves the requested behavior.

    line 21
  3. Very specific:

    Do not treat tdd as a replacement for the build gate.

    line 23
  4. Distinctive:

    Keep test intent explicit so the next implementation step stays narrow.

    line 24

“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

TDD

Use this skill inside Codex when implementation should start by locking behavior with tests. tdd is a non-gating helper skill that supports execution once the relevant lane is ready.

Output

Produce:

  • behavior to lock
  • minimal regression or failing test shape
  • implementation boundary
  • proof that the test belongs to the requested change
  • exact next trigger, usually the implementation lane or $cleanup

Rules

  • Prefer the smallest failing test that proves the requested behavior.
  • Lock current behavior before cleanup or refactor work when behavior is not already protected.
  • Do not treat tdd as a replacement for the build gate.
  • Keep test intent explicit so the next implementation step stays narrow.

Procedure

  1. Translate the requested behavior into one observable acceptance example.
  2. Choose the narrowest test boundary that fails before the fix and passes after it.
  3. Include the important negative or permission case without building a speculative suite.
  4. Name fixtures, dependencies, and cleanup requirements explicitly.
  5. Hand the locked behavior to the implementation lane and preserve the test as evidence.

Quality bar

  • The test proves user-visible or contract-visible behavior, not implementation trivia.
  • Failure output points to the intended boundary.
  • Tests do not mutate production systems, secrets, or unrelated user data.

Example

For a copy button, test clipboard content, keyboard activation, alignment-independent click behavior, and the visible success state rather than only asserting that a handler exists.

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