[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DA9H758SH9WJR2KXBQE2F9":3,"skill-same:01M6DA9H758SH9WJR2KXBQE2F9":126},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6DA9H758SH9WJR2KXBQE2F9","ck:plan",null,"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.","tvanle\u002FMiniProj","tvanle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110284635?v=4","01M6DA4BVW596533CDA41S8KDH","Trong Le","01M6DA4C0HZ091M62H15QFNKCR",2,"MIT","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"plan","system","feature","task","implementation","system design","use","strategy","technical","archive","design","team","red-team","implementation strategy","planning","create","documentation","architecture","validate","2026-11-10 10:12:30",false,"---\nname: ck:plan\ndescription: \"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.\"\nargument-hint: \"[task] OR archive|red-team|validate\"\nlicense: MIT\n---\n\n# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation | Description |\n|-----------|-------------|\n| `(default)` | Create implementation plan for a task |\n| `archive` | Write journal entry & archive plans |\n| `red-team` | Adversarial plan review |\n| `validate` | Critical questions interview |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag | Mode | Research | Red Team | Validation | Cook Flag |\n|------|------|----------|----------|------------|-----------|\n| `--auto` | Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |\n| `--fast` | Fast | Skip | Skip | Skip | `--auto` |\n| `--hard` | Hard | 2 researchers | Yes | Optional | (none) |\n| `--parallel` | Parallel | 2 researchers | Yes | Optional | `--parallel` |\n| `--two` | Two approaches | 2+ researchers | After selection | After selection | (none) |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .claude\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand | Reference | Purpose |\n|------------|-----------|---------|\n| `\u002Fck:plan archive` | `references\u002Farchive-workflow.md` | Archive plans + write journal entries |\n| `\u002Fck:plan red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers |\n| `\u002Fck:plan validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n","# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation | Description |\n|-----------|-------------|\n| `(default)` | Create implementation plan for a task |\n| `archive` | Write journal entry & archive plans |\n| `red-team` | Adversarial plan review |\n| `validate` | Critical questions interview |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag | Mode | Research | Red Team | Validation | Cook Flag |\n|------|------|----------|----------|------------|-----------|\n| `--auto` | Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |\n| `--fast` | Fast | Skip | Skip | Skip | `--auto` |\n| `--hard` | Hard | 2 researchers | Yes | Optional | (none) |\n| `--parallel` | Parallel | 2 researchers | Yes | Optional | `--parallel` |\n| `--two` | Two approaches | 2+ researchers | After selection | After selection | (none) |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .claude\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand | Reference | Purpose |\n|------------|-----------|---------|\n| `\u002Fck:plan archive` | `references\u002Farchive-workflow.md` | Archive plans + write journal entries |\n| `\u002Fck:plan red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers |\n| `\u002Fck:plan validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n",{"name":5,"license":15,"description":7,"argument-hint":53},"[task] OR archive|red-team|validate","master","3a0e1cd9f02f25856402695b26cd27a6c660365d",".claude\u002Fskills\u002Fplan",0,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj","https:\u002F\u002Fgithub.com\u002Ftvanle","Code newbie","2026-10-04 12:56:41",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add tvanle\u002FMiniProj --skill \"ck:plan\"",{"tool":68,"command":69},"bunx","bunx skills add tvanle\u002FMiniProj --skill \"ck:plan\"",{"tool":71,"command":72},"pnpm","pnpm dlx skills add tvanle\u002FMiniProj --skill \"ck:plan\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",true,[76,82,86,90,94,98,102,106,110,114,118,122],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Farchive-workflow.md","REFERENCE","参考文档",2336,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Farchive-workflow.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fcodebase-understanding.md",1973,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fcodebase-understanding.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Foutput-standards.md",4571,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Foutput-standards.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fplan-organization.md",3705,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fplan-organization.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fred-team-personas.md",2621,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-personas.md",{"path":99,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fred-team-workflow.md",2684,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-workflow.md",{"path":103,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fresearch-phase.md",1578,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fresearch-phase.md",{"path":107,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fsolution-design.md",{"path":111,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftask-management.md",5631,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Ftask-management.md",{"path":115,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fvalidate-question-framework.md",2361,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-question-framework.md",{"path":119,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fvalidate-workflow.md",2306,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-workflow.md",{"path":123,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fworkflow-modes.md",5737,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fworkflow-modes.md",[127,157,181,207,232,248],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":131,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":48},"01M6DACP358EABVVDP9RPDS9F0","ck:web-testing","Web testing with Playwright, Vitest, k6. E2E\u002Funit\u002Fintegration\u002Fload\u002Fsecurity\u002Fvisual\u002Fa11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-testing\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,35,154,155,156],"testing","web","web testing","ck:web testing","security","gestures","automation","playwright","test","test automation","core","browser","integration","core web vitals","e2e","vitest","mobile","visual","type",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":48},"01M6DACHY0T647J000NPP7H042","ck:web-frameworks","Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[139,164,165,166,167,168,169,170,171,35,172,173,174,175,176,177,178,179,31,180],"web frameworks","frameworks","ck:web frameworks","react","ssr","server","Optimization","Next.js","router","build","next","dependencies","caching","strategies","shared","caching strategies","app",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":189,"publishedAt":48},"01M6DABTKHCN35K3DDVY06N1K3","ck:ui-styling","Style UIs with shadcn\u002Fui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[187,188],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[190,191,192,193,39,194,195,196,197,198,199,200,201,35,202,203,204,205,206],"ui styling","ui","styling","ck:ui styling","css","components","component","design systems","shadcn","Tailwind","customization","radix ui","Tailwind CSS","responsive","layout","systems","dark mode",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":216,"publishedAt":48},"01M6DABMYZR8HHAHA1J5YVBYS9","ck:threejs","Build 3D web apps with Three.js (WebGL\u002FWebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR\u002FXR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fthreejs\u002FSKILL.md",[213],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[217,209,218,219,139,220,44,221,222,223,224,225,226,227,228,35,229,230,231,31],"threejs","gltf","implement","webgpu","examples","actions","api","Animation","3D","Audio","model","integrations","three","compute","physics",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":48},"01M6DAAQXHGM5007DEH08X1CGW","ck:sequential-thinking","Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[239,240,241,43,242,243,244,245,246,35,247],"sequential thinking","thinking","ck:sequential thinking","reasoning","verification","hypothesis","analysis","analyze","decomposition",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":252,"categories":253,"keywords":257,"publishedAt":48},"01M6DAAHF9TP4JT6FP0ZV38Y6Y","ck:research","Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability\u002Fsecurity\u002Fmaintainability analysis.","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fresearch\u002FSKILL.md",[254],{"categoryNo":255,"categoryName":256,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[258,250,39,142,259,260,245,246,37,35,261,262,263,264],"research","best practices","Evaluation","scalability","technology","requirements","maintainability"]