[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPC6K3TMWAVCY2VXJBCE4C":3,"skill-same:01M6MPC6K3TMWAVCY2VXJBCE4C":104},{"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":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6MPC6K3TMWAVCY2VXJBCE4C","test-driven-development",null,"Use when implementing a feature, fixing a bug, or changing behavior — write a failing test first, watch it fail, write minimal code to pass, then refactor. Adds Kent Beck's Tidy First (separate structural vs behavioral changes) and a Canon test list. Language-agnostic core; per-language notes under references\u002Flanguages\u002F. Not for throwaway prototypes, generated code, or pure config changes (ask first).","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\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"test driven development","development","driven","test","generated","failing","when","throwaway","implementing","structural","test list","references","bug","behavioral","list","write","ask","tidy","refactor","code","notes","config","2026-11-10 10:12:30",false,"---\nname: test-driven-development\ndescription: \"Use when implementing a feature, fixing a bug, or changing behavior — write a failing test first, watch it fail, write minimal code to pass, then refactor. Adds Kent Beck's Tidy First (separate structural vs behavioral changes) and a Canon test list. Language-agnostic core; per-language notes under references\u002Flanguages\u002F. Not for throwaway prototypes, generated code, or pure config changes (ask first).\"\n---\n\n# Test-Driven Development (TDD)\n\n## Overview\n\nWrite the test first. Watch it fail. Write minimal code to pass. Then tidy.\n\n**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.\n\n**Announce at start:** \"I'm using the test-driven-development skill to drive this change test-first.\"\n\nThis skill is **language-agnostic**. The discipline below holds in every language; concrete framework, runner, and idiom examples live in [references\u002Flanguages\u002F](references\u002Flanguages\u002F) — load the one matching your project.\n\n## Prerequisites\n\n- A working test runner for your stack (see the matching `references\u002Flanguages\u002F\u003Clang>.md`)\n- Ability to run a single test and watch its output\n- For mocks\u002Ftest doubles, read [references\u002Ftesting-anti-patterns.md](references\u002Ftesting-anti-patterns.md) first\n\n## When to Use\n\n**Always:**\n- New features\n- Bug fixes\n- Refactoring\n- Behavior changes\n\n**Exceptions (ask your human partner first):**\n- Throwaway prototypes (then throw them away and restart with TDD)\n- Generated code\n- Pure configuration changes\n\nThinking \"skip TDD just this once\"? Stop. That's rationalization.\n\n## The Iron Law\n\n```\nNO PRODUCTION CODE WITHOUT A FAILING TEST FIRST\n```\n\nWrote code before the test? Delete it. Start over.\n\n**No exceptions:** don't keep it as \"reference\", don't \"adapt\" it while writing the test, don't even look at it. Delete means delete. Implement fresh from the test.\n\n## Workflow\n\n### Phase 1: Build a Test List (Canon TDD)\n\nBefore writing any test, list the behaviors you need to cover — the basic case plus every variant you can think of (\"what if the input is empty? what if the service times out? what if the key is missing?\").\n\n- This is **behavioral analysis**, not implementation design.\n- Keep the list visible. Add to it whenever you discover a new case mid-cycle.\n- Turn **exactly one** item into a concrete test at a time — never convert the whole list up front (reworking speculative tests when an early decision changes is wasted effort).\n\n### Phase 2: Red-Green-Refactor — one list item at a time\n\n```\npick one item  →  RED  →  verify red  →  GREEN  →  verify green  →  REFACTOR  →  back to the list\n```\n\n> **Run tests in the quietest mode that still surfaces failures.** Verbose pass logs burn context you don't need — quiet runners stay silent on green and print full detail on red, so you keep the failures without the noise. Switch to verbose (`-v` \u002F `-s` \u002F `--nocapture`) only when isolating one test's output. Per-language quiet flags are in each [`references\u002Flanguages\u002F\u003Clang>.md`](references\u002Flanguages\u002F).\n\n#### RED — write one failing test\n\nOne behavior, a name that describes that behavior (e.g. `shouldRetryThreeTimesThenSucceed`, not `test1`), real code over mocks. Work backwards from the assertion. See your language file for concrete framework syntax.\n\n#### Verify RED — watch it fail (MANDATORY, never skip)\n\nRun the single test. Confirm:\n- It **fails**, not errors (no typos\u002Fmissing imports)\n- It fails for the **expected reason** — the behavior is missing, not the setup is broken\n\n**Test passes already?** You're testing existing behavior. Fix the test.\n\n#### GREEN — minimal code to pass\n\nWrite the simplest code that makes this test (and all previous tests) pass. No speculative APIs, no extra options, no \"while I'm here\" cleanup. YAGNI.\n\n#### Verify GREEN — watch it pass (MANDATORY)\n\nRun the test. Confirm it passes, all previous tests still pass, and output is pristine (no warnings\u002Ferrors). **Test fails? Fix the code, not the test.**\n\n#### REFACTOR — only on green\n\nRemove duplication, improve names, extract helpers. Keep every test green. Don't add behavior here — that's the next RED.\n\nThen mark the item done and return to the list. Repeat until the list is empty.\n\n### Phase 3: Tidy First — separate structural from behavioral changes\n\nKent Beck's distinction. Every change is one of two kinds — **never mix them in one commit:**\n\n| Kind | What it is | Reversible? |\n|---|---|---|\n| **Structural** | Rearranging without changing behavior: rename, extract method, move code, organize imports | Usually yes |\n| **Behavioral** | Adding or changing what the system actually does | No |\n\n- When you need both, make the **structural change first**, on green.\n- Validate a structural change didn't alter behavior by running the tests **before and after** — they stay green throughout.\n- If a change is a tangle of both, untangle it (or redo it) into a structural step then a behavioral step.\n\n### Phase 4: Commit Discipline\n\nCommit only when:\n- **All** tests pass and **all** compiler\u002Flinter warnings are resolved\n- The change is a single logical unit\n- The commit message states whether it is **structural** or **behavioral**\n\nPrefer small, frequent commits over large, infrequent ones. (For this repo's commit format, the `git-commit` skill applies — structural vs behavioral maps cleanly onto its `refactor:` vs `feat:`\u002F`fix:` types.)\n\n## Why Test-First (Not Test-After)\n\nTests written after code pass immediately — and passing immediately proves nothing: they may test the wrong thing, test the implementation instead of behavior, or miss the edge case you forgot. You never saw them catch anything.\n\nTest-after answers \"what does this do?\" Test-first answers \"what *should* this do?\" — and forces edge-case discovery *before* you implement. 30 minutes of tests-after gives you coverage but loses the proof the test works.\n\n## Common Rationalizations\n\n| Excuse | Reality |\n|--------|---------|\n| \"Too simple to test\" | Simple code breaks. The test takes 30 seconds. |\n| \"I'll test after\" | Tests passing immediately prove nothing. |\n| \"Tests after achieve the same goals\" | Tests-after = \"what does this do?\" Tests-first = \"what should this do?\" |\n| \"Already manually tested\" | Ad-hoc ≠ systematic. No record, can't re-run. |\n| \"Deleting X hours is wasteful\" | Sunk cost. Keeping unverified code is the real debt. |\n| \"Keep it as reference, write tests first\" | You'll adapt it. That's testing after. Delete means delete. |\n| \"Need to explore first\" | Fine. Throw away the exploration, restart with TDD. |\n| \"Hard to test = need to push through\" | Hard to test = hard to use. Listen to the test; simplify the design. |\n| \"TDD will slow me down\" | TDD is faster than debugging in production. |\n| \"This case is different because…\" | It isn't. Start over with TDD. |\n\n## Anti-Cheating Checks\n\nTest-first only works if you don't game it. These failures are especially tempting for AI agents under pressure — treat each as a STOP:\n\n- **Deleting or weakening an assertion** to make a test \"pass\" — make it pass *for real*.\n- **Pasting the computed actual value** into the expected slot — that defeats the double-check that gives TDD its value. Derive the expected value independently.\n- **Writing a test with no assertion** just for coverage.\n- **Mixing refactoring into the green step** — two hats: make it run, *then* make it right.\n- **Branching production code on test-only artifacts** (env flags, test IDs) to fake green.\n\nFor bug fixes, add at least one test that **reproduces the bug and fails first** — never fix a bug without a failing test that proves the fix.\n\n## Red Flags — STOP and start over\n\n- Code written before the test\n- Test passes on the very first run\n- Can't explain why the test failed\n- \"I already manually tested it\"\n- \"It's about the spirit, not the ritual\"\n- \"Keep as reference\" \u002F \"adapt the existing code\"\n- Tidied and changed behavior in the same commit\n- Edited the test to match the code instead of the code to match the test\n\n## Language-Specific Guidance\n\nThe discipline above is the same everywhere. For framework choice, runner commands, idioms, and language-specific anti-patterns, load **only** the file matching your project — and only when you actually need that detail:\n\n| Project language | Read |\n|---|---|\n| Java | [references\u002Flanguages\u002Fjava.md](references\u002Flanguages\u002Fjava.md) |\n| TypeScript \u002F JavaScript | [references\u002Flanguages\u002Ftypescript.md](references\u002Flanguages\u002Ftypescript.md) |\n| Python | [references\u002Flanguages\u002Fpython.md](references\u002Flanguages\u002Fpython.md) |\n| Go | [references\u002Flanguages\u002Fgo.md](references\u002Flanguages\u002Fgo.md) |\n| Rust | [references\u002Flanguages\u002Frust.md](references\u002Flanguages\u002Frust.md) |\n\nNo file for your language? The core skill is sufficient — apply the same red-green-refactor and Tidy First discipline with your stack's idiomatic runner.\n\n## Testing Anti-Patterns\n\nWhen adding mocks or test utilities, read [references\u002Ftesting-anti-patterns.md](references\u002Ftesting-anti-patterns.md) — cross-language pitfalls like testing mock behavior instead of real behavior, test-only methods on production classes, and incomplete mocks.\n\n## When Stuck\n\n| Problem | Solution |\n|---|---|\n| Don't know how to test it | Write the wished-for API in the test first. Ask your human partner. |\n| Test is too complicated | The design is too complicated. Simplify the interface. |\n| Must mock everything | Code is too coupled. Use dependency injection. |\n| Test setup is huge | Extract helpers; if still complex, the design needs simplifying. |\n\n## Verification Checklist\n\nBefore marking work complete:\n\n- [ ] Every new behavior has a test\n- [ ] Watched each test fail first, for the expected reason\n- [ ] Wrote minimal code to pass each test\n- [ ] All tests pass; output is pristine (no warnings\u002Ferrors)\n- [ ] Tests use real code (mocks only when unavoidable; see anti-patterns)\n- [ ] Edge cases from the test list are covered\n- [ ] Structural and behavioral changes are in separate commits\n\nCan't check every box? You skipped TDD. Start over.\n\n## Attribution\n\n- Red-green-refactor discipline, the Iron Law, rationalization\u002Fanti-pattern tables, and `testing-anti-patterns.md` are adapted from [superpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers) (MIT).\n- The Canon test list, Tidy First (structural vs behavioral separation), and commit discipline are from Kent Beck — *Canon TDD* and *Augmented Coding: Beyond the Vibes* (tidyfirst.substack.com).\n","# Test-Driven Development (TDD)\n\n## Overview\n\nWrite the test first. Watch it fail. Write minimal code to pass. Then tidy.\n\n**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.\n\n**Announce at start:** \"I'm using the test-driven-development skill to drive this change test-first.\"\n\nThis skill is **language-agnostic**. The discipline below holds in every language; concrete framework, runner, and idiom examples live in [references\u002Flanguages\u002F](references\u002Flanguages\u002F) — load the one matching your project.\n\n## Prerequisites\n\n- A working test runner for your stack (see the matching `references\u002Flanguages\u002F\u003Clang>.md`)\n- Ability to run a single test and watch its output\n- For mocks\u002Ftest doubles, read [references\u002Ftesting-anti-patterns.md](references\u002Ftesting-anti-patterns.md) first\n\n## When to Use\n\n**Always:**\n- New features\n- Bug fixes\n- Refactoring\n- Behavior changes\n\n**Exceptions (ask your human partner first):**\n- Throwaway prototypes (then throw them away and restart with TDD)\n- Generated code\n- Pure configuration changes\n\nThinking \"skip TDD just this once\"? Stop. That's rationalization.\n\n## The Iron Law\n\n```\nNO PRODUCTION CODE WITHOUT A FAILING TEST FIRST\n```\n\nWrote code before the test? Delete it. Start over.\n\n**No exceptions:** don't keep it as \"reference\", don't \"adapt\" it while writing the test, don't even look at it. Delete means delete. Implement fresh from the test.\n\n## Workflow\n\n### Phase 1: Build a Test List (Canon TDD)\n\nBefore writing any test, list the behaviors you need to cover — the basic case plus every variant you can think of (\"what if the input is empty? what if the service times out? what if the key is missing?\").\n\n- This is **behavioral analysis**, not implementation design.\n- Keep the list visible. Add to it whenever you discover a new case mid-cycle.\n- Turn **exactly one** item into a concrete test at a time — never convert the whole list up front (reworking speculative tests when an early decision changes is wasted effort).\n\n### Phase 2: Red-Green-Refactor — one list item at a time\n\n```\npick one item  →  RED  →  verify red  →  GREEN  →  verify green  →  REFACTOR  →  back to the list\n```\n\n> **Run tests in the quietest mode that still surfaces failures.** Verbose pass logs burn context you don't need — quiet runners stay silent on green and print full detail on red, so you keep the failures without the noise. Switch to verbose (`-v` \u002F `-s` \u002F `--nocapture`) only when isolating one test's output. Per-language quiet flags are in each [`references\u002Flanguages\u002F\u003Clang>.md`](references\u002Flanguages\u002F).\n\n#### RED — write one failing test\n\nOne behavior, a name that describes that behavior (e.g. `shouldRetryThreeTimesThenSucceed`, not `test1`), real code over mocks. Work backwards from the assertion. See your language file for concrete framework syntax.\n\n#### Verify RED — watch it fail (MANDATORY, never skip)\n\nRun the single test. Confirm:\n- It **fails**, not errors (no typos\u002Fmissing imports)\n- It fails for the **expected reason** — the behavior is missing, not the setup is broken\n\n**Test passes already?** You're testing existing behavior. Fix the test.\n\n#### GREEN — minimal code to pass\n\nWrite the simplest code that makes this test (and all previous tests) pass. No speculative APIs, no extra options, no \"while I'm here\" cleanup. YAGNI.\n\n#### Verify GREEN — watch it pass (MANDATORY)\n\nRun the test. Confirm it passes, all previous tests still pass, and output is pristine (no warnings\u002Ferrors). **Test fails? Fix the code, not the test.**\n\n#### REFACTOR — only on green\n\nRemove duplication, improve names, extract helpers. Keep every test green. Don't add behavior here — that's the next RED.\n\nThen mark the item done and return to the list. Repeat until the list is empty.\n\n### Phase 3: Tidy First — separate structural from behavioral changes\n\nKent Beck's distinction. Every change is one of two kinds — **never mix them in one commit:**\n\n| Kind | What it is | Reversible? |\n|---|---|---|\n| **Structural** | Rearranging without changing behavior: rename, extract method, move code, organize imports | Usually yes |\n| **Behavioral** | Adding or changing what the system actually does | No |\n\n- When you need both, make the **structural change first**, on green.\n- Validate a structural change didn't alter behavior by running the tests **before and after** — they stay green throughout.\n- If a change is a tangle of both, untangle it (or redo it) into a structural step then a behavioral step.\n\n### Phase 4: Commit Discipline\n\nCommit only when:\n- **All** tests pass and **all** compiler\u002Flinter warnings are resolved\n- The change is a single logical unit\n- The commit message states whether it is **structural** or **behavioral**\n\nPrefer small, frequent commits over large, infrequent ones. (For this repo's commit format, the `git-commit` skill applies — structural vs behavioral maps cleanly onto its `refactor:` vs `feat:`\u002F`fix:` types.)\n\n## Why Test-First (Not Test-After)\n\nTests written after code pass immediately — and passing immediately proves nothing: they may test the wrong thing, test the implementation instead of behavior, or miss the edge case you forgot. You never saw them catch anything.\n\nTest-after answers \"what does this do?\" Test-first answers \"what *should* this do?\" — and forces edge-case discovery *before* you implement. 30 minutes of tests-after gives you coverage but loses the proof the test works.\n\n## Common Rationalizations\n\n| Excuse | Reality |\n|--------|---------|\n| \"Too simple to test\" | Simple code breaks. The test takes 30 seconds. |\n| \"I'll test after\" | Tests passing immediately prove nothing. |\n| \"Tests after achieve the same goals\" | Tests-after = \"what does this do?\" Tests-first = \"what should this do?\" |\n| \"Already manually tested\" | Ad-hoc ≠ systematic. No record, can't re-run. |\n| \"Deleting X hours is wasteful\" | Sunk cost. Keeping unverified code is the real debt. |\n| \"Keep it as reference, write tests first\" | You'll adapt it. That's testing after. Delete means delete. |\n| \"Need to explore first\" | Fine. Throw away the exploration, restart with TDD. |\n| \"Hard to test = need to push through\" | Hard to test = hard to use. Listen to the test; simplify the design. |\n| \"TDD will slow me down\" | TDD is faster than debugging in production. |\n| \"This case is different because…\" | It isn't. Start over with TDD. |\n\n## Anti-Cheating Checks\n\nTest-first only works if you don't game it. These failures are especially tempting for AI agents under pressure — treat each as a STOP:\n\n- **Deleting or weakening an assertion** to make a test \"pass\" — make it pass *for real*.\n- **Pasting the computed actual value** into the expected slot — that defeats the double-check that gives TDD its value. Derive the expected value independently.\n- **Writing a test with no assertion** just for coverage.\n- **Mixing refactoring into the green step** — two hats: make it run, *then* make it right.\n- **Branching production code on test-only artifacts** (env flags, test IDs) to fake green.\n\nFor bug fixes, add at least one test that **reproduces the bug and fails first** — never fix a bug without a failing test that proves the fix.\n\n## Red Flags — STOP and start over\n\n- Code written before the test\n- Test passes on the very first run\n- Can't explain why the test failed\n- \"I already manually tested it\"\n- \"It's about the spirit, not the ritual\"\n- \"Keep as reference\" \u002F \"adapt the existing code\"\n- Tidied and changed behavior in the same commit\n- Edited the test to match the code instead of the code to match the test\n\n## Language-Specific Guidance\n\nThe discipline above is the same everywhere. For framework choice, runner commands, idioms, and language-specific anti-patterns, load **only** the file matching your project — and only when you actually need that detail:\n\n| Project language | Read |\n|---|---|\n| Java | [references\u002Flanguages\u002Fjava.md](references\u002Flanguages\u002Fjava.md) |\n| TypeScript \u002F JavaScript | [references\u002Flanguages\u002Ftypescript.md](references\u002Flanguages\u002Ftypescript.md) |\n| Python | [references\u002Flanguages\u002Fpython.md](references\u002Flanguages\u002Fpython.md) |\n| Go | [references\u002Flanguages\u002Fgo.md](references\u002Flanguages\u002Fgo.md) |\n| Rust | [references\u002Flanguages\u002Frust.md](references\u002Flanguages\u002Frust.md) |\n\nNo file for your language? The core skill is sufficient — apply the same red-green-refactor and Tidy First discipline with your stack's idiomatic runner.\n\n## Testing Anti-Patterns\n\nWhen adding mocks or test utilities, read [references\u002Ftesting-anti-patterns.md](references\u002Ftesting-anti-patterns.md) — cross-language pitfalls like testing mock behavior instead of real behavior, test-only methods on production classes, and incomplete mocks.\n\n## When Stuck\n\n| Problem | Solution |\n|---|---|\n| Don't know how to test it | Write the wished-for API in the test first. Ask your human partner. |\n| Test is too complicated | The design is too complicated. Simplify the interface. |\n| Must mock everything | Code is too coupled. Use dependency injection. |\n| Test setup is huge | Extract helpers; if still complex, the design needs simplifying. |\n\n## Verification Checklist\n\nBefore marking work complete:\n\n- [ ] Every new behavior has a test\n- [ ] Watched each test fail first, for the expected reason\n- [ ] Wrote minimal code to pass each test\n- [ ] All tests pass; output is pristine (no warnings\u002Ferrors)\n- [ ] Tests use real code (mocks only when unavoidable; see anti-patterns)\n- [ ] Edge cases from the test list are covered\n- [ ] Structural and behavioral changes are in separate commits\n\nCan't check every box? You skipped TDD. Start over.\n\n## Attribution\n\n- Red-green-refactor discipline, the Iron Law, rationalization\u002Fanti-pattern tables, and `testing-anti-patterns.md` are adapted from [superpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers) (MIT).\n- The Canon test list, Tidy First (structural vs behavioral separation), and commit discipline are from Kent Beck — *Canon TDD* and *Augmented Coding: Beyond the Vibes* (tidyfirst.substack.com).\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill test-driven-development",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill test-driven-development",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill test-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",true,[78,84,88,92,96,100],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Flanguages\u002Fgo.md","REFERENCE","参考文档",12237,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Flanguages\u002Fgo.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Flanguages\u002Fjava.md",9535,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Flanguages\u002Fjava.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Flanguages\u002Fpython.md",10831,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Flanguages\u002Fpython.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Flanguages\u002Frust.md",11117,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Flanguages\u002Frust.md",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Flanguages\u002Ftypescript.md",9512,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Flanguages\u002Ftypescript.md",{"path":101,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Ftesting-anti-patterns.md",8251,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ftest-driven-development\u002Freferences\u002Ftesting-anti-patterns.md",[105,115,123,131,139,147],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":114},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":114},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":114},"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":114},"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":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":114},"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":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":114},"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",[],[]]