[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDHE62H14DWH2H8XA6DST9":3,"skill-same:01M6PDHE62H14DWH2H8XA6DST9":81},{"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":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6PDHE62H14DWH2H8XA6DST9","tdd",null,"Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.","stevesolun\u002Fctx","stevesolun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1304538?v=4","01M6PDDJQ35XAXMPJQP8YG3P2X","Steve Solun","01M6PDDJVJ663A3CMV7XQN9XAY",593,"MIT","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"use","test-first","test-driven","apply","with","loops","tests","green","build","red-green-refactor","fix","behavior","feedback","first","refactor","integration","development","integration tests","test","2026-11-10 10:12:30",false,"---\nname: tdd\ndescription: Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.\n---\n\n# Test-Driven Development\n\nUse small red → green → refactor cycles when a test-first feedback loop is\npractical. Treat repository conventions, existing tests, and the requested\nbehavior as authoritative.\n\n## Loop\n\n1. Identify one observable behavior and the seam through which callers see it.\n2. Write the smallest meaningful test and confirm that it fails for the expected\n   reason.\n3. Add only enough implementation to make the test pass.\n4. Refactor when doing so improves clarity or design; keep the suite green.\n5. Repeat with the next vertical slice.\n\nInfer seams from public interfaces and nearby tests. Ask the user only when\nchoosing a seam would materially change the product contract, cost, or scope.\n\n## Judgment\n\n- Prefer behavior-focused tests that survive internal refactors.\n- Derive expected results from a specification, worked example, or other\n  independent source rather than duplicating the implementation.\n- Mock external or nondeterministic boundaries when useful; follow established\n  repository patterns where they provide an adequate feedback loop.\n- Prefer vertical slices over a speculative batch of tests. Batch closely\n  related mechanical cases when that is clearer and faster.\n- If a failing-first cycle is impractical—for example in legacy code with no\n  usable seam—state the limitation and establish the nearest reliable\n  characterization or integration test.\n\nRead [tests.md](tests.md) for examples and [mocking.md](mocking.md) when deciding\nwhether and where to use test doubles.\n","# Test-Driven Development\n\nUse small red → green → refactor cycles when a test-first feedback loop is\npractical. Treat repository conventions, existing tests, and the requested\nbehavior as authoritative.\n\n## Loop\n\n1. Identify one observable behavior and the seam through which callers see it.\n2. Write the smallest meaningful test and confirm that it fails for the expected\n   reason.\n3. Add only enough implementation to make the test pass.\n4. Refactor when doing so improves clarity or design; keep the suite green.\n5. Repeat with the next vertical slice.\n\nInfer seams from public interfaces and nearby tests. Ask the user only when\nchoosing a seam would materially change the product contract, cost, or scope.\n\n## Judgment\n\n- Prefer behavior-focused tests that survive internal refactors.\n- Derive expected results from a specification, worked example, or other\n  independent source rather than duplicating the implementation.\n- Mock external or nondeterministic boundaries when useful; follow established\n  repository patterns where they provide an adequate feedback loop.\n- Prefer vertical slices over a speculative batch of tests. Batch closely\n  related mechanical cases when that is clearer and faster.\n- If a failing-first cycle is impractical—for example in legacy code with no\n  usable seam—state the limitation and establish the nearest reliable\n  characterization or integration test.\n\nRead [tests.md](tests.md) for examples and [mocking.md](mocking.md) when deciding\nwhether and where to use test doubles.\n",{"name":5,"description":7},"main","11b582a7cd4d549f1e83c412e04421bcc9c3fc28",".agents\u002Fskills\u002Ftdd",69,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx","https:\u002F\u002Fstevesolun.github.io\u002Fctx\u002F","https:\u002F\u002Fgithub.com\u002Fstevesolun","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fsolunsteve\u002F","High motivated, dedicated, fast learner data scientist and enthusiastic researcher.","2026-10-15 03:55:28",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add stevesolun\u002Fctx --skill tdd",{"tool":59,"command":60},"bunx","bunx skills add stevesolun\u002Fctx --skill tdd",{"tool":62,"command":63},"pnpm","pnpm dlx skills add stevesolun\u002Fctx --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",true,[67,73,77],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",87,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"mocking.md",1822,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Fmocking.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"tests.md",2479,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002Ftests.md",[82,107,131,155,181,202],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":38},"01M6PDTT7F6Z9T6G6H92845RNC","toolbox","Pre\u002Fpost dev toolbox — named bundles of skills\u002Fagents loaded before development work and councils of experts invoked after. Run \u002Ftoolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ftoolbox\u002FSKILL.md",[],[84,89,35,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"cli","run","start","team","work","list","initialize","export","up","activate","feature","end","new repo","false","import","experts","at","invoke",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":38},"01M6PDTNZ10BAW6VY49S40NCBB","skill-router","Alive skill router — reads the current project's stack and loads\u002Funloads skills dynamically. Invoke at session start or when project context changes.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Fskill-router\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[119,120,91,121,122,123,124,125,126,127,128,129,105,130,106],"router","skill router","Meta","stack","context","session","project context","project","loads","session start","true","changes",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":38},"01M6PDTGVDG503T4QNX64KJMAC","repo-stats-autoupdate","Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes\u002Fedges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Frepo-stats-autoupdate\u002FSKILL.md",[137],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},[139,140,141,37,142,143,144,145,146,147,148,149,19,150,151,102,23,152,153,154],"stats","repo","repo stats autoupdate","commit","sync","release","git","graph","pre-commit","inventory","README","publishing","communities","hook","number","inline",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":167,"publishedAt":38},"01M6PDTC3AB7H4NXJFS3SDKQG9","find-skills","Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add\u002Fupdate a skill, or needs a repeatable procedure for finding candidate skills safely.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ffind-skills\u002FSKILL.md",[161,162],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[168,169,89,170,171,172,173,174,19,56,175,176,177,178,179,180],"find skills","find","update","search","api","user","catalog","discover","add","skills cli","for","candidate","ctx",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":38},"01M6PDT6ETDH54GGY7K8E29Y9V","no-mistakes","Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fno-mistakes\u002Fskills\u002Fno-mistakes\u002FSKILL.md",[],[188,189,37,190,191,192,90,193,194,195,196,197,198,199,19,200,201,99,129,130],"no mistakes","review","change","validate","pr","lint","push","ci","pipeline","ship","rebase","branch","intent","upstream",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":210,"publishedAt":38},"01M6PDT18DD3HETZF1CF39CT8J","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fmattpocock\u002Fzoom-out\u002FSKILL.md",[208,209],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},[211,212,213,214,123,19,215,216,23,217,218,129,219,220],"zoom out","zoom","code","how","it","understand","you","re","perspective","section"]