Claude Cursor opencode Skill

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download innei-ryugi-docs_ryugi_skill-evals_2026-11-13-test-driven-development-slim_skills_candidate-fe17c7b.zip · 6 KB

Install

skills CLI npx skills add https://github.com/Innei/ryugi/tree/main/docs/ryugi/skill-evals/2026-11-13-test-driven-development-slim/skills/candidate
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install innei-ryugi@llmmart
Git git clone https://github.com/Innei/ryugi.git

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

Skill manifest

Test-Driven Development (TDD)

Overview

Write the test first. Watch it fail. Write minimal code to pass.

Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.

Violating the letter of the rules is violating the spirit of the rules.

When to Use

Always:

  • New features
  • Bug fixes
  • Refactoring
  • Behavior changes

Exceptions (ask your human partner):

  • Throwaway prototypes
  • Generated code
  • Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

Before the first edit: ryugi:using-git-worktrees decides where the work happens, unless ryugi:executing-specs already did at its Setup.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? Delete it. Start over.

No exceptions:

  • Don't keep it as "reference"
  • Don't "adapt" it while writing tests
  • Don't look at it
  • Delete means delete

Implement fresh from tests. Period.

No exceptions without your human partner's permission.

Red-Green-Refactor

RED: write a failing test → verify it fails correctly → GREEN: minimal code → verify it passes, all green → REFACTOR: clean up, stay green → next test.

RED - Write Failing Test

Write one minimal test showing what should happen.

Requirements:

  • One behavior
  • Clear name
  • Real code (no mocks unless unavoidable)

Verify RED - Watch It Fail

MANDATORY. Never skip.

npm test path/to/test.test.ts

Confirm:

  • Test fails (not errors)
  • Failure message is expected
  • Fails because feature missing (not typos)

Test passes? You're testing existing behavior. Fix test.

Test errors? Fix error, re-run until it fails correctly.

GREEN - Minimal Code

Write simplest code to pass the test.

Don't add features, refactor other code, or "improve" beyond the test.

Verify GREEN - Watch It Pass

MANDATORY.

npm test path/to/test.test.ts

Confirm:

  • Test passes
  • Other tests still pass
  • Output pristine (no errors, warnings)

Test fails? Fix code, not test.

Other tests fail? Fix now.

"Other tests" means the project's suite, not just your file. A green run of the test you wrote is not a green suite. Before you call the change done, run the project's test command (bare pytest, npm test, cargo test — whatever the repo uses) even when your task named only one test file. A scope statement in your task bounds the deliverable, not your verification. Any failure that run shows — including one you didn't cause — goes in your report by name; a red test you watched scroll past and didn't mention is a report falsified by omission.

REFACTOR - Clean Up

After green only:

  • Remove duplication
  • Improve names
  • Extract helpers

Keep tests green. Don't add behavior.

Repeat

Next failing test for next feature.

Good Tests

Quality Good Bad
Minimal One thing. "and" in name? Split it. test('validates email and domain and whitespace')
Clear Name describes behavior test('test1')
Shows intent Demonstrates desired API Obscures what code should do

When writing or changing any test, read writing-good-tests.md for the rules that keep tests honest:

  • Name the production change that would make the test fail — before writing it
  • Assert on real behavior, never on mock behavior
  • Keep test-only code in test utilities, out of production classes
  • Understand a dependency's side effects before mocking it

Common Rationalizations

Excuse Reality
"Too simple to test" Simple code breaks. Test takes 30 seconds.
"I'll test after" Tests written after pass immediately, which proves nothing. You never watched them catch the bug.
"Tests after achieve same goals (spirit not ritual)" Tests-after answer "what does this do?"; tests-first answer "what should this do?" You verify the cases you remembered, not the ones you'd have discovered.
"Already manually tested" Ad-hoc: no record, no re-run when the code changes. "Worked when I tried it" is not a test.
"Deleting X hours is wasteful" Sunk cost. That time is spent either way; keeping code you can't trust is the waste.
"Keep as reference, write tests first" You'll adapt it. That's testing after. Delete means delete.
"Need to explore first" Fine. Throw away exploration, start with TDD.
"Test hard = design unclear" Listen to test. Hard to test = hard to use.
"TDD will slow me down" Debugging in production is slower. TDD catches it before commit.
"Manual test faster" Manual doesn't prove edge cases. You'll re-test every change.
"Existing code has no tests" You're improving it. Add tests for existing code.

Red Flags - STOP and Start Over

  • Code before test
  • Test passes immediately
  • Can't explain why test failed
  • Rationalizing "just this once"
  • "This is different because..."
  • Any excuse in the table above

All of these mean: Delete code. Start over with TDD.

When Stuck

Problem Solution
Don't know how to test Write wished-for API. Write assertion first. Ask your human partner.
Test too complicated Design too complicated. Simplify interface.
Must mock everything Code too coupled. Use dependency injection.
Test setup huge Extract helpers. Still complex? Simplify design.

Debugging Integration

Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.

Never fix bugs without a test.

Files (ryugi)
  • SKILL.md 7.7 KB
    ---
    name: test-driven-development
    description: Use when implementing any feature or bugfix, before writing implementation code
    ---
    
    # Test-Driven Development (TDD)
    
    ## Overview
    
    Write the test first. Watch it fail. Write minimal code to pass.
    
    **Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.
    
    **Violating the letter of the rules is violating the spirit of the rules.**
    
    ## When to Use
    
    **Always:**
    
    - New features
    - Bug fixes
    - Refactoring
    - Behavior changes
    
    **Exceptions (ask your human partner):**
    
    - Throwaway prototypes
    - Generated code
    - Configuration files
    
    Thinking "skip TDD just this once"? Stop. That's rationalization.
    
    **Before the first edit:** ryugi:using-git-worktrees decides where the
    work happens, unless ryugi:executing-specs already did at its Setup.
    
    ## The Iron Law
    
    ```
    NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
    ```
    
    Write code before the test? Delete it. Start over.
    
    **No exceptions:**
    
    - Don't keep it as "reference"
    - Don't "adapt" it while writing tests
    - Don't look at it
    - Delete means delete
    
    Implement fresh from tests. Period.
    
    No exceptions without your human partner's permission.
    
    ## Red-Green-Refactor
    
    RED: write a failing test → verify it fails correctly → GREEN: minimal
    code → verify it passes, all green → REFACTOR: clean up, stay green →
    next test.
    
    ### RED - Write Failing Test
    
    Write one minimal test showing what should happen.
    
    **Requirements:**
    
    - One behavior
    - Clear name
    - Real code (no mocks unless unavoidable)
    
    ### Verify RED - Watch It Fail
    
    **MANDATORY. Never skip.**
    
    ```bash
    npm test path/to/test.test.ts
    ```
    
    Confirm:
    
    - Test fails (not errors)
    - Failure message is expected
    - Fails because feature missing (not typos)
    
    **Test passes?** You're testing existing behavior. Fix test.
    
    **Test errors?** Fix error, re-run until it fails correctly.
    
    ### GREEN - Minimal Code
    
    Write simplest code to pass the test.
    
    Don't add features, refactor other code, or "improve" beyond the test.
    
    ### Verify GREEN - Watch It Pass
    
    **MANDATORY.**
    
    ```bash
    npm test path/to/test.test.ts
    ```
    
    Confirm:
    
    - Test passes
    - Other tests still pass
    - Output pristine (no errors, warnings)
    
    **Test fails?** Fix code, not test.
    
    **Other tests fail?** Fix now.
    
    **"Other tests" means the project's suite, not just your file.** A
    green run of the test you wrote is not a green suite. Before you call
    the change done, run the project's test command (bare `pytest`,
    `npm test`, `cargo test` — whatever the repo uses) even when your task
    named only one test file. A scope statement in your task bounds the
    deliverable, not your verification. Any failure that run shows —
    including one you didn't cause — goes in your report by name; a red
    test you watched scroll past and didn't mention is a report falsified
    by omission.
    
    ### REFACTOR - Clean Up
    
    After green only:
    
    - Remove duplication
    - Improve names
    - Extract helpers
    
    Keep tests green. Don't add behavior.
    
    ### Repeat
    
    Next failing test for next feature.
    
    ## Good Tests
    
    | Quality          | Good                                | Bad                                                 |
    | ---------------- | ----------------------------------- | --------------------------------------------------- |
    | **Minimal**      | One thing. "and" in name? Split it. | `test('validates email and domain and whitespace')` |
    | **Clear**        | Name describes behavior             | `test('test1')`                                     |
    | **Shows intent** | Demonstrates desired API            | Obscures what code should do                        |
    
    When writing or changing any test, read [writing-good-tests.md](writing-good-tests.md) for the rules that keep tests honest:
    
    - Name the production change that would make the test fail — before writing it
    - Assert on real behavior, never on mock behavior
    - Keep test-only code in test utilities, out of production classes
    - Understand a dependency's side effects before mocking it
    
    ## Common Rationalizations
    
    | Excuse                                               | Reality                                                                                                                                                     |
    | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | "Too simple to test"                                 | Simple code breaks. Test takes 30 seconds.                                                                                                                  |
    | "I'll test after"                                    | Tests written after pass immediately, which proves nothing. You never watched them catch the bug.                                                           |
    | "Tests after achieve same goals (spirit not ritual)" | Tests-after answer "what does this do?"; tests-first answer "what should this do?" You verify the cases you remembered, not the ones you'd have discovered. |
    | "Already manually tested"                            | Ad-hoc: no record, no re-run when the code changes. "Worked when I tried it" is not a test.                                                                 |
    | "Deleting X hours is wasteful"                       | Sunk cost. That time is spent either way; keeping code you can't trust is the waste.                                                                        |
    | "Keep as reference, write tests first"               | You'll adapt it. That's testing after. Delete means delete.                                                                                                 |
    | "Need to explore first"                              | Fine. Throw away exploration, start with TDD.                                                                                                               |
    | "Test hard = design unclear"                         | Listen to test. Hard to test = hard to use.                                                                                                                 |
    | "TDD will slow me down"                              | Debugging in production is slower. TDD catches it before commit.                                                                                            |
    | "Manual test faster"                                 | Manual doesn't prove edge cases. You'll re-test every change.                                                                                               |
    | "Existing code has no tests"                         | You're improving it. Add tests for existing code.                                                                                                           |
    
    ## Red Flags - STOP and Start Over
    
    - Code before test
    - Test passes immediately
    - Can't explain why test failed
    - Rationalizing "just this once"
    - "This is different because..."
    - Any excuse in the table above
    
    **All of these mean: Delete code. Start over with TDD.**
    
    ## When Stuck
    
    | Problem                | Solution                                                             |
    | ---------------------- | -------------------------------------------------------------------- |
    | Don't know how to test | Write wished-for API. Write assertion first. Ask your human partner. |
    | Test too complicated   | Design too complicated. Simplify interface.                          |
    | Must mock everything   | Code too coupled. Use dependency injection.                          |
    | Test setup huge        | Extract helpers. Still complex? Simplify design.                     |
    
    ## Debugging Integration
    
    Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.
    
    Never fix bugs without a test.
    
  • writing-good-tests.md 8.5 KB
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.