[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72AD0DVF6GYAF162MESZQ54":3,"skill-same:01M72AD0DVF6GYAF162MESZQ54":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72AD0DVF6GYAF162MESZQ54","tdd-workflows-tdd-red",null,"Generate failing tests for the TDD red phase to define expected behavior and edge cases.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Ftdd-workflows-tdd-red\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: tdd-workflows-tdd-red\ndescription: \"Generate failing tests for the TDD red phase to define expected behavior and edge cases.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\nWrite comprehensive failing tests following TDD red phase principles.\n\n[Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.]\n\n## Use this skill when\n\n- Starting the TDD red phase for new behavior\n- You need failing tests that capture expected behavior\n- You want edge case coverage before implementation\n\n## Do not use this skill when\n\n- You are in the green or refactor phase\n- You only need performance benchmarks\n- Tests must run against production systems\n\n## Instructions\n\n1. Identify behaviors, constraints, and edge cases.\n2. Generate failing tests that define expected outcomes.\n3. Ensure failures are due to missing behavior, not setup errors.\n4. Document how to run tests and verify failures.\n\n## Safety\n\n- Keep test data isolated and avoid production environments.\n- Avoid flaky external dependencies in the red phase.\n\n## Role\n\nGenerate failing tests using Task tool with subagent_type=\"unit-testing::test-automator\".\n\n## Prompt Template\n\n\"Generate comprehensive FAILING tests for: $ARGUMENTS\n\n## Core Requirements\n\n1. **Test Structure**\n   - Framework-appropriate setup (Jest\u002Fpytest\u002FJUnit\u002FGo\u002FRSpec)\n   - Arrange-Act-Assert pattern\n   - should_X_when_Y naming convention\n   - Isolated fixtures with no interdependencies\n\n2. **Behavior Coverage**\n   - Happy path scenarios\n   - Edge cases (empty, null, boundary values)\n   - Error handling and exceptions\n   - Concurrent access (if applicable)\n\n3. **Failure Verification**\n   - Tests MUST fail when run\n   - Failures for RIGHT reasons (not syntax\u002Fimport errors)\n   - Meaningful diagnostic error messages\n   - No cascading failures\n\n4. **Test Categories**\n   - Unit: Isolated component behavior\n   - Integration: Component interaction\n   - Contract: API\u002Finterface contracts\n   - Property: Mathematical invariants\n\n## Framework Patterns\n\n**JavaScript\u002FTypeScript (Jest\u002FVitest)**\n- Mock dependencies with `vi.fn()` or `jest.fn()`\n- Use `@testing-library` for React components\n- Property tests with `fast-check`\n\n**Python (pytest)**\n- Fixtures with appropriate scopes\n- Parametrize for multiple test cases\n- Hypothesis for property-based tests\n\n**Go**\n- Table-driven tests with subtests\n- `t.Parallel()` for parallel execution\n- Use `testify\u002Fassert` for cleaner assertions\n\n**Ruby (RSpec)**\n- `let` for lazy loading, `let!` for eager\n- Contexts for different scenarios\n- Shared examples for common behavior\n\n## Quality Checklist\n\n- Readable test names documenting intent\n- One behavior per test\n- No implementation leakage\n- Meaningful test data (not 'foo'\u002F'bar')\n- Tests serve as living documentation\n\n## Anti-Patterns to Avoid\n\n- Tests passing immediately\n- Testing implementation vs behavior\n- Complex setup code\n- Multiple responsibilities per test\n- Brittle tests tied to specifics\n\n## Edge Case Categories\n\n- **Null\u002FEmpty**: undefined, null, empty string\u002Farray\u002Fobject\n- **Boundaries**: min\u002Fmax values, single element, capacity limits\n- **Special Cases**: Unicode, whitespace, special characters\n- **State**: Invalid transitions, concurrent modifications\n- **Errors**: Network failures, timeouts, permissions\n\n## Output Requirements\n\n- Complete test files with imports\n- Documentation of test purpose\n- Commands to run and verify failures\n- Metrics: test count, coverage areas\n- Next steps for green phase\"\n\n## Validation\n\nAfter generation:\n1. Run tests - confirm they fail\n2. Verify helpful failure messages\n3. Check test independence\n4. Ensure comprehensive coverage\n\n## Example (Minimal)\n\n```typescript\n\u002F\u002F auth.service.test.ts\ndescribe('AuthService', () => {\n  let authService: AuthService;\n  let mockUserRepo: jest.Mocked\u003CUserRepository>;\n\n  beforeEach(() => {\n    mockUserRepo = { findByEmail: jest.fn() } as any;\n    authService = new AuthService(mockUserRepo);\n  });\n\n  it('should_return_token_when_valid_credentials', async () => {\n    const user = { id: '1', email: 'test@example.com', passwordHash: 'hashed' };\n    mockUserRepo.findByEmail.mockResolvedValue(user);\n\n    const result = await authService.authenticate('test@example.com', 'pass');\n\n    expect(result.success).toBe(true);\n    expect(result.token).toBeDefined();\n  });\n\n  it('should_fail_when_user_not_found', async () => {\n    mockUserRepo.findByEmail.mockResolvedValue(null);\n\n    const result = await authService.authenticate('none@example.com', 'pass');\n\n    expect(result.success).toBe(false);\n    expect(result.error).toBe('INVALID_CREDENTIALS');\n  });\n});\n```\n\nTest requirements: $ARGUMENTS\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","Write comprehensive failing tests following TDD red phase principles.\n\n[Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.]\n\n## Use this skill when\n\n- Starting the TDD red phase for new behavior\n- You need failing tests that capture expected behavior\n- You want edge case coverage before implementation\n\n## Do not use this skill when\n\n- You are in the green or refactor phase\n- You only need performance benchmarks\n- Tests must run against production systems\n\n## Instructions\n\n1. Identify behaviors, constraints, and edge cases.\n2. Generate failing tests that define expected outcomes.\n3. Ensure failures are due to missing behavior, not setup errors.\n4. Document how to run tests and verify failures.\n\n## Safety\n\n- Keep test data isolated and avoid production environments.\n- Avoid flaky external dependencies in the red phase.\n\n## Role\n\nGenerate failing tests using Task tool with subagent_type=\"unit-testing::test-automator\".\n\n## Prompt Template\n\n\"Generate comprehensive FAILING tests for: $ARGUMENTS\n\n## Core Requirements\n\n1. **Test Structure**\n   - Framework-appropriate setup (Jest\u002Fpytest\u002FJUnit\u002FGo\u002FRSpec)\n   - Arrange-Act-Assert pattern\n   - should_X_when_Y naming convention\n   - Isolated fixtures with no interdependencies\n\n2. **Behavior Coverage**\n   - Happy path scenarios\n   - Edge cases (empty, null, boundary values)\n   - Error handling and exceptions\n   - Concurrent access (if applicable)\n\n3. **Failure Verification**\n   - Tests MUST fail when run\n   - Failures for RIGHT reasons (not syntax\u002Fimport errors)\n   - Meaningful diagnostic error messages\n   - No cascading failures\n\n4. **Test Categories**\n   - Unit: Isolated component behavior\n   - Integration: Component interaction\n   - Contract: API\u002Finterface contracts\n   - Property: Mathematical invariants\n\n## Framework Patterns\n\n**JavaScript\u002FTypeScript (Jest\u002FVitest)**\n- Mock dependencies with `vi.fn()` or `jest.fn()`\n- Use `@testing-library` for React components\n- Property tests with `fast-check`\n\n**Python (pytest)**\n- Fixtures with appropriate scopes\n- Parametrize for multiple test cases\n- Hypothesis for property-based tests\n\n**Go**\n- Table-driven tests with subtests\n- `t.Parallel()` for parallel execution\n- Use `testify\u002Fassert` for cleaner assertions\n\n**Ruby (RSpec)**\n- `let` for lazy loading, `let!` for eager\n- Contexts for different scenarios\n- Shared examples for common behavior\n\n## Quality Checklist\n\n- Readable test names documenting intent\n- One behavior per test\n- No implementation leakage\n- Meaningful test data (not 'foo'\u002F'bar')\n- Tests serve as living documentation\n\n## Anti-Patterns to Avoid\n\n- Tests passing immediately\n- Testing implementation vs behavior\n- Complex setup code\n- Multiple responsibilities per test\n- Brittle tests tied to specifics\n\n## Edge Case Categories\n\n- **Null\u002FEmpty**: undefined, null, empty string\u002Farray\u002Fobject\n- **Boundaries**: min\u002Fmax values, single element, capacity limits\n- **Special Cases**: Unicode, whitespace, special characters\n- **State**: Invalid transitions, concurrent modifications\n- **Errors**: Network failures, timeouts, permissions\n\n## Output Requirements\n\n- Complete test files with imports\n- Documentation of test purpose\n- Commands to run and verify failures\n- Metrics: test count, coverage areas\n- Next steps for green phase\"\n\n## Validation\n\nAfter generation:\n1. Run tests - confirm they fail\n2. Verify helpful failure messages\n3. Check test independence\n4. Ensure comprehensive coverage\n\n## Example (Minimal)\n\n```typescript\n\u002F\u002F auth.service.test.ts\ndescribe('AuthService', () => {\n  let authService: AuthService;\n  let mockUserRepo: jest.Mocked\u003CUserRepository>;\n\n  beforeEach(() => {\n    mockUserRepo = { findByEmail: jest.fn() } as any;\n    authService = new AuthService(mockUserRepo);\n  });\n\n  it('should_return_token_when_valid_credentials', async () => {\n    const user = { id: '1', email: 'test@example.com', passwordHash: 'hashed' };\n    mockUserRepo.findByEmail.mockResolvedValue(user);\n\n    const result = await authService.authenticate('test@example.com', 'pass');\n\n    expect(result.success).toBe(true);\n    expect(result.token).toBeDefined();\n  });\n\n  it('should_fail_when_user_not_found', async () => {\n    mockUserRepo.findByEmail.mockResolvedValue(null);\n\n    const result = await authService.authenticate('none@example.com', 'pass');\n\n    expect(result.success).toBe(false);\n    expect(result.error).toBe('INVALID_CREDENTIALS');\n  });\n});\n```\n\nTest requirements: $ARGUMENTS\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"source":24,"date_added":25,"description":7},"unknown","community","2026-02-27","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Ftdd-workflows-tdd-red","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Sansar35\u002Fclaude-agent --skill tdd-workflows-tdd-red",{"tool":38,"command":39},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill tdd-workflows-tdd-red",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill tdd-workflows-tdd-red","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Ftdd-workflows-tdd-red\u002FSKILL.md",true,[],[47,54,61,68,75,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","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\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]