[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KX0RAT6897FJX1QR4BBGXB":3,"skill-same:01M6KX0RAT6897FJX1QR4BBGXB":80},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6KX0RAT6897FJX1QR4BBGXB","tdd",null,"Test-driven development with a red-green loop, one vertical slice at a time, plus what makes a test worth keeping. Use when building a feature or fixing a bug test-first, when the user mentions TDD or red-green-refactor, when writing integration tests, and when another skill implements a change at an agreed seam.","dougborg\u002Fharness-kit","dougborg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1261222?v=4","01M6KWS4PB51EYD4ZDJJSGNGB2","Doug Borg","01M6KWS4T8ZZW6SX5QZS9B5BN2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftdd\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"at","writing","with","vertical slice","feature","tests","time","green","another skill","bug","red-green-refactor","use","loop","first","integration","development","integration tests","change","test","2026-11-10 10:12:30",false,"---\nname: tdd\ndescription: >-\n  Test-driven development with a red-green loop, one vertical slice at a time,\n  plus what makes a test worth keeping. Use when building a feature or fixing a\n  bug test-first, when the user mentions TDD or red-green-refactor, when\n  writing integration tests, and when another skill implements a change at an\n  agreed seam.\n---\n\n# Test-Driven Development\n\nTDD is the **red → green** loop. This skill is the reference that makes the\nloop produce tests worth keeping.\n\nRead the project's `GLOSSARY.md` (if any) so test names use the domain's\nwords, and respect ADRs in the area you're changing.\n\n## Agree the seams first\n\nA **seam** is the public interface you test at: where you observe behaviour\nwithout reaching inside. Before writing any test, list the seams you intend to\ntest and confirm them with the user. You can't test everything; agreeing the\nseams up front puts the effort on critical paths and complex logic. When the\nshape of the interface itself is in question (how deep the module is, where\nthe seam belongs), call the Skill tool with \"codebase-design\" for the\nvocabulary.\n\nDone when the user has confirmed the seams, or the task names them already.\n\n## The loop\n\n1. **Red.** Write one failing test at an agreed seam, for one behaviour. Done\n   when you have run it and seen it fail for the reason you expect.\n2. **Green.** Write only enough code to pass it: no code for tests you haven't\n   written yet. Done when the test and its neighbours pass.\n3. Repeat with the next behaviour.\n\nWork in **vertical slices**: one test, one implementation, then the next, each\ntest a **tracer bullet** that responds to what the last cycle taught you.\nWriting all the tests first and then all the code tests imagined behaviour and\nlocks in a structure before you understand it.\n\nRefactor after green as its own step, or leave it to review (the\ncode-reviewer skill), never inside the red-green cycle.\n\n## What a good test is\n\nA good test exercises behaviour through the public interface and reads like a\nspecification: \"user can check out with a valid cart\". It survives a rewrite\nof the internals because it never looked at them. Examples are in\n[tests.md](tests.md); when and how to mock is in [mocking.md](mocking.md).\n\nThree anti-patterns, each with its tell:\n\n- **Implementation-coupled:** mocks internal collaborators, tests private\n  methods, or checks results through a side channel (querying the database\n  instead of the interface). Tell: it breaks when you refactor and behaviour\n  hasn't changed.\n- **Tautological:** the expected value is computed the way the code computes\n  it (`expect(add(a, b)).toBe(a + b)`), so it passes by construction. Take\n  expected values from an independent source: a known literal, a worked\n  example, the spec.\n- **Unfalsifiable:** it can't fail when the defect it targets is present. The\n  red step proves this for a test written first; for a test written after the\n  code, break the code it covers and watch the test go red before trusting\n  it.\n","# Test-Driven Development\n\nTDD is the **red → green** loop. This skill is the reference that makes the\nloop produce tests worth keeping.\n\nRead the project's `GLOSSARY.md` (if any) so test names use the domain's\nwords, and respect ADRs in the area you're changing.\n\n## Agree the seams first\n\nA **seam** is the public interface you test at: where you observe behaviour\nwithout reaching inside. Before writing any test, list the seams you intend to\ntest and confirm them with the user. You can't test everything; agreeing the\nseams up front puts the effort on critical paths and complex logic. When the\nshape of the interface itself is in question (how deep the module is, where\nthe seam belongs), call the Skill tool with \"codebase-design\" for the\nvocabulary.\n\nDone when the user has confirmed the seams, or the task names them already.\n\n## The loop\n\n1. **Red.** Write one failing test at an agreed seam, for one behaviour. Done\n   when you have run it and seen it fail for the reason you expect.\n2. **Green.** Write only enough code to pass it: no code for tests you haven't\n   written yet. Done when the test and its neighbours pass.\n3. Repeat with the next behaviour.\n\nWork in **vertical slices**: one test, one implementation, then the next, each\ntest a **tracer bullet** that responds to what the last cycle taught you.\nWriting all the tests first and then all the code tests imagined behaviour and\nlocks in a structure before you understand it.\n\nRefactor after green as its own step, or leave it to review (the\ncode-reviewer skill), never inside the red-green cycle.\n\n## What a good test is\n\nA good test exercises behaviour through the public interface and reads like a\nspecification: \"user can check out with a valid cart\". It survives a rewrite\nof the internals because it never looked at them. Examples are in\n[tests.md](tests.md); when and how to mock is in [mocking.md](mocking.md).\n\nThree anti-patterns, each with its tell:\n\n- **Implementation-coupled:** mocks internal collaborators, tests private\n  methods, or checks results through a side channel (querying the database\n  instead of the interface). Tell: it breaks when you refactor and behaviour\n  hasn't changed.\n- **Tautological:** the expected value is computed the way the code computes\n  it (`expect(add(a, b)).toBe(a + b)`), so it passes by construction. Take\n  expected values from an independent source: a known literal, a worked\n  example, the spec.\n- **Unfalsifiable:** it can't fail when the defect it targets is present. The\n  red step proves this for a test written first; for a test written after the\n  code, break the code it covers and watch the test go red before trusting\n  it.\n",{"name":5,"description":7},"main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","skills\u002Fengineering\u002Ftdd",1,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit","https:\u002F\u002Fgithub.com\u002Fdougborg","http:\u002F\u002Fdougborg.org","Platforms and Infrastructure Software Engineer","2026-11-13 07:43:37",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add dougborg\u002Fharness-kit --skill tdd",{"tool":58,"command":59},"bunx","bunx skills add dougborg\u002Fharness-kit --skill tdd",{"tool":61,"command":62},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftdd\u002FSKILL.md",true,[66,72,76],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",121,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftdd\u002Fagents\u002Fopenai.yaml",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"mocking.md",1173,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftdd\u002Fmocking.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"tests.md",1947,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftdd\u002Ftests.md",[81,99,120,151,173,190],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":38},"01M6KX4J65S5FZKMSN5DQNPSZM","teach","Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fteach\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[83,93,94,21,95,96,97,98],"lessons","you","learned","record","references","sessions",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":110,"publishedAt":38},"01M6KX4FSSG7MHF00JDT5QT0BQ","svg-logo-designer","Generate SVG logos with multiple concepts, layouts, and color variations.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fsvg-logo-designer\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[111,112,113,114,115,116,21,117,118,119],"logo","designer","svg logo designer","SVG","color","concepts","write","read","generate",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":132,"publishedAt":38},"01M6KX4BD3J9MZPPSH4MENH7FP","documentation-writer","Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use \u002Fskill-writer instead.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":130,"categoryName":131,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000036","内容创作者",[133,134,135,136,137,138,139,140,30,141,142,143,144,145,146,147,148,149,150,20],"writer","documentation writer","documentation","entries","changelog","architecture","document","files","question","README","notes","code","examples","pages","for","information","guides","type",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":38},"01M6KX47ZJ4ZWHDN3MY8SYAWZZ","adhd-mode","Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says \"stop adhd mode\". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fadhd-mode\u002FSKILL.md",[],[158,159,160,161,147,162,163,21,164,165,166,25,167,168,169,170,32,171,172,144],"adhd","mode","adhd mode","next","action","kit","output","style","progress","back","stop","session","reader","REST","harness",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":38},"01M6KX463Z6E18EPDW873GDHKB","wait-what","That last message didn't land: re-explain it with the missing context.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fwait-what\u002FSKILL.md",[],[180,181,182,21,183,184,185,186,187,188,189],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":38},"01M6KX43NE1NB0Y2HECY515730","to-questionnaire","Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",[],[197,198,147,199,200,201,202,94,203,183,204,205],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]