TDD — Test-Driven Development
A test-driven development reference: the red-green loop, where tests live, and the anti-patterns that make tests worthless
- What
- A test-driven development reference: the red-green loop, where tests live, and the anti-patterns that make tests worthless
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a test-driven development reference skill that makes the red → green loop produce tests worth keeping. It defines what a good test is (behavior through public interfaces, reads like a specification), where tests go (at pre-agreed "seams" — the public boundary you test at, never internals, confirmed with you before any test is written), and the anti-patterns to avoid: implementation-coupled tests, tautological assertions, and horizontal slicing (bulk tests before implementation) instead of vertical tracer-bullet slices. Loop rules are strict: red before green, one slice at a time, and refactoring belongs to the review stage, not the loop. By @mattpocock, listed here with credit to its creator. Honest caveats: it's a discipline reference, not a test generator — it guides the loop but you still write the tests; it reads your project's CONTEXT.md and ADRs to match domain language, so it works best in a repo that has them. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "TDD — Test-Driven Development" for me. A test-driven development reference: the red-green loop, where tests live, and the anti-patterns that make tests worthless Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/tdd/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-tdd". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.