agentleFS
Sign inStart free
claude-worldclaude-world/director-mode-lite/skills/test-first/SKILL.md

test-first

Skill80 starsChanged 8 months agoMITView on GitHub

Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.

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 19 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:

    Write a failing test

    line 12
  2. Distinctive:

    Run test, confirm failure

    line 13
  3. Distinctive:

    Write minimal code to pass

    line 14
  4. Distinctive:

    Follow TDD strictly. No shortcuts.

    line 84

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

Implement TDD for: $ARGUMENTS

Quick Steps

  1. Write a failing test
  2. Run test, confirm failure
  3. Write minimal code to pass
  4. Refactor while keeping tests green
  5. Repeat

Red Phase - Write Failing Test

Test Design Principles

  • Test one specific behavior
  • Test name describes expected result
  • Test should fail (feature doesn't exist yet)

Must Test

  • Normal case
  • Edge cases
  • Error cases
  • Invalid input

Example

// auth/login.test.ts
it('should return JWT token for valid credentials', async () => {
  const res = await request(app)
    .post('/auth/login')
    .send({ email: 'test@example.com', password: 'password123' })

  expect(res.status).toBe(200)
  expect(res.body.token).toBeDefined()
})

Green Phase - Minimal Implementation

Implementation Principles

  • Write ONLY enough code to pass the test
  • Don't optimize yet
  • Don't worry about elegance
  • Just make it work

Refactor Phase - Clean Up

Refactoring Checklist

  • Is there code duplication?
  • Are variable names clear?
  • Are functions too long?
  • Is the logic too complex?

Refactoring Rules

  • Keep tests passing
  • Change one thing at a time
  • Run tests frequently

Test Quality Checklist

  • Unit tests cover core logic
  • Integration tests cover interactions
  • Test names clearly describe intent
  • Tests are independent and repeatable
  • Tests run fast (unit tests < 100ms)
  • Edge cases are covered

Follow TDD strictly. No shortcuts.

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