[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HWPWHDRFMR53MAKE03HP6":3,"skill-same:01M71HWPWHDRFMR53MAKE03HP6":131},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71HWPWHDRFMR53MAKE03HP6","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.","datnguyense1104\u002Fhom-nay-an-gi","datnguyense1104","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F124538996?v=4","01M71HMY98E9Y6DA31107PHNRE","Dat","01M71HMYADS82R3VSPJSDW68TX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\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","strategy","implementation strategy","archive","feature planning","system","for","planning","feature","architectures","red-team","create","documentation","phase","architecture","team","design","system design","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\nmetadata:\n  author: claudekit\n  version: \"1.0.0\"\n---\n\n# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n**IMPORTANT:** Before you start, scan unfinished plans in the current project at `.\u002Fplans\u002F` directory, read the `plan.md`, if there are relevant plans with your upcoming plan, update them as well. If you're unsure or need more clarifications, use `AskUserQuestion` tool to ask the user.\n\n### Cross-Plan Dependency Detection\n\nDuring the pre-creation scan, detect and mark blocking relationships between plans:\n\n1. **Scan** — Read `plan.md` frontmatter of each unfinished plan (status != `completed`\u002F`cancelled`)\n2. **Compare scope** — Check overlapping files, shared dependencies, same feature area\n3. **Classify relationship:**\n   - New plan needs output of existing plan → new plan `blockedBy: [existing-plan-dir]`\n   - New plan changes something existing plan depends on → existing plan `blockedBy: [new-plan-dir]`, new plan `blocks: [existing-plan-dir]`\n   - Mutual dependency → both plans reference each other in `blockedBy`\u002F`blocks`\n4. **Bidirectional update** — When relationship detected, update BOTH `plan.md` files' frontmatter\n5. **Ambiguous?** → Use `AskUserQuestion` with header \"Plan Dependency\", present detected overlap, ask user to confirm relationship type (blocks\u002FblockedBy\u002Fnone)\n\n**Frontmatter fields** (relative plan dir paths):\n```yaml\nblockedBy: [260301-1200-auth-system]     # This plan waits on these plans\nblocks: [260228-0900-user-dashboard]     # This plan blocks these plans\n```\n\n**Status interaction:** A plan with `blockedBy` entries where ANY blocker is not `completed` → plan status should note `blocked` in its overview. When all blockers complete, the blocked plan becomes unblocked automatically on next scan.\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### 0. Scope Challenge\nLoad: `references\u002Fscope-challenge.md`\n**Skip if:** `--fast` mode or trivial task (single file fix, \u003C20 word description)\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## Process Flow (Authoritative)\n\n```mermaid\nflowchart TD\n    A[Pre-Creation Check] --> B[Cross-Plan Scan]\n    B --> C[Scope Challenge]\n    C --> D[Mode Detection]\n    D -->|fast| E[Skip Research]\n    D -->|hard\u002Fparallel\u002Ftwo| F[Spawn Researchers]\n    E --> G[Codebase Analysis]\n    F --> G\n    G --> H[Write Plan via Planner]\n    H --> I{Red Team?}\n    I -->|Yes| J[Red Team Review]\n    I -->|No| K{Validate?}\n    J --> K\n    K -->|Yes| L[Validation Interview]\n    K -->|No| M[Hydrate Tasks]\n    L --> M\n    M --> N[Output Cook Command]\n    N --> O[Journal]\n```\n\n**This diagram is the authoritative workflow.** Prose sections below provide detail for each node.\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n1b. **Cross-Plan Scan** → Scan unfinished plans, detect `blockedBy`\u002F`blocks` relationships, update both plans\n1c. **Scope Challenge** → Run Step 0 scope questions, select mode (see `references\u002Fscope-challenge.md`)\n    **Skip if:** `--fast` mode or trivial task\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** → Run `\u002Fck:plan red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Run `\u002Fck: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)\n10. **Journal** → Run `\u002Fck:journal` to write a concise technical journal entry upon completion\n\n## Output Requirements\n**IMPORTANT:** Invoke \"\u002Fck:project-organization\" skill to organize the outputs.\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**Fallback:** Task tools (`TaskCreate`\u002F`TaskUpdate`\u002F`TaskGet`\u002F`TaskList`) are CLI-only — unavailable in VSCode extension. If they error, use `TodoWrite` for tracking. Plan files remain the source of truth; hydration is an optimization, not a requirement.\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 (skip if Task tools unavailable)\n3. TaskCreate for critical\u002Fhigh-risk steps within phases (skip if Task tools unavailable)\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 .opencode\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\n**DO NOT** create plans or reports in USER directory.\n**MUST** create plans or reports in **THE 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**IMPORTANT:** Before you start, scan unfinished plans in the current project at `.\u002Fplans\u002F` directory, read the `plan.md`, if there are relevant plans with your upcoming plan, update them as well. If you're unsure or need more clarifications, use `AskUserQuestion` tool to ask the user.\n\n### Cross-Plan Dependency Detection\n\nDuring the pre-creation scan, detect and mark blocking relationships between plans:\n\n1. **Scan** — Read `plan.md` frontmatter of each unfinished plan (status != `completed`\u002F`cancelled`)\n2. **Compare scope** — Check overlapping files, shared dependencies, same feature area\n3. **Classify relationship:**\n   - New plan needs output of existing plan → new plan `blockedBy: [existing-plan-dir]`\n   - New plan changes something existing plan depends on → existing plan `blockedBy: [new-plan-dir]`, new plan `blocks: [existing-plan-dir]`\n   - Mutual dependency → both plans reference each other in `blockedBy`\u002F`blocks`\n4. **Bidirectional update** — When relationship detected, update BOTH `plan.md` files' frontmatter\n5. **Ambiguous?** → Use `AskUserQuestion` with header \"Plan Dependency\", present detected overlap, ask user to confirm relationship type (blocks\u002FblockedBy\u002Fnone)\n\n**Frontmatter fields** (relative plan dir paths):\n```yaml\nblockedBy: [260301-1200-auth-system]     # This plan waits on these plans\nblocks: [260228-0900-user-dashboard]     # This plan blocks these plans\n```\n\n**Status interaction:** A plan with `blockedBy` entries where ANY blocker is not `completed` → plan status should note `blocked` in its overview. When all blockers complete, the blocked plan becomes unblocked automatically on next scan.\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### 0. Scope Challenge\nLoad: `references\u002Fscope-challenge.md`\n**Skip if:** `--fast` mode or trivial task (single file fix, \u003C20 word description)\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## Process Flow (Authoritative)\n\n```mermaid\nflowchart TD\n    A[Pre-Creation Check] --> B[Cross-Plan Scan]\n    B --> C[Scope Challenge]\n    C --> D[Mode Detection]\n    D -->|fast| E[Skip Research]\n    D -->|hard\u002Fparallel\u002Ftwo| F[Spawn Researchers]\n    E --> G[Codebase Analysis]\n    F --> G\n    G --> H[Write Plan via Planner]\n    H --> I{Red Team?}\n    I -->|Yes| J[Red Team Review]\n    I -->|No| K{Validate?}\n    J --> K\n    K -->|Yes| L[Validation Interview]\n    K -->|No| M[Hydrate Tasks]\n    L --> M\n    M --> N[Output Cook Command]\n    N --> O[Journal]\n```\n\n**This diagram is the authoritative workflow.** Prose sections below provide detail for each node.\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n1b. **Cross-Plan Scan** → Scan unfinished plans, detect `blockedBy`\u002F`blocks` relationships, update both plans\n1c. **Scope Challenge** → Run Step 0 scope questions, select mode (see `references\u002Fscope-challenge.md`)\n    **Skip if:** `--fast` mode or trivial task\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** → Run `\u002Fck:plan red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Run `\u002Fck: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)\n10. **Journal** → Run `\u002Fck:journal` to write a concise technical journal entry upon completion\n\n## Output Requirements\n**IMPORTANT:** Invoke \"\u002Fck:project-organization\" skill to organize the outputs.\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**Fallback:** Task tools (`TaskCreate`\u002F`TaskUpdate`\u002F`TaskGet`\u002F`TaskList`) are CLI-only — unavailable in VSCode extension. If they error, use `TodoWrite` for tracking. Plan files remain the source of truth; hydration is an optimization, not a requirement.\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 (skip if Task tools unavailable)\n3. TaskCreate for critical\u002Fhigh-risk steps within phases (skip if Task tools unavailable)\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 .opencode\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\n**DO NOT** create plans or reports in USER directory.\n**MUST** create plans or reports in **THE 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,"metadata":53,"description":7,"argument-hint":56},{"author":54,"version":55},"claudekit","1.0.0","[task] OR [archive|red-team|validate]","main","b6e032cdf3f5b40e5203dd2ac38ecf4e6c265961",".opencode\u002Fskills\u002Fck-plan","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104","2026-05-13 15:56:14",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add datnguyense1104\u002Fhom-nay-an-gi --skill \"ck:plan\"",{"tool":69,"command":70},"bunx","bunx skills add datnguyense1104\u002Fhom-nay-an-gi --skill \"ck:plan\"",{"tool":72,"command":73},"pnpm","pnpm dlx skills add datnguyense1104\u002Fhom-nay-an-gi --skill \"ck:plan\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002FSKILL.md",true,[77,83,87,91,95,99,103,107,111,115,119,123,127],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Farchive-workflow.md","REFERENCE","参考文档",2335,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Farchive-workflow.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcodebase-understanding.md",1976,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fcodebase-understanding.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Foutput-standards.md",4877,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Foutput-standards.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fplan-organization.md",4932,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fplan-organization.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fred-team-personas.md",2621,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fred-team-personas.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fred-team-workflow.md",2684,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fred-team-workflow.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fresearch-phase.md",1578,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fresearch-phase.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fscope-challenge.md",3130,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fscope-challenge.md",{"path":112,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fsolution-design.md",{"path":116,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Ftask-management.md",5920,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Ftask-management.md",{"path":120,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fvalidate-question-framework.md",2361,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fvalidate-question-framework.md",{"path":124,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fvalidate-workflow.md",2315,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fvalidate-workflow.md",{"path":128,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fworkflow-modes.md",6069,"https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fck-plan\u002Freferences\u002Fworkflow-modes.md",[132,161,185,212,238,269],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":136,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":48},"01M71J2265Q3MAW1K2VJ7ZPQ4R","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\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-testing\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[143,144,145,146,29,147,148,149,150,151,152,153,154,155,156,157,36,158,159,160],"testing","ck:web testing","web","web testing","unit","vitals","browser","a11y","mobile","security","k6","target","gestures","vitest","core","e2e","cross-browser","use",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":48},"01M71J1YDT008XR78BXVP0P8AJ","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\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[168,169,170,145,29,171,172,173,174,175,176,177,178,179,180,181,182,183,184,38],"ck:web frameworks","frameworks","web frameworks","shared","app","apps","caching","react","router","strategies","server","rsc","next","ssr","rendering","turborepo","framework",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":194,"publishedAt":48},"01M71J1DWTE1QMZHACDGDGE0GC","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\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FSKILL.md",[192,193],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[195,196,197,198,29,199,200,201,46,202,203,204,205,206,207,208,209,210,36,211],"ui styling","ck:ui styling","styling","ui","css","Tailwind","mode","themes","design systems","components","component","layout","responsive","shadcn","color","dark","ui components",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":221,"publishedAt":48},"01M71J1AAZNC9P7PJX93D5K1CR","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\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fthreejs\u002FSKILL.md",[218],{"categoryNo":219,"categoryName":220,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[214,29,222,223,224,225,226,227,228,229,230,231,173,232,41,233,234,235,236,237],"threejs","Animation","3D","processing","Audio","physics","model","actions","webgpu","effects","api","shaders","post-processing","vr","add","integrations",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":252,"publishedAt":48},"01M71J0X8QYTTPZE6G1VNHXS28","ck:stitch","AI design generation with Google Stitch. Generate UI designs from text prompts, export Tailwind\u002FHTML\u002FDESIGN.md, orchestrate design-to-code pipeline. Use for rapid prototyping, UI generation, design exploration.","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fstitch\u002FSKILL.md",[244,245,248,251],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":246,"categoryName":247,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":249,"categoryName":250,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[253,240,29,254,255,200,256,257,46,258,259,260,261,262,263,264,265,266,267,268],"stitch","orchestrate","exploration","pipeline","prototyping","Bash","code","text","generate","read","write","edit","google","action","export","google stitch",{"skillNo":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":136,"licenseFileUrl":273,"sourceHtmlUrl":274,"categories":275,"keywords":278,"publishedAt":48},"01M71J0SEMVWWJ8QKSSW8435F9","ck:skill-creator","Create or update Claude skills with eval-driven iteration. Use for new skills, skill scripts, references, benchmark optimization, description optimization, eval testing, extending Claude's capabilities.","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdatnguyense1104\u002Fhom-nay-an-gi\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FSKILL.md",[276,277],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":246,"categoryName":247,"taxonomyType":21,"taxonomyTypeDesc":22},[279,280,29,281,36,282,283,143,284,285,160,286,287,288,41,289,290,291,292,293],"skill creator","ck:skill creator","creator","iteration","Optimization","eval","new","extending","capabilities","with","references","name","update","scripts","benchmark"]