[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79S2Y3CWDAW783ZGE2HMMB0":3,"skill-same:01M79S2Y3CWDAW783ZGE2HMMB0":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79S2Y3CWDAW783ZGE2HMMB0","tdd",null,"Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","EnzoTironi\u002Fskills","EnzoTironi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F97469972?v=4","01M79S0WRXK376E007TTT8TF5N","Enzo Tironi","01M79S0WSJZDCANYA8172QCTVJ",0,"MIT","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tdd\ndescription: Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.\n---\n\n# Test-Driven Development\n\nTDD is the red → green → refactor loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle — consult them before and during the loop, not after.\n\nWhen exploring the codebase, read `CONTEXT.md` (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.\n\n## What a good test is\n\nTests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification — \"user can checkout with valid cart\" tells you exactly what capability exists — and survives refactors because it doesn't care about internal structure.\n\nSee [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.\n\n## Seams — where tests go\n\nA **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.\n\n**Test only at pre-agreed seams.** Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything — agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.\n\nAsk: \"What's the public interface, and which seams should we test?\"\n\n## Anti-patterns\n\n- **Implementation-coupled** — mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.\n- **Tautological** — the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth — a known-good literal, a worked example, the spec.\n- **Horizontal slicing** — writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead — one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you.\n\n## Rules of the loop\n\n- **Red for the expected reason.** Write the failing test first and run it. Confirm that it fails because the requested behavior is absent, not because the test is broken.\n- **Green with the minimum change.** Write only enough production code to pass the new test. Don't anticipate future tests or add speculative features.\n- **Refactor while green.** Improve the design immediately after green and before the next red. Keep behavior unchanged and rerun the focused tests after each small transformation.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Keep slices releasable.** Do not leave the branch with a known failing test, a half-migrated interface, or production behavior that depends on a later slice.\n- **Escalate large refactors.** If a refactor cannot stay small and behavior-preserving, stop the loop and plan it as separate work with characterization tests. Use `$code-review` after the completed slices; review complements refactoring and does not replace it.\n","# Test-Driven Development\n\nTDD is the red → green → refactor loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle — consult them before and during the loop, not after.\n\nWhen exploring the codebase, read `CONTEXT.md` (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.\n\n## What a good test is\n\nTests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification — \"user can checkout with valid cart\" tells you exactly what capability exists — and survives refactors because it doesn't care about internal structure.\n\nSee [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.\n\n## Seams — where tests go\n\nA **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.\n\n**Test only at pre-agreed seams.** Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything — agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.\n\nAsk: \"What's the public interface, and which seams should we test?\"\n\n## Anti-patterns\n\n- **Implementation-coupled** — mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.\n- **Tautological** — the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth — a known-good literal, a worked example, the spec.\n- **Horizontal slicing** — writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead — one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you.\n\n## Rules of the loop\n\n- **Red for the expected reason.** Write the failing test first and run it. Confirm that it fails because the requested behavior is absent, not because the test is broken.\n- **Green with the minimum change.** Write only enough production code to pass the new test. Don't anticipate future tests or add speculative features.\n- **Refactor while green.** Improve the design immediately after green and before the next red. Keep behavior unchanged and rerun the focused tests after each small transformation.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Keep slices releasable.** Do not leave the branch with a known failing test, a half-migrated interface, or production behavior that depends on a later slice.\n- **Escalate large refactors.** If a refactor cannot stay small and behavior-preserving, stop the loop and plan it as separate work with characterization tests. Use `$code-review` after the completed slices; review complements refactoring and does not replace it.\n",{"name":5,"description":7},"main","936a01cfff0d181de38adab29ead3ba52d29741a",".agents\u002Fskills\u002Ftdd","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills","https:\u002F\u002Fgithub.com\u002FEnzoTironi","2026-08-13 01:38:50",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add EnzoTironi\u002Fskills --skill tdd",{"tool":36,"command":37},"bunx","bunx skills add EnzoTironi\u002Fskills --skill tdd",{"tool":39,"command":40},"pnpm","pnpm dlx skills add EnzoTironi\u002Fskills --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",299,"https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"mocking.md",1481,"https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Fmocking.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"tests.md",2214,"https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Ftests.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79S3EZ16NB5C56AKQ5XBSP6","zoen-product-engineering","Orchestrate Zoen product engineering from discovery to production using the curated Matt Pocock skill set, Extreme Programming, ontology-first architecture, and risk-controlled delivery. Use for any Zoen product, architecture, feature, bug, refactor, AI-agent, integration, release, or engineering-workflow decision, especially nouns-links-verbs-evidence, AgentRun\u002FToolCall, Action Gateway, approvals, audit and provenance, tenancy, client-owned export, or production readiness.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoen-product-engineering\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79S3CEQ5XBEYR5NC78V5BEY","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79S39T2XDFPCZZ9YR9XWGED","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79S37NCKFNDXRDN1FS6JJTE","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79S34BGWQYF0KB77YHZ27ZD","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79S317JQ7N93MJCTP2A1FMT","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FEnzoTironi\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[]]