[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DT604C3A5GRG03S2XM9QR4":3,"skill-same:01M6DT604C3A5GRG03S2XM9QR4":75},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6DT604C3A5GRG03S2XM9QR4","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.","nicolasLuduena\u002Fskills","nicolasLuduena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47897388?v=4","01M6DT2J6QHQB14SH18EFBKT6D","Nicolás Ludueña","01M6DT2JBREQBVQYEQBR2AC31G",0,"MIT","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"test","integration tests","development","integration","refactor","first","user","fix","use","red-green-refactor","build","green","tests","driven","red","2026-11-10 10:12:30",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 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), call the Skill tool with \"codebase-design\" 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 (see the `code-review` skill), not the red → green implementation cycle.\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), call the Skill tool with \"codebase-design\" 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 (see the `code-review` skill), not the red → green implementation cycle.\n",{"name":5,"description":7},"main","7ea7cd250b1d6a56795f2f23baf513a21420124b","skills\u002Floop\u002Ftdd","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills","https:\u002F\u002Fgithub.com\u002FnicolasLuduena","https:\u002F\u002Fnico-luduena.online","Senior full-stack engineer at @txpipe · Rust, TypeScript, blockchain infrastructure, developer tooling, and privacy-preserving applications.","2026-11-10 04:46:43",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add nicolasLuduena\u002Fskills --skill tdd",{"tool":53,"command":54},"bunx","bunx skills add nicolasLuduena\u002Fskills --skill tdd",{"tool":56,"command":57},"pnpm","pnpm dlx skills add nicolasLuduena\u002Fskills --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002FSKILL.md",true,[61,67,71],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"agents\u002Fopenai.yaml","REFERENCE","参考文档",87,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002Fagents\u002Fopenai.yaml",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"mocking.md",1481,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002Fmocking.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"tests.md",2214,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002Ftests.md",[76,83,113,137,152,176],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":34},"01M717YJYMV0G9H52HJ9R259M2","improve","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FSKILL.md",[],[78],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":34},"01M6DT66VWY2M4VM3J7G2813T6","create-verification-skill","Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for \u002Fcreate-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI\u002FCLI\u002Fservice behavior.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fcreate-verification-skill\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[95,96,97,98,99,100,101,102,103,104,39,105,27,106,107,108,109,110,111,112],"create verification skill","verification","create","harness","github","app","control","platform","project","local","evidence","pr","generated","repo","generate","verify","license","cli",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":34},"01M6DT6ABQ8TMVEFEFRQ7SP58V","maintain-verification-skill","Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for \u002Fmaintain-verification-skill or \"audit the verify skill\".","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fmaintain-verification-skill\u002FSKILL.md",[119],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[96,121,122,99,123,124,125,126,127,128,129,130,103,131,39,106,27,132,133,108,134,135,110,136,111],"maintain verification skill","maintain","periodic","normal","weekly","for","true","tree","as","feature","map","session","implementer","parallel","loop","audit",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":34},"01M6DT64EQS172J3GFTSGW6MZR","verdict","The Reviewer's Verdict on a PR: re-run the repo's verification skill at the PR's head, hold the PR's Evidence against it, and record pass or fail with nico-agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fverdict\u002FSKILL.md",[],[139,127,96,144,145,146,147,148,149,105,108,150,151,106],"at","re","with","it","head","record","reviewer","run",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":34},"01M6DT5X7ZAHFMFDSMM1RA2500","research","Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fresearch\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000021","资料检索与研究",[154,25,162,108,163,164,165,166,167,168,27,169,170,171,172,173,174,129,175],"question","capture","markdown","investigate","api","file","docs","when","background","facts","high","reading","sources","trust",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":34},"01M6DT5STG12ET75KKQ4M1CN1Z","quality-scan","Audit a Repo with ponytail-audit and a deepening scan and file the top findings as issues, at most five open at once, without editing code.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fquality-scan\u002FSKILL.md",[],[183,184,185,127,186,144,187,146,129,108,188,189,136,167,190,191,192],"quality scan","scan","quality","deepening","top","editing","open","issues","code","ponytail"]