[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CB7FGCAFQX40TX1MMAQ38M":3,"skill-same:01M6CB7FGCAFQX40TX1MMAQ38M":71},{"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":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M6CB7FGCAFQX40TX1MMAQ38M","planning",null,"Use when you need to plan technical solutions that are scalable, secure, and maintainable.","vienkmt\u002FTermiPro","vienkmt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20434534?v=4","01M6C6SZP4N31HMXD9G3PBSAM3","VienLv","01M6C6SZTVB1M4VE0BMW58YG0B",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002FSKILL.md",[],[5,19,20,21,22],"secure","plan","technical","use","2026-11-10 10:12:30",false,"---\nname: planning\ndescription: Use when you need to plan technical solutions that are scalable, secure, and maintainable.\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### 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 .claude\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### 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 .claude\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","812c56c3373a712c9368c5a705fe9f1c7604fbbd","TermiMax\u002F.claude\u002Fskills\u002Fplanning","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro","https:\u002F\u002Fgithub.com\u002Fvienkmt","https:\u002F\u002Fwww.facebook.com\u002Fmark","2026-08-09 20:17:36",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add vienkmt\u002FTermiPro --skill planning",{"tool":41,"command":42},"bunx","bunx skills add vienkmt\u002FTermiPro --skill planning",{"tool":44,"command":45},"pnpm","pnpm dlx skills add vienkmt\u002FTermiPro --skill planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcodebase-understanding.md","REFERENCE","参考文档",1967,"https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002Freferences\u002Fcodebase-understanding.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Foutput-standards.md",4567,"https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002Freferences\u002Foutput-standards.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fplan-organization.md",4232,"https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002Freferences\u002Fplan-organization.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fresearch-phase.md",1572,"https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002Freferences\u002Fresearch-phase.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fplanning\u002Freferences\u002Fsolution-design.md",[72,98,128,151,164,175],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":23},"01M6CB8V1E4APYVGPP6XVVVZVV","web-frameworks","Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined\u002Ffilled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[79,80,81,82,83,84,22,85,86,87,88,89,90,91,92,93,94,95,96,97],"web frameworks","web","applications","parallel execution","up","router","monorepo","parallel","stack","projects","Next.js","execution","server","icons","packages","libraries","react","components","performance",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":114,"publishedAt":23},"01M6CB8D4MXVYSA7Q8F0VXBR0T","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[115,116,117,118,119,120,81,121,122,123,96,124,125,126,127,22],"styling","ui","ui styling","user","Tailwind","first","shadcn","design systems","create","canvas","css","design","radix ui",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":23},"01M6CB89DT68MMYZKTWKDT0ARW","threejs","Build immersive 3D web experiences with Three.js - WebGL\u002FWebGPU library for scenes, cameras, geometries, materials, lights, animations, loaders, post-processing, shaders (including node-based TSL), compute, physics, VR\u002FXR, and advanced rendering. Use when creating 3D visualizations, games, interactive graphics, data viz, product configurators, architectural walkthroughs, or WebGL\u002FWebGPU applications. Covers OrbitControls, GLTF\u002FFBX loading, PBR materials, shadow mapping, post-processing effects (bloom, SSAO, SSR), custom shaders, instancing, LOD, animation systems, and WebXR.","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[130,135,136,81,137,138,22,139,140,141,142,143,144,145,80,146,147,148,149,150],"interactive","visualizations","node","Shadow","pbr","Animation","data","product","shaders","ssr","webgpu","webxr","webgl","3D","graphics","gltf",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":23},"01M6CB7Y4KZKH2T51JF2THHAFB","sequential-thinking","Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[158,22,159,160,161,162,5,163],"sequential thinking","work","analysis","hypothesis","verification","tasks",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":23},"01M6CB7VW0MXYN6P7TV9142X11","research","Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fresearch\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000021","资料检索与研究",[166,21,174,20,19,22],"analyze",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":23},"01M6CB7B61PKARVSEBJCXQ5PHV","payment-integration","Implement payment integrations with SePay (Vietnamese payment gateway with VietQR, bank transfers, cards) and Polar (global SaaS monetization platform with subscriptions, usage-based billing, automated benefits). Use when integrating payment processing, implementing checkout flows, managing subscriptions, handling webhooks, processing bank transfers, generating QR codes, automating benefit delivery, or building billing systems. Supports authentication (API keys, OAuth2), product management, customer portals, tax compliance (Polar as MoR), and comprehensive SDK integrations (Node.js, PHP, Python, Go, Laravel, Next.js).","https:\u002F\u002Fgithub.com\u002Fvienkmt\u002FTermiPro\u002Fblob\u002Fmain\u002FTermiMax\u002F.claude\u002Fskills\u002Fpayment-integration\u002FSKILL.md",[],[182,183,184,185,186,22,187,137,188,89,189,190,191,192,142,193,194,195,196,197],"payment integration","integration","laravel","product management","webhooks","tax","integrations","api","saas","compliance","gateway","authentication","customer","implement","sdk","python"]