[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C35SVSCZTSNBF33KG3HS3J":3,"skill-same:01M7C35SVSCZTSNBF33KG3HS3J":66},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C35SVSCZTSNBF33KG3HS3J","planning",null,"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.","Truc350\u002FWebHomeStay","Truc350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F176447042?v=4","01M7C2S7D6AAK15J66E3NDXSXK","Huỳnh Thị Thanh Trúc","01M7C2S7DTPMN5ZM8876HF8KF8",0,"MIT","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\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 .codex\u002Fbasedkit\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 .codex\u002Fbasedkit\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","af64bb75a16e8bc1847a568059b9300e09f27c4a",".agents\u002Fskills\u002Fplanning","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay","https:\u002F\u002Fgithub.com\u002FTruc350","2026-09-04 21:59:58",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Truc350\u002FWebHomeStay --skill planning",{"tool":36,"command":37},"bunx","bunx skills add Truc350\u002FWebHomeStay --skill planning",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Truc350\u002FWebHomeStay --skill planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002FSKILL.md",true,[44,50,54,58,62],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fcodebase-understanding.md","REFERENCE","参考文档",1967,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002Freferences\u002Fcodebase-understanding.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Foutput-standards.md",4567,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002Freferences\u002Foutput-standards.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fplan-organization.md",4240,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002Freferences\u002Fplan-organization.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fresearch-phase.md",1572,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002Freferences\u002Fresearch-phase.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanning\u002Freferences\u002Fsolution-design.md",[67,74,81,88,96,103],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7C3D9JFFHDYQ93YQ2NFSTXV","widget-cms","Tạo, sửa và kiểm thử widget Laravel CMS theo renderer theme\u002Fcore\u002Fplugin, layout builder, settings_schema, shortcode, hook, CSS\u002FJS và zone contract.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwidget-cms\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7C3CNZVN589PK7ZJ1JZ98JB","website-sitemap","This skill should be used to create, crawl, map, redesign, or migrate website sitemaps and information architecture from briefs, ERP data, URLs, documents, or mixed inputs.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebsite-sitemap\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7C3C36PECBZQR0RBXGE8781","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\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7C3A7X0WG8RWDDJFB9CHP0F","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\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7C39497ER4DVF3R8P9R6K41","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\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7C38TQE66MV142R5K58QJM6","theme-cms-ecommerce","This skill should be used independently to create, update, validate, or package complete Laravel CMS storefronts with product catalogs, search, promotions, cart, checkout, and responsive shopping UX.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-ecommerce\u002FSKILL.md",[],[]]