[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG9MQ45983S3A6658DD6DC":3,"skill-same:01M6MG9MQ45983S3A6658DD6DC":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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MG9MQ45983S3A6658DD6DC","tdd",null,"Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Ftdd\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"green","new","failing","test-driven","features","fixes","for","with","red","driven","control","cycle","bug","use","first","Safety","refactor","Production","code","development","test","2026-11-10 10:12:30",false,"---\nname: tdd\ndimension: control_and_safety\ndescription: \"Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.\"\n---\n\n# TDD — Test-Driven Development\n\n## Iron Law\n\nNO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Violating the letter of this process is violating the spirit of this process.\n\n## Process\n\n### Red → Green → Refactor\n\n1. **Red**: Write a failing test that describes the desired behavior\n   - Test name should read like a spec: `it(\"returns 401 when token is expired\")` (reason: the test name IS your specification — it must communicate intent to future readers)\n   - Run the test — confirm it fails for the right reason (reason: a test that fails for the wrong reason gives false confidence)\n\n2. **Green**: Write the minimum code to make the test pass\n   - Do not write more than needed — because premature optimization is the root of all evil; make it work first\n   - Do not optimize yet — because optimization without a passing test is speculation, not engineering\n   - Run the test — confirm it passes (reason: a passing test is the only proof the code works)\n\n3. **Refactor**: Clean up without changing behavior\n   - Extract duplicates, rename for clarity, simplify — because readability matters more than cleverness\n   - Run tests again — must still pass (reason: refactoring without re-running tests is just renaming bugs)\n\n### Cycle\nRepeat for each behavior. One test, one behavior, one cycle — because scope creep in a single test cycle leads to unverified code.\n\n## When to Trigger\n- `\u002Fgo` subagents: always — because autonomous agents without TDD produce unverified code\n- New function or method being written\n- Bug fix (write regression test first — because a bug that happened once will happen again without a guard)\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|--------------------|\n| \"This is too simple for tests\" | Simple code still breaks. The Beyonce Rule applies: if you liked it, you should have put a test on it. | Write the test anyway — it takes 30 seconds and catches edge cases. |\n| \"I'll write tests after\" | That's documentation, not specification. Tests written after confirm what you built; tests written before define what you should build. | Write the test first. If you can't describe the behavior, you don't understand the requirement. |\n| \"Tests slow me down\" | 15 minutes of TDD saves hours of debugging regression bugs later. | Time the cycle — Red-Green-Refactor is usually faster than debug-after-deploy. |\n| \"I'll just test manually\" | Manual tests don't catch regressions. Automate it once, save hours forever. | Write an automated test that runs on every commit. |\n| \"The types guarantee correctness\" | Types check shape, not logic. `add(a,b)` can still return `a-b`. | Write a test that verifies the actual business rule, not just the type signature. |\n| \"I need to see the API shape first\" | Spike freely, then delete and rebuild test-first. A throwaway spike is research, not implementation. | Spike, discard, then TDD the real implementation from what you learned. |\n\n## Evidence Required\n\nBefore claiming TDD is done, show ALL of these:\n\n- [ ] Failing test output (Red phase): the test name and failure message\n- [ ] Passing test output (Green phase): `✓` with the same test name\n- [ ] Test covers behavior, not implementation (no mocking internals)\n- [ ] Refactor step completed OR explicitly noted as unnecessary with reason\n\n**No evidence = not done.** \"I wrote tests\" without showing output is not TDD.\n\n## Red Flags\n- Writing implementation before any test exists\n- Test that tests implementation details instead of behavior\n- Skipping the refactor step\n- Multiple behaviors in one test\n","# TDD — Test-Driven Development\n\n## Iron Law\n\nNO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Violating the letter of this process is violating the spirit of this process.\n\n## Process\n\n### Red → Green → Refactor\n\n1. **Red**: Write a failing test that describes the desired behavior\n   - Test name should read like a spec: `it(\"returns 401 when token is expired\")` (reason: the test name IS your specification — it must communicate intent to future readers)\n   - Run the test — confirm it fails for the right reason (reason: a test that fails for the wrong reason gives false confidence)\n\n2. **Green**: Write the minimum code to make the test pass\n   - Do not write more than needed — because premature optimization is the root of all evil; make it work first\n   - Do not optimize yet — because optimization without a passing test is speculation, not engineering\n   - Run the test — confirm it passes (reason: a passing test is the only proof the code works)\n\n3. **Refactor**: Clean up without changing behavior\n   - Extract duplicates, rename for clarity, simplify — because readability matters more than cleverness\n   - Run tests again — must still pass (reason: refactoring without re-running tests is just renaming bugs)\n\n### Cycle\nRepeat for each behavior. One test, one behavior, one cycle — because scope creep in a single test cycle leads to unverified code.\n\n## When to Trigger\n- `\u002Fgo` subagents: always — because autonomous agents without TDD produce unverified code\n- New function or method being written\n- Bug fix (write regression test first — because a bug that happened once will happen again without a guard)\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|--------------------|\n| \"This is too simple for tests\" | Simple code still breaks. The Beyonce Rule applies: if you liked it, you should have put a test on it. | Write the test anyway — it takes 30 seconds and catches edge cases. |\n| \"I'll write tests after\" | That's documentation, not specification. Tests written after confirm what you built; tests written before define what you should build. | Write the test first. If you can't describe the behavior, you don't understand the requirement. |\n| \"Tests slow me down\" | 15 minutes of TDD saves hours of debugging regression bugs later. | Time the cycle — Red-Green-Refactor is usually faster than debug-after-deploy. |\n| \"I'll just test manually\" | Manual tests don't catch regressions. Automate it once, save hours forever. | Write an automated test that runs on every commit. |\n| \"The types guarantee correctness\" | Types check shape, not logic. `add(a,b)` can still return `a-b`. | Write a test that verifies the actual business rule, not just the type signature. |\n| \"I need to see the API shape first\" | Spike freely, then delete and rebuild test-first. A throwaway spike is research, not implementation. | Spike, discard, then TDD the real implementation from what you learned. |\n\n## Evidence Required\n\nBefore claiming TDD is done, show ALL of these:\n\n- [ ] Failing test output (Red phase): the test name and failure message\n- [ ] Passing test output (Green phase): `✓` with the same test name\n- [ ] Test covers behavior, not implementation (no mocking internals)\n- [ ] Refactor step completed OR explicitly noted as unnecessary with reason\n\n**No evidence = not done.** \"I wrote tests\" without showing output is not TDD.\n\n## Red Flags\n- Writing implementation before any test exists\n- Test that tests implementation details instead of behavior\n- Skipping the refactor step\n- Multiple behaviors in one test\n",{"name":5,"dimension":50,"description":7},"control_and_safety","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Ftdd",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tdd",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tdd",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Ftdd\u002FSKILL.md",true,[],[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\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":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]