[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF82B3VBHVSHZ89M8JEYDJ":3,"skill-same:01M7AF82B3VBHVSHZ89M8JEYDJ":68},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF82B3VBHVSHZ89M8JEYDJ","planning",null,"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.","minhlongs\u002Fsophia-ai-factory","minhlongs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F186063428?v=4","01M7AETK9R4ST1TK6JXR2CV5BY","Minh Long","01M7AETKAFVJDBYMX448AMZV0Y",0,"MIT","https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning\ndescription: Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.\nlicense: MIT\n---\n\n# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## When to Use\n\nUse this skill when:\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n- Assessing technical trade-offs\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:** 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. **Initial Analysis** → Read codebase docs, understand context\n2. **Research Phase** → Spawn researchers, investigate approaches\n3. **Synthesis** → Analyze reports, identify optimal solution\n4. **Design Phase** → Create architecture, implementation design\n5. **Plan Documentation** → Write comprehensive plan\n6. **Review & Refine** → Ensure completeness, clarity, actionability\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- Provide multiple options with trade-offs when appropriate\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file.\n\n## Task Integration (Optional)\n\nWhen session has `CLAUDE_CODE_TASK_LIST_ID` set (active plan):\n- Use TaskCreate to create tasks for each phase with clear subjects\n- Set dependencies: Phase N+1 `blockedBy` Phase N\n- Subagents coordinate via shared task list automatically\n- Use TaskUpdate to mark progress (in_progress → completed)\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n**Plan Directory Structure**\nIN CURRENT WORKING PROJECT DIRECTORY:\n```\nplans\u002F\n└── {date}-plan-name\u002F\n    ├── research\u002F\n    │   ├── researcher-XX-report.md\n    │   └── ...\n    ├── reports\u002F\n    │   ├── XX-report.md\n    │   └── ...\n    ├── scout\u002F\n    │   ├── scout-XX-report.md\n    │   └── ...\n    ├── plan.md\n    ├── phase-XX-phase-name-here.md\n    └── ...\n```\n\n## Active Plan State\n\nPrevents version proliferation by tracking current working plan via session state.\n\n### Active vs Suggested Plans\n\nCheck the `## Plan Context` section injected by hooks:\n- **\"Plan: {path}\"** = Active plan, explicitly set via `set-active-plan.cjs` - use for reports\n- **\"Suggested: {path}\"** = Branch-matched, hint only - do NOT auto-use\n- **\"Plan: none\"** = No active plan\n\n### Rules\n\n1. **If \"Plan:\" shows a path**: Ask \"Continue with existing plan? [Y\u002Fn]\"\n2. **If \"Suggested:\" shows a path**: Inform user, ask if they want to activate or create new\n3. **If \"Plan: none\"**: Create new plan using naming from `## Naming` section\n4. **Update on create**: Run `node .opencode\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\n\n### Report Output Location\n\nAll agents writing reports MUST:\n1. Check `## Naming` section injected by hooks for the computed naming pattern\n2. Active plans use plan-specific reports path\n3. Suggested plans use default reports path (not plan folder)\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n**Important:** Suggested plans do NOT get plan-specific reports - this prevents pollution of old plan folders.\n\n## Quality Standards\n\n- Be thorough and specific\n- Consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Make plans 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## When to Use\n\nUse this skill when:\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n- Assessing technical trade-offs\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:** 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. **Initial Analysis** → Read codebase docs, understand context\n2. **Research Phase** → Spawn researchers, investigate approaches\n3. **Synthesis** → Analyze reports, identify optimal solution\n4. **Design Phase** → Create architecture, implementation design\n5. **Plan Documentation** → Write comprehensive plan\n6. **Review & Refine** → Ensure completeness, clarity, actionability\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- Provide multiple options with trade-offs when appropriate\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file.\n\n## Task Integration (Optional)\n\nWhen session has `CLAUDE_CODE_TASK_LIST_ID` set (active plan):\n- Use TaskCreate to create tasks for each phase with clear subjects\n- Set dependencies: Phase N+1 `blockedBy` Phase N\n- Subagents coordinate via shared task list automatically\n- Use TaskUpdate to mark progress (in_progress → completed)\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n**Plan Directory Structure**\nIN CURRENT WORKING PROJECT DIRECTORY:\n```\nplans\u002F\n└── {date}-plan-name\u002F\n    ├── research\u002F\n    │   ├── researcher-XX-report.md\n    │   └── ...\n    ├── reports\u002F\n    │   ├── XX-report.md\n    │   └── ...\n    ├── scout\u002F\n    │   ├── scout-XX-report.md\n    │   └── ...\n    ├── plan.md\n    ├── phase-XX-phase-name-here.md\n    └── ...\n```\n\n## Active Plan State\n\nPrevents version proliferation by tracking current working plan via session state.\n\n### Active vs Suggested Plans\n\nCheck the `## Plan Context` section injected by hooks:\n- **\"Plan: {path}\"** = Active plan, explicitly set via `set-active-plan.cjs` - use for reports\n- **\"Suggested: {path}\"** = Branch-matched, hint only - do NOT auto-use\n- **\"Plan: none\"** = No active plan\n\n### Rules\n\n1. **If \"Plan:\" shows a path**: Ask \"Continue with existing plan? [Y\u002Fn]\"\n2. **If \"Suggested:\" shows a path**: Inform user, ask if they want to activate or create new\n3. **If \"Plan: none\"**: Create new plan using naming from `## Naming` section\n4. **Update on create**: Run `node .opencode\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\n\n### Report Output Location\n\nAll agents writing reports MUST:\n1. Check `## Naming` section injected by hooks for the computed naming pattern\n2. Active plans use plan-specific reports path\n3. Suggested plans use default reports path (not plan folder)\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n**Important:** Suggested plans do NOT get plan-specific reports - this prevents pollution of old plan folders.\n\n## Quality Standards\n\n- Be thorough and specific\n- Consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Make plans 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},"main","b2c7cb35d94e515781b32f7e3948740c401f86dc",".claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning","https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory","https:\u002F\u002Fgithub.com\u002Fminhlongs","https:\u002F\u002Fwww.mekongmind.com","AI-powered business ops for Vietnam — Zalo OA, tax compliance, AI video","2026-11-15 02:50:35",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add minhlongs\u002Fsophia-ai-factory --skill planning",{"tool":38,"command":39},"bunx","bunx skills add minhlongs\u002Fsophia-ai-factory --skill planning",{"tool":41,"command":42},"pnpm","pnpm dlx skills add minhlongs\u002Fsophia-ai-factory --skill planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcodebase-understanding.md","REFERENCE","参考文档",1967,"https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002Freferences\u002Fcodebase-understanding.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Foutput-standards.md",4567,"https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002Freferences\u002Foutput-standards.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fplan-organization.md",4234,"https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002Freferences\u002Fplan-organization.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fresearch-phase.md",1572,"https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002Freferences\u002Fresearch-phase.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.claude\u002Fworktrees-archive.bak\u002F20260614-233957\u002Fagent-phase-06-fixes\u002Fagent-phase-06-fixes\u002F.opencode\u002Fskills\u002Fplanning\u002Freferences\u002Fsolution-design.md",[69,77,84,92,99,107],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AGRPKF5YS8YXJG94537JBP","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\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-testing\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGRGNGKWMZKBGMBCNNAQ9M","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\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AGQYS5CV6TSY3JFT05XZ3C","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\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AGQSGV9RP800VBKRWNT0GG","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\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7AGQKNJ8AZ0XP1BZ99Q6NTM","skill-creator","Create or update Claude skills. Use for new skills, skill references, skill scripts, optimizing existing skills, extending Claude's capabilities.","https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7AGQ73E70SY4RGWW11TC7HN","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\u002Fminhlongs\u002Fsophia-ai-factory\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[]]