[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C66VDXYX662A58GQF39JF":3,"skill-same:01M71C66VDXYX662A58GQF39JF":73},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71C66VDXYX662A58GQF39JF","tdd-workflow",null,"Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.","yqecea\u002Fgem-swarm","yqecea","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196189405?v=4","01M71C12KWH5QPTE12J69335KF","Yusuf","01M71C12MFS3BRGNE5SSHB4DY9",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Ftdd-workflow\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"workflow","tdd","tdd workflow","test-driven","principles","red","driven","green","cycle","development workflow","red-green-refactor","edit","write","read","grep","Bash","refactor","development","test","2026-11-10 10:12:30",false,"---\nname: tdd-workflow\ndescription: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash\n---\n\n# TDD Workflow\n\n> Write tests first, code second.\n\n---\n\n## 1. The TDD Cycle\n\n```\n🔴 RED → Write failing test\n    ↓\n🟢 GREEN → Write minimal code to pass\n    ↓\n🔵 REFACTOR → Improve code quality\n    ↓\n   Repeat...\n```\n\n---\n\n## 2. The Three Laws of TDD\n\n1. Write production code only to make a failing test pass\n2. Write only enough test to demonstrate failure\n3. Write only enough code to make the test pass\n\n---\n\n## 3. RED Phase Principles\n\n### What to Write\n\n| Focus | Example |\n|-------|---------|\n| Behavior | \"should add two numbers\" |\n| Edge cases | \"should handle empty input\" |\n| Error states | \"should throw for invalid data\" |\n\n### RED Phase Rules\n\n- Test must fail first\n- Test name describes expected behavior\n- One assertion per test (ideally)\n\n---\n\n## 4. GREEN Phase Principles\n\n### Minimum Code\n\n| Principle | Meaning |\n|-----------|---------|\n| **YAGNI** | You Aren't Gonna Need It |\n| **Simplest thing** | Write the minimum to pass |\n| **No optimization** | Just make it work |\n\n### GREEN Phase Rules\n\n- Don't write unneeded code\n- Don't optimize yet\n- Pass the test, nothing more\n\n---\n\n## 5. REFACTOR Phase Principles\n\n### What to Improve\n\n| Area | Action |\n|------|--------|\n| Duplication | Extract common code |\n| Naming | Make intent clear |\n| Structure | Improve organization |\n| Complexity | Simplify logic |\n\n### REFACTOR Rules\n\n- All tests must stay green\n- Small incremental changes\n- Commit after each refactor\n\n---\n\n## 6. AAA Pattern\n\nEvery test follows:\n\n| Step | Purpose |\n|------|---------|\n| **Arrange** | Set up test data |\n| **Act** | Execute code under test |\n| **Assert** | Verify expected outcome |\n\n---\n\n## 7. When to Use TDD\n\n| Scenario | TDD Value |\n|----------|-----------|\n| New feature | High |\n| Bug fix | High (write test first) |\n| Complex logic | High |\n| Exploratory | Low (spike, then TDD) |\n| UI layout | Low |\n\n---\n\n## 8. Test Prioritization\n\n| Priority | Test Type |\n|----------|-----------|\n| 1 | Happy path |\n| 2 | Error cases |\n| 3 | Edge cases |\n| 4 | Performance |\n\n---\n\n## 9. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Skip the RED phase | Watch test fail first |\n| Write tests after | Write tests before |\n| Over-engineer initial | Keep it simple |\n| Multiple asserts | One behavior per test |\n| Test implementation | Test behavior |\n\n---\n\n## 10. AI-Augmented TDD\n\n### Multi-Agent Pattern\n\n| Agent | Role |\n|-------|------|\n| Agent A | Write failing tests (RED) |\n| Agent B | Implement to pass (GREEN) |\n| Agent C | Optimize (REFACTOR) |\n\n---\n\n> **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.\n","# TDD Workflow\n\n> Write tests first, code second.\n\n---\n\n## 1. The TDD Cycle\n\n```\n🔴 RED → Write failing test\n    ↓\n🟢 GREEN → Write minimal code to pass\n    ↓\n🔵 REFACTOR → Improve code quality\n    ↓\n   Repeat...\n```\n\n---\n\n## 2. The Three Laws of TDD\n\n1. Write production code only to make a failing test pass\n2. Write only enough test to demonstrate failure\n3. Write only enough code to make the test pass\n\n---\n\n## 3. RED Phase Principles\n\n### What to Write\n\n| Focus | Example |\n|-------|---------|\n| Behavior | \"should add two numbers\" |\n| Edge cases | \"should handle empty input\" |\n| Error states | \"should throw for invalid data\" |\n\n### RED Phase Rules\n\n- Test must fail first\n- Test name describes expected behavior\n- One assertion per test (ideally)\n\n---\n\n## 4. GREEN Phase Principles\n\n### Minimum Code\n\n| Principle | Meaning |\n|-----------|---------|\n| **YAGNI** | You Aren't Gonna Need It |\n| **Simplest thing** | Write the minimum to pass |\n| **No optimization** | Just make it work |\n\n### GREEN Phase Rules\n\n- Don't write unneeded code\n- Don't optimize yet\n- Pass the test, nothing more\n\n---\n\n## 5. REFACTOR Phase Principles\n\n### What to Improve\n\n| Area | Action |\n|------|--------|\n| Duplication | Extract common code |\n| Naming | Make intent clear |\n| Structure | Improve organization |\n| Complexity | Simplify logic |\n\n### REFACTOR Rules\n\n- All tests must stay green\n- Small incremental changes\n- Commit after each refactor\n\n---\n\n## 6. AAA Pattern\n\nEvery test follows:\n\n| Step | Purpose |\n|------|---------|\n| **Arrange** | Set up test data |\n| **Act** | Execute code under test |\n| **Assert** | Verify expected outcome |\n\n---\n\n## 7. When to Use TDD\n\n| Scenario | TDD Value |\n|----------|-----------|\n| New feature | High |\n| Bug fix | High (write test first) |\n| Complex logic | High |\n| Exploratory | Low (spike, then TDD) |\n| UI layout | Low |\n\n---\n\n## 8. Test Prioritization\n\n| Priority | Test Type |\n|----------|-----------|\n| 1 | Happy path |\n| 2 | Error cases |\n| 3 | Edge cases |\n| 4 | Performance |\n\n---\n\n## 9. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Skip the RED phase | Watch test fail first |\n| Write tests after | Write tests before |\n| Over-engineer initial | Keep it simple |\n| Multiple asserts | One behavior per test |\n| Test implementation | Test behavior |\n\n---\n\n## 10. AI-Augmented TDD\n\n### Multi-Agent Pattern\n\n| Agent | Role |\n|-------|------|\n| Agent A | Write failing tests (RED) |\n| Agent B | Implement to pass (GREEN) |\n| Agent C | Optimize (REFACTOR) |\n\n---\n\n> **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.\n",{"name":5,"description":7,"allowed-tools":51},"Read, Write, Edit, Glob, Grep, Bash","main","923c514d4d5e15bbfd65ec7eaf949a997679aa3e","src\u002Fskills\u002Fdomain\u002Ftdd-workflow","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm","https:\u002F\u002Fgithub.com\u002Fyqecea","15 y.o Data Science,Student","2026-04-26 20:00:27",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add yqecea\u002Fgem-swarm --skill tdd-workflow",{"tool":65,"command":66},"bunx","bunx skills add yqecea\u002Fgem-swarm --skill tdd-workflow",{"tool":68,"command":69},"pnpm","pnpm dlx skills add yqecea\u002Fgem-swarm --skill tdd-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Ftdd-workflow\u002FSKILL.md",true,[],[74,88,102,113,125,148],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":46},"01M71C74XVPP23ST10E8MYJZA0","validation","Cross-cutting validation methodology for verifying phase outputs and project integrity","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fvalidation\u002FSKILL.md",[],[76,81,82,83,84,85,86,87],"validation methodology","for","project","outputs","phase","methodology","integrity",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":46},"01M71C72PTKRV481M975R3QDDE","session-management","Manages orchestration session state, tracking, and resumption","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fsession-management\u002FSKILL.md",[],[95,96,97,98,99,100,101],"session management","session","management","session state","orchestration","state","tracking",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":46},"01M71C6ZY1EGM4SGVYT4B2HHD7","implementation-planning","Generates detailed implementation plans from finalized designs","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fimplementation-planning\u002FSKILL.md",[],[109,110,111,112],"planning","implementation","implementation planning","plans",{"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":119,"publishedAt":46},"01M71C6XQVGMDFJ50BP5SBDS76","execution","Phase execution methodology for orchestration workflows with error handling and completion protocols","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fexecution\u002FSKILL.md",[],[115,82,86,120,121,99,85,122,123,124],"error","workflows","protocols","error handling","with",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":139,"publishedAt":46},"01M71C6VY8APWMNK1XEJ3WP7A2","design-dialogue","Guides structured design conversations for complex engineering tasks","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdesign-dialogue\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[140,141,142,143,144,82,145,146,147],"dialogue","design","design dialogue","guides","conversations","tasks","engineering","structured",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":158,"publishedAt":46},"01M71C6R4RJWG3S2R26778TPD8","delegation","Agent delegation best practices for constructing effective subagent prompts with proper scoping","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdelegation\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[150,159,160,82,161,124,162],"subagent","scoping","best practices","prompts"]