[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H1S83H18XYVFV7FHMXWM2D":3,"skill-same:01M6H1S83H18XYVFV7FHMXWM2D":125},{"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":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6H1S83H18XYVFV7FHMXWM2D","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.","dungnt1312\u002Ffilemanager-server","dungnt1312","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78264679?v=4","01M6H1A3AXWE83KGDRXBGA1SVY","DzungNT","01M6H1A3EPF6BMYQ5BM6Z8KTCE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\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","适用职业",[29,5,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"ck","plan","archive","for","feature planning","architectures","feature","system design","strategy","technical","design","system","team","red-team","implementation strategy","planning","create","documentation","architecture","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","371c133163a3479273304ffc6839de7e65370b82",".claude\u002Fskills\u002Fplan","https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server","https:\u002F\u002Fgithub.com\u002Fdungnt1312","BE Dev","2026-03-20 19:14:21",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add dungnt1312\u002Ffilemanager-server --skill \"ck:plan\"",{"tool":67,"command":68},"bunx","bunx skills add dungnt1312\u002Ffilemanager-server --skill \"ck:plan\"",{"tool":70,"command":71},"pnpm","pnpm dlx skills add dungnt1312\u002Ffilemanager-server --skill \"ck:plan\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",true,[75,81,85,89,93,97,101,105,109,113,117,121],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Farchive-workflow.md","REFERENCE","参考文档",2336,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Farchive-workflow.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcodebase-understanding.md",1973,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fcodebase-understanding.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Foutput-standards.md",4571,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Foutput-standards.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fplan-organization.md",3705,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fplan-organization.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fred-team-personas.md",2621,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-personas.md",{"path":98,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fred-team-workflow.md",2684,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-workflow.md",{"path":102,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fresearch-phase.md",1578,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fresearch-phase.md",{"path":106,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fsolution-design.md",{"path":110,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Ftask-management.md",5631,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Ftask-management.md",{"path":114,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fvalidate-question-framework.md",2361,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-question-framework.md",{"path":118,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fvalidate-workflow.md",2306,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-workflow.md",{"path":122,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fworkflow-modes.md",5737,"https:\u002F\u002Fgithub.com\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fworkflow-modes.md",[126,155,178,203,228,249],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":48},"01M6H1XJJDV8HCAZ0XTFBR37MW","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-testing\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[137,138,139,140,29,141,142,143,144,145,146,147,148,149,150,151,152,153,154,32],"testing","web","web testing","ck:web testing","security","gestures","automation","core","browser","k6","e2e","vitest","use","mobile","visual","unit","load","cross-browser",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":48},"01M6H1XBSWPPEEAPRN5XPK43KC","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[138,162,163,164,29,165,166,167,168,169,170,171,172,173,174,35,175,176,177,32],"web frameworks","frameworks","ck:web frameworks","react","ssr","framework","server","turborepo","router","next","caching","strategies","shared","app","apps","rendering",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":186,"publishedAt":48},"01M6H1WC67YNKTS5AAHTCZ5YHP","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[184,185],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[187,188,189,190,29,39,191,192,193,194,195,196,149,197,198,199,200,201,202,32],"ui styling","ui","styling","ck:ui styling","css","components","component","design systems","shadcn","Tailwind","responsive","layout","ui components","themes","color","mode",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":212,"publishedAt":48},"01M6H1W58ZN1AK0YV8NC5JJNKG","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fthreejs\u002FSKILL.md",[209],{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[213,205,29,214,45,215,216,217,218,219,220,221,222,223,35,176,224,225,226,227],"threejs","webgpu","shaders","actions","api","Animation","3D","Audio","model","integrations","physics","add","processing","post-processing","vr",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":48},"01M6H1TYHVYCJDQ6YKWV9G7GZP","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[235,236,237,29,44,238,239,240,241,242,149,243,244,245,246,247,248,32],"sequential thinking","thinking","ck:sequential thinking","reasoning","verification","hypothesis","analysis","analyze","decomposition","problem","multi","with","course","revision",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":258,"publishedAt":48},"01M6H1TMDBY06C144SDXH8ZCA0","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\u002Fdungnt1312\u002Ffilemanager-server\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fresearch\u002FSKILL.md",[255],{"categoryNo":256,"categoryName":257,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[259,251,29,39,141,260,261,241,242,38,149,262,263,264,265,34,32],"research","best practices","Evaluation","scalability","technology","requirements","maintainability"]