[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BXRS1VDXV3PAZW0SWM48P":3,"skill-same:01M73BXRS1VDXV3PAZW0SWM48P":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73BXRS1VDXV3PAZW0SWM48P","tdd-workflow",null,"Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: tdd-workflow\ndescription: \"Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Ftdd-workflow","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill tdd-workflow",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill tdd-workflow",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill tdd-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"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":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]