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:20260303.a0d3e9c, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4211 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
szoloth/skill-pack · 14 stars · license MIT · pushed 2026-09-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uyxvx6pef25ijycj
GET https://markdownregistry.com/api/v1/resolve?ref=szoloth/skill-pack/tdd
GET https://markdownregistry.com/api/v1/blob/1d0a1439aefa3ebe6a8fe83b5bb4559610d75268edd0bd4ef7d391d841742fc5
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.
szoloth/skill-pack · .agents/skills/pstack-full/SKILL.md · Full Poteto Mode and project notes for nontrivial engineering in skill-pack. Apply when planning, building, debugging…
szoloth/skill-pack · .agents/skills/pstack-project/SKILL.md · Apply pstack to Skill pack maintenance using its actual controls and local evidence boundaries.
szoloth/skill-pack · skills/agentic-review/SKILL.md · Deep multi-agent code review for local changes. Inspired by AmpCode's agentic review. Use when you want comprehensive…
szoloth/skill-pack · skills/b2b-expert-advisor/SKILL.md · B2B startup strategy advisor grounded in Lenny Rachitsky's 7-part series and April Dunford's positioning framework…
szoloth/skill-pack · skills/design-swarm/SKILL.md · Orchestrate a team of 10 design agents for holistic UI audit, ideation, and implementation.
Use when: "design swarm"…
szoloth/skill-pack · skills/doc-coauthoring/SKILL.md · Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation…
szoloth/skill-pack · skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
szoloth/skill-pack · skills/iterate/SKILL.md · Diverge-converge workflow: spin up N agents on isolated worktrees, each exploring a different approach to the same…
szoloth/skill-pack · skills/master/SKILL.md · Turn reference docs into active mastery through retrieval practice, case binding, and scenario simulation. Combines…
szoloth/skill-pack · skills/mcp-builder/SKILL.md · Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external…
szoloth/skill-pack · skills/napkin/SKILL.md · Maintain a per-repo napkin as a continuously curated runbook (not a session
log). Activates EVERY session. Read and…
szoloth/skill-pack · skills/orchestrating-swarms/SKILL.md · Master multi-agent orchestration using Claude Code's TeammateTool and Task system. Use when coordinating multiple…
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…
