[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74B8YQYV3Y8T6M4PDG5FEF3":3,"skill-same:01M74B8YQYV3Y8T6M4PDG5FEF3":43},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M74B8YQYV3Y8T6M4PDG5FEF3","tdd-workflow",null,"Test-Driven Development workflow for Claude Code. Use when implementing features with TDD, writing tests first, or need Red-Green-Refactor discipline. Triggers on TDD, test-driven, red-green-refactor, test first, or write tests before code keywords.","aicreator350\u002FaurionOFFICIELLE","aicreator350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217751428?v=4","01M731QVHB22WCM6PDX5VFN1RV","01M731QVJ0TAD058M1SW9MY548",0,"MIT","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: tdd-workflow\ndescription: \"Test-Driven Development workflow for Claude Code. Use when implementing features with TDD, writing tests first, or need Red-Green-Refactor discipline. Triggers on TDD, test-driven, red-green-refactor, test first, or write tests before code keywords.\"\n---\n\n# TDD Workflow\n\nStrict Red-Green-Refactor cycle for Test-Driven Development.\n\n## Phases\n\n### RED: Write a failing test\n1. Identify the smallest unit of behavior to implement\n2. Write a test that describes the expected behavior\n3. Run the test — it MUST fail\n4. If it passes, the test is wrong or the feature already exists\n\n```typescript\n\u002F\u002F Vitest pattern for Aurion\nimport { describe, it, expect } from 'vitest';\n\ndescribe('featureName', () => {\n  it('should [expected behavior] when [condition]', () => {\n    \u002F\u002F Arrange\n    const input = \u002F* ... *\u002F;\n    \n    \u002F\u002F Act\n    const result = featureUnderTest(input);\n    \n    \u002F\u002F Assert\n    expect(result).toBe(\u002F* expected *\u002F);\n  });\n});\n```\n\n### GREEN: Make it pass\n1. Write the MINIMUM code to make the test pass\n2. No optimization, no elegance — just make it work\n3. Run the test — it MUST pass\n4. If it fails, fix the implementation (not the test)\n\nRules:\n- TypeScript strict, zero `any`\n- Hardcoded values are OK in this phase\n- Don't write more code than needed\n\n### REFACTOR: Clean up\n1. Improve the code without changing behavior\n2. ALL tests must still pass after refactoring\n3. Remove duplication\n4. Improve naming\n5. Apply Aurion patterns (Tailwind, Framer Motion, etc.)\n\nChecklist:\n- [ ] All tests still pass\n- [ ] No duplicate code\n- [ ] TypeScript strict compliance\n- [ ] Aurion conventions followed\n\n## Cycle\n```\nRED → GREEN → REFACTOR → RED → GREEN → REFACTOR → ...\n```\n\nRepeat for each behavior. Build up complexity gradually.\n\n## Running Tests\n```bash\n# Single test file\nnpx vitest run path\u002Fto\u002Ftest.test.ts\n\n# Watch mode during development\nnpx vitest --watch path\u002Fto\u002Ftest.test.ts\n\n# With coverage\nnpx vitest run --coverage\n```\n\n## Aurion Test Patterns\n- Mock Supabase: `vi.mock('@supabase\u002Fsupabase-js')`\n- Mock Clerk: `vi.mock('@clerk\u002Fclerk-react')`\n- Mock fetch: `vi.stubGlobal('fetch', vi.fn())`\n- React Testing Library for components\n- Playwright for E2E\n","# TDD Workflow\n\nStrict Red-Green-Refactor cycle for Test-Driven Development.\n\n## Phases\n\n### RED: Write a failing test\n1. Identify the smallest unit of behavior to implement\n2. Write a test that describes the expected behavior\n3. Run the test — it MUST fail\n4. If it passes, the test is wrong or the feature already exists\n\n```typescript\n\u002F\u002F Vitest pattern for Aurion\nimport { describe, it, expect } from 'vitest';\n\ndescribe('featureName', () => {\n  it('should [expected behavior] when [condition]', () => {\n    \u002F\u002F Arrange\n    const input = \u002F* ... *\u002F;\n    \n    \u002F\u002F Act\n    const result = featureUnderTest(input);\n    \n    \u002F\u002F Assert\n    expect(result).toBe(\u002F* expected *\u002F);\n  });\n});\n```\n\n### GREEN: Make it pass\n1. Write the MINIMUM code to make the test pass\n2. No optimization, no elegance — just make it work\n3. Run the test — it MUST pass\n4. If it fails, fix the implementation (not the test)\n\nRules:\n- TypeScript strict, zero `any`\n- Hardcoded values are OK in this phase\n- Don't write more code than needed\n\n### REFACTOR: Clean up\n1. Improve the code without changing behavior\n2. ALL tests must still pass after refactoring\n3. Remove duplication\n4. Improve naming\n5. Apply Aurion patterns (Tailwind, Framer Motion, etc.)\n\nChecklist:\n- [ ] All tests still pass\n- [ ] No duplicate code\n- [ ] TypeScript strict compliance\n- [ ] Aurion conventions followed\n\n## Cycle\n```\nRED → GREEN → REFACTOR → RED → GREEN → REFACTOR → ...\n```\n\nRepeat for each behavior. Build up complexity gradually.\n\n## Running Tests\n```bash\n# Single test file\nnpx vitest run path\u002Fto\u002Ftest.test.ts\n\n# Watch mode during development\nnpx vitest --watch path\u002Fto\u002Ftest.test.ts\n\n# With coverage\nnpx vitest run --coverage\n```\n\n## Aurion Test Patterns\n- Mock Supabase: `vi.mock('@supabase\u002Fsupabase-js')`\n- Mock Clerk: `vi.mock('@clerk\u002Fclerk-react')`\n- Mock fetch: `vi.stubGlobal('fetch', vi.fn())`\n- React Testing Library for components\n- Playwright for E2E\n",{"name":5,"description":7},"main","5593cf3c72898ea9fc67225d452fe38f866ba6dd",".claude\u002Fskills\u002Ftdd-workflow","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE","https:\u002F\u002Fgithub.com\u002Faicreator350","2026-05-18 03:39:30",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add aicreator350\u002FaurionOFFICIELLE --skill tdd-workflow",{"tool":35,"command":36},"bunx","bunx skills add aicreator350\u002FaurionOFFICIELLE --skill tdd-workflow",{"tool":38,"command":39},"pnpm","pnpm dlx skills add aicreator350\u002FaurionOFFICIELLE --skill tdd-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",true,[],[44,53,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":48,"licenseFileUrl":49,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M74CAJWR9WB6DX1HF2V461Y0","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M74CAFWC2H75GJ81B39C9RSW","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M74CA9N2HTGCKJ93AE9NQMHA","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M74CA364D4EVDXZZQRVK1Z73","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M74C9YQZX1GVS18V0AYCYPZE","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M74C9SEYD6F764Q1JACZX3A6","vercel-cli-with-tokens","Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[]]