Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Test-Driven Development
## Philosophy
**Core principle**: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't.
**Good tests** are integration-style: they exercise real code paths through public APIs. They describe _what_ the system does, not _how_ it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure.
**Bad tests** are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means (like querying a database directly instead of using the interface). The warning sign: your test breaks when you refactor, but behavior hasn't changed. If you rename an internal function and tests fail, those tests were testing implementation, not behavior.
See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.
## Anti-Pattern: Horizontal Slices
…
The line at the top of this page pins the label git:20260520.77c7886, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_5ytuftxyluks6c3z
GET https://markdownregistry.com/api/v1/resolve?ref=lythos-labs/lythoskill/tdd
GET https://markdownregistry.com/api/v1/blob/af059705061156fd4845ddbb736fe92b564118ac5f03551e09ef9e8f6d970638
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
lythos-labs/lythoskill · packages/lythoskill-arena/skill/SKILL.md · Test play for skills and deck configurations. DEFAULT: agent reads
config, spawns parallel subagents via native Agent…
lythos-labs/lythoskill · packages/lythoskill-creator/skill/SKILL.md · Scaffold and build projects for the lythoskill ecosystem only.
Creates thin-skill monorepos: heavy logic in npm…
lythos-labs/lythoskill · packages/lythoskill-deck/skill/SKILL.md · Declarative skill deck governance. `deck link` reconciles the working set
to match skill-deck.toml — deny-by-default…
lythos-labs/lythoskill · packages/lythoskill-hello-world/skill/SKILL.md · A minimal hello-world skill. No scripts, no dependencies.
Demonstrates the simplest possible thin-skill: just a…
lythos-labs/lythoskill · packages/lythoskill-project-cortex/skill/SKILL.md · Register tasks BEFORE fixing bugs. Close epics when work is done.
Always move state through the CLI — never mv files by…
cursor/plugins · pstack/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
cursor/plugins · harness/pstack/claude-code/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
michael-denyer/pstack-claude · plugins/pstack/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
backnotprop/pstack · skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
