[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KN3H30KN5PJJS4JJ2FCSHZ":3,"skill-same:01M6KN3H30KN5PJJS4JJ2FCSHZ":98},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6KN3H30KN5PJJS4JJ2FCSHZ","tdd",null,"Build features or fix bugs test-first through agreed public interfaces using the red-green loop. Tested with Gemma4 E4B at 16K context and 24 tool rounds.","zhongkaifu\u002FTensorSharp","zhongkaifu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3347714?v=4","01M6KMY6F1P2PMX13BA17R8ZHE","Zhongkai Fu","01M6KMY6KB2CA5J6MW78KVWVNB",677,"MIT","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002FSKILL.md",[],[5,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"file tools","test-first","gemma4","features","bugs","for","at","e2b","fix bugs","token","green","up","fix","context","tool","loop","Tools","file","artifacts","code","2026-11-10 10:12:30",false,"---\nname: tdd\ndescription: Build features or fix bugs test-first through agreed public interfaces using the red-green loop. Tested with Gemma4 E4B at 16K context and 24 tool rounds.\nlicense: MIT\ncompatibility: TensorSharp or TensorAgent; workspace file tools required for saved artifacts and code changes. Tested on Gemma4 E4B Q8_0 with 16384-token context and up to 24 tool rounds. E2B failed the earlier eight-round task; E2B at 24 rounds and other models are not validated.\nmetadata:\n  source: mattpocock\u002Fskills\n  revision: 49dd158d1076134a641b33efb035946536778336\n---\n\n# Test-Driven Development\n\nTDD is the red → green 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 `GLOSSARY.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 it 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, so 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?\" Give each proposed seam a one-line note on what it catches and what it misses.\n\nWhen the shape of that interface is itself in question (how deep the module is, where the seam belongs, what the interface should expose), read `skills_read` with `skill=\"tdd\"`, `path=\"codebase-design.md\"` for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.\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 before green.** Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Refactoring is not part of the loop.** It belongs to the review stage (review the agreed public interface and test results with the user), not the red → green implementation cycle.\n\n## Execute and prove each cycle\n\nFor an approved interface, first create one public test and the minimal failing implementation (for example a stub). Run that test with the offered shell tool and confirm its real failure before implementing the behavior. A test name containing 'red' is not evidence of a red run. Implement only that slice and run it again to prove green; then repeat for the remaining agreed behavior. Report actual failing and passing command results, never inferred outcomes or runs you did not perform.\n\n## Host capabilities\n\nUse only tools offered in this conversation. Read supplied workspace files with `read_file`; create artifacts with `write_file` and edit existing files with `apply_patch` when offered. Do not invent a `Skill` tool. After creating any file, include its exact Markdown download link from the tool result in your answer, even when the rest of your answer asks the user a decision question. Never replace that link with a filename or a claim that the file exists. If a required file, workspace, executable, or tool is unavailable, explain the limitation and do not claim it ran. A user's already-agreed scope and test interface count as agreement; do not ask the same question again. Apply the workflow directly after reading it; keep progress narration brief.\n","# Test-Driven Development\n\nTDD is the red → green 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 `GLOSSARY.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 it 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, so 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?\" Give each proposed seam a one-line note on what it catches and what it misses.\n\nWhen the shape of that interface is itself in question (how deep the module is, where the seam belongs, what the interface should expose), read `skills_read` with `skill=\"tdd\"`, `path=\"codebase-design.md\"` for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.\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 before green.** Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Refactoring is not part of the loop.** It belongs to the review stage (review the agreed public interface and test results with the user), not the red → green implementation cycle.\n\n## Execute and prove each cycle\n\nFor an approved interface, first create one public test and the minimal failing implementation (for example a stub). Run that test with the offered shell tool and confirm its real failure before implementing the behavior. A test name containing 'red' is not evidence of a red run. Implement only that slice and run it again to prove green; then repeat for the remaining agreed behavior. Report actual failing and passing command results, never inferred outcomes or runs you did not perform.\n\n## Host capabilities\n\nUse only tools offered in this conversation. Read supplied workspace files with `read_file`; create artifacts with `write_file` and edit existing files with `apply_patch` when offered. Do not invent a `Skill` tool. After creating any file, include its exact Markdown download link from the tool result in your answer, even when the rest of your answer asks the user a decision question. Never replace that link with a filename or a claim that the file exists. If a required file, workspace, executable, or tool is unavailable, explain the limitation and do not claim it ran. A user's already-agreed scope and test interface count as agreement; do not ask the same question again. Apply the workflow directly after reading it; keep progress narration brief.\n",{"name":5,"license":15,"metadata":45,"description":7,"compatibility":48},{"source":46,"revision":47},"mattpocock\u002Fskills","49dd158d1076134a641b33efb035946536778336","TensorSharp or TensorAgent; workspace file tools required for saved artifacts and code changes. Tested on Gemma4 E4B Q8_0 with 16384-token context and up to 24 tool rounds. E2B failed the earlier eight-round task; E2B at 24 rounds and other models are not validated.","main","2369f533b0a00861d0deee7739ec28671a1a7897","TensorAgent\u002Fskills\u002Ftdd",73,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp","https:\u002F\u002Ftensorsharp.ai","https:\u002F\u002Fgithub.com\u002Fzhongkaifu","2026-11-13 03:53:42",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add zhongkaifu\u002FTensorSharp --skill tdd",{"tool":63,"command":64},"bunx","bunx skills add zhongkaifu\u002FTensorSharp --skill tdd",{"tool":66,"command":67},"pnpm","pnpm dlx skills add zhongkaifu\u002FTensorSharp --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002FSKILL.md",true,[71,77,81,85,90,94],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"codebase-design.md","REFERENCE","参考文档",6136,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002Fcodebase-design.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"DEEPENING.md",2573,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002FDEEPENING.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"DESIGN-IT-TWICE.md",2857,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002FDESIGN-IT-TWICE.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1068,{"path":91,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":92,"sourceHtmlUrl":93},"mocking.md",1481,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002Fmocking.md",{"path":95,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":96,"sourceHtmlUrl":97},"tests.md",2214,"https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftdd\u002Ftests.md",[99,130,159,189,215,241],{"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":103,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":40},"01M6KN3TFVCZHZMDB6JYHSCFTT","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[113,114,38,115,116,117,118,119,120,121,122,123,36,124,125,126,127,25,128,129],"web artifacts builder","web","artifacts builder","builder","frontend","css","components","react","component","shadcn","ui","Tailwind","html","single-file","ui components","jsx","suite",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":40},"01M6KN3P30A9VG3459BQMD1QQB","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000015","视觉设计",[141,142,143,144,145,38,146,147,148,149,125,150,151,152,153,154,155,156,25,157,158],"theme factory","factory","theme","toolkit","generate","SET","fly","slides","landing","styling","artifact","pages","themes","you","fonts","can","apply","new",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":172,"publishedAt":40},"01M6KN3AGP5G5KT8NY4WA7FHM1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[166,169],{"categoryNo":167,"categoryName":168,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":170,"categoryName":171,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000016","图像与多媒体",[173,174,175,176,177,36,178,179,180,181,182,183,184,185,186,25,187,188],"slack gif creator","slack","gif","creator","validation","constraints","Animation","knowledge","use","me","users","make","Utilities","concepts","request","when",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":40},"01M6KN2RSKQ19P9SGZ5CGJCC7S","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Finternal-comms\u002FSKILL.md",[196],{"categoryNo":167,"categoryName":168,"taxonomyType":110,"taxonomyTypeDesc":111},[198,199,200,201,146,202,181,203,182,204,205,206,207,208,209,210,211,212,213,214],"internal comms","comms","status","help","write","reports","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates","company",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":229,"publishedAt":40},"01M6KN13V1EK7HHG19QQDBW8QH","frontend-design","Design distinctive UI with intentional aesthetics and typography. Read the workflow first; save HTML with the offered file tool and return its download link.","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[222,223,224],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},{"categoryNo":138,"categoryName":139,"taxonomyType":110,"taxonomyTypeDesc":111},{"categoryNo":225,"categoryName":226,"taxonomyType":227,"taxonomyTypeDesc":228},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[117,230,231,232,37,123,233,234,34,235,236,237,125,238,239,240],"design","frontend design","workflow","first","save","download","read","typography","link","aesthetics","with",{"skillNo":242,"name":243,"nameZh":6,"description":244,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":245,"sourceHtmlUrl":246,"categories":247,"keywords":253,"publishedAt":40},"01M6KMZF30TZEPM9ZMYMJKXBW6","canvas-design","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fcanvas-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongkaifu\u002FTensorSharp\u002Fblob\u002Fmain\u002FTensorAgent\u002Fskills\u002Fcanvas-design\u002FSKILL.md",[248,251,252],{"categoryNo":249,"categoryName":250,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":138,"categoryName":139,"taxonomyType":110,"taxonomyTypeDesc":111},{"categoryNo":225,"categoryName":226,"taxonomyType":227,"taxonomyTypeDesc":228},[230,254,255,256,257,258,259,260,261,262,181,263,264,265,266,267,154,268,269,270,188],"canvas design","canvas","PDF","design philosophy","documents","create","png","work","user","never","Art","philosophy","visual","poster","Existing","static","copyright"]