[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDC4YYYBBVM5PTSAPSF1CY":3,"skill-same:01M6MDC4YYYBBVM5PTSAPSF1CY":77},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6MDC4YYYBBVM5PTSAPSF1CY","test-driven-development",null,"Enforce RED-GREEN-REFACTOR discipline for every implementation task. Use for all new features, bug fixes, and refactors. The core rule — if you didn't watch the test fail, you don't know if it tests the right thing.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\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],"test driven development","development","test","driven","new","features","fixes","for","you","watch","tests","green","enforce","task","implementation","bug","red-green-refactor","discipline","use","refactor","core","2026-11-10 10:12:30",false,"---\nname: test-driven-development\ndescription: Enforce RED-GREEN-REFACTOR discipline for every implementation task. Use for all new features, bug fixes, and refactors. The core rule — if you didn't watch the test fail, you don't know if it tests the right thing.\n---\n\n# Test-Driven Development\n\n## The Core Rule\n\n```\nIF YOU DIDN'T WATCH THE TEST FAIL, YOU DON'T KNOW IF IT TESTS THE RIGHT THING.\n```\n\nA green test you've never seen red is not a test — it's a decoration.\n\n## The Three Phases (Non-Negotiable)\n\n### Phase RED — Write a Failing Test\n\nWrite the test FIRST. Not after. Not \"I'll add it later.\" **First.**\n\nThe test must:\n- Describe the behavior you want, not the implementation\n- Be specific enough to fail for the right reason\n- Cover the exact scenario you're about to implement\n\n```typescript\n\u002F\u002F RED: Write this BEFORE writing the function\ntest('returns empty array when no users match the filter', () => {\n  const result = filterActiveUsers([])\n  expect(result).toEqual([])\n})\n```\n\n**Run it. Watch it fail.**\n\n```bash\nnpm test -- --testPathPattern=\"user-filter\"\n# Expected: FAIL (function doesn't exist yet)\n```\n\nIf the test passes before you write the implementation: the test is wrong. Rewrite it.\n\n### Phase GREEN — Write Minimal Implementation\n\nWrite the **smallest possible code** that makes the test pass. Nothing more.\n\n- No extra features \"while I'm here\"\n- No optimization\n- No handling of edge cases not yet covered by tests\n- Ugly code that passes is better than beautiful code that doesn't exist yet\n\n```typescript\n\u002F\u002F GREEN: Minimal implementation that passes the test\nfunction filterActiveUsers(users: User[]): User[] {\n  return users.filter(u => u.active)\n}\n```\n\n**Run it. Watch it pass.**\n\n```bash\nnpm test -- --testPathPattern=\"user-filter\"\n# Expected: PASS\n```\n\nIf it still fails: read the error message carefully. Fix only what the message tells you.\n\n### Phase REFACTOR — Improve Without Breaking\n\nNow clean up. Rename, extract, simplify — **while keeping tests green**.\n\n```bash\n# Run tests continuously during refactor\nnpm test -- --watch --testPathPattern=\"user-filter\"\n```\n\nRules during refactor:\n- Tests must stay green at every step\n- No new behavior — only structural improvement\n- If tests go red: undo the last change, understand why\n\n## Adding More Tests (Expand-Contract Pattern)\n\nAfter GREEN for the first case, expand coverage:\n\n```\nRED  → watch new test fail\nGREEN → minimal code to pass\nRED  → add next edge case test\nGREEN → handle the edge case\n...\nREFACTOR → clean up all at once when coverage is complete\n```\n\nCover in order:\n1. Happy path (basic success case)\n2. Empty \u002F null inputs\n3. Boundary values (min, max, exactly-at-limit)\n4. Error paths (invalid input, dependency failure)\n5. Concurrent \u002F race conditions if applicable\n\n## What to Test vs. What NOT to Test\n\n**Test:**\n- Public API surface (exported functions, class methods, HTTP endpoints)\n- Business logic decisions\n- Data transformations\n- Error handling\n\n**Do NOT test:**\n- Implementation details (private functions, internal state)\n- Third-party library behavior\n- Framework internals\n\n## Mocking External Dependencies\n\nExternal dependencies (database, APIs, file system) must be mocked in unit tests:\n\n```typescript\n\u002F\u002F Mock the DB before testing the service\njest.mock('..\u002Fdb\u002Fusers')\nconst mockFindUser = db.findUser as jest.MockedFunction\u003Ctypeof db.findUser>\nmockFindUser.mockResolvedValue({ id: '1', name: 'Alice', active: true })\n```\n\nIntegration tests should hit real dependencies — but unit tests must be fast and isolated.\n\n## Coverage Gate\n\nAfter each feature or bug fix, verify coverage meets the project minimum:\n\n```bash\nnpm run test:coverage\n# Required: ≥ 80% branches, functions, lines, statements\n```\n\nIf coverage drops below threshold: add tests before moving on.\n\n## TDD Red Flags — You're Doing It Wrong\n\n- Writing the implementation before writing the test\n- Running the test only after implementation (never seeing it red)\n- Writing tests that test the implementation, not the behavior\n- Skipping the refactor phase (\"it works, ship it\")\n- Writing multiple failing tests before making any pass\n- Adding edge cases without first making them fail\n\nIf you catch yourself rationalizing any of these: stop, revert to the last green state, and start the RED phase properly.\n\n## Integration with A Team Workflow\n\nTDD fits into the full workflow:\n1. `brainstorming` → spec approved\n2. `writing-plans` → plan with test strategy included\n3. **`test-driven-development`** ← you are here, per task\n4. `subagent-driven-development` → each subagent runs TDD internally\n5. `verification-before-completion` → final proof before claiming done\n6. `finishing-a-development-branch` → branch wrap-up\n","# Test-Driven Development\n\n## The Core Rule\n\n```\nIF YOU DIDN'T WATCH THE TEST FAIL, YOU DON'T KNOW IF IT TESTS THE RIGHT THING.\n```\n\nA green test you've never seen red is not a test — it's a decoration.\n\n## The Three Phases (Non-Negotiable)\n\n### Phase RED — Write a Failing Test\n\nWrite the test FIRST. Not after. Not \"I'll add it later.\" **First.**\n\nThe test must:\n- Describe the behavior you want, not the implementation\n- Be specific enough to fail for the right reason\n- Cover the exact scenario you're about to implement\n\n```typescript\n\u002F\u002F RED: Write this BEFORE writing the function\ntest('returns empty array when no users match the filter', () => {\n  const result = filterActiveUsers([])\n  expect(result).toEqual([])\n})\n```\n\n**Run it. Watch it fail.**\n\n```bash\nnpm test -- --testPathPattern=\"user-filter\"\n# Expected: FAIL (function doesn't exist yet)\n```\n\nIf the test passes before you write the implementation: the test is wrong. Rewrite it.\n\n### Phase GREEN — Write Minimal Implementation\n\nWrite the **smallest possible code** that makes the test pass. Nothing more.\n\n- No extra features \"while I'm here\"\n- No optimization\n- No handling of edge cases not yet covered by tests\n- Ugly code that passes is better than beautiful code that doesn't exist yet\n\n```typescript\n\u002F\u002F GREEN: Minimal implementation that passes the test\nfunction filterActiveUsers(users: User[]): User[] {\n  return users.filter(u => u.active)\n}\n```\n\n**Run it. Watch it pass.**\n\n```bash\nnpm test -- --testPathPattern=\"user-filter\"\n# Expected: PASS\n```\n\nIf it still fails: read the error message carefully. Fix only what the message tells you.\n\n### Phase REFACTOR — Improve Without Breaking\n\nNow clean up. Rename, extract, simplify — **while keeping tests green**.\n\n```bash\n# Run tests continuously during refactor\nnpm test -- --watch --testPathPattern=\"user-filter\"\n```\n\nRules during refactor:\n- Tests must stay green at every step\n- No new behavior — only structural improvement\n- If tests go red: undo the last change, understand why\n\n## Adding More Tests (Expand-Contract Pattern)\n\nAfter GREEN for the first case, expand coverage:\n\n```\nRED  → watch new test fail\nGREEN → minimal code to pass\nRED  → add next edge case test\nGREEN → handle the edge case\n...\nREFACTOR → clean up all at once when coverage is complete\n```\n\nCover in order:\n1. Happy path (basic success case)\n2. Empty \u002F null inputs\n3. Boundary values (min, max, exactly-at-limit)\n4. Error paths (invalid input, dependency failure)\n5. Concurrent \u002F race conditions if applicable\n\n## What to Test vs. What NOT to Test\n\n**Test:**\n- Public API surface (exported functions, class methods, HTTP endpoints)\n- Business logic decisions\n- Data transformations\n- Error handling\n\n**Do NOT test:**\n- Implementation details (private functions, internal state)\n- Third-party library behavior\n- Framework internals\n\n## Mocking External Dependencies\n\nExternal dependencies (database, APIs, file system) must be mocked in unit tests:\n\n```typescript\n\u002F\u002F Mock the DB before testing the service\njest.mock('..\u002Fdb\u002Fusers')\nconst mockFindUser = db.findUser as jest.MockedFunction\u003Ctypeof db.findUser>\nmockFindUser.mockResolvedValue({ id: '1', name: 'Alice', active: true })\n```\n\nIntegration tests should hit real dependencies — but unit tests must be fast and isolated.\n\n## Coverage Gate\n\nAfter each feature or bug fix, verify coverage meets the project minimum:\n\n```bash\nnpm run test:coverage\n# Required: ≥ 80% branches, functions, lines, statements\n```\n\nIf coverage drops below threshold: add tests before moving on.\n\n## TDD Red Flags — You're Doing It Wrong\n\n- Writing the implementation before writing the test\n- Running the test only after implementation (never seeing it red)\n- Writing tests that test the implementation, not the behavior\n- Skipping the refactor phase (\"it works, ship it\")\n- Writing multiple failing tests before making any pass\n- Adding edge cases without first making them fail\n\nIf you catch yourself rationalizing any of these: stop, revert to the last green state, and start the RED phase properly.\n\n## Integration with A Team Workflow\n\nTDD fits into the full workflow:\n1. `brainstorming` → spec approved\n2. `writing-plans` → plan with test strategy included\n3. **`test-driven-development`** ← you are here, per task\n4. `subagent-driven-development` → each subagent runs TDD internally\n5. `verification-before-completion` → final proof before claiming done\n6. `finishing-a-development-branch` → branch wrap-up\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ftest-driven-development",474,"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-11 14:40:14",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill test-driven-development",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill test-driven-development",{"tool":72,"command":73},"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\u002FRBraga01\u002Fa-team\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",true,[],[78,86,93,100,126,151],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":85},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":85},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":48},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,35,119,120,121,122,123,124,125],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","done","reviewer","io","change","cli","merge","past",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":48},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[133,134,135,121,136,137,138,139,140,141,142,143,144,145,112,146,147,148,149,150],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":166,"publishedAt":48},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[157,160,163],{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[153,167,168,169,170,171,172,147,173,113,174,175,176,177,118,178,179,180,181,182],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]