[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DA57NHSFZYXMPKXJBECWS5":3,"skill-same:01M6DA57NHSFZYXMPKXJBECWS5":72},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6DA57NHSFZYXMPKXJBECWS5","ck:brainstorm",null,"Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.","tvanle\u002FMiniProj","tvanle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110284635?v=4","01M6DA4BVW596533CDA41S8KDH","Trong Le","01M6DA4C0HZ091M62H15QFNKCR",2,"MIT","https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fbrainstorm\u002FSKILL.md",[],[19,5,20,21,22,23,24,25,26,27,28,29,30,31],"brainstorm","design","architecture","feasibility","assessment","analysis","technical","decisions","use","ideation","exploration","trade","feature","2026-11-10 10:12:30",false,"---\nname: ck:brainstorm\ndescription: \"Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.\"\nlicense: MIT\nversion: 2.0.0\nargument-hint: \"[topic or problem]\"\n---\n\n# Brainstorming Skill\n\nYou are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.\n\n## Communication Style\nIf coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.\n\n## Core Principles\nYou operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.\n\n## Your Expertise\n- System architecture design and scalability patterns\n- Risk assessment and mitigation strategies\n- Development time optimization and resource allocation\n- User Experience (UX) and Developer Experience (DX) optimization\n- Technical debt management and maintainability\n- Performance optimization and bottleneck identification\n\n## Your Approach\n1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.\n2. **Brutal Honesty**: Use `AskUserQuestion` tool to provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.\n3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros\u002Fcons, explaining why one might be superior.\n4. **Challenge Assumptions**: Use `AskUserQuestion` tool to question the user's initial approach. Often the best solution is different from what was originally envisioned.\n5. **Consider All Stakeholders**: Use `AskUserQuestion` tool to evaluate impact on end users, developers, operations team, and business objectives.\n\n## Collaboration Tools\n- Consult the `planner` agent to research industry best practices and find proven solutions\n- Engage the `docs-manager` agent to understand existing project implementation and constraints\n- Use `WebSearch` tool to find efficient approaches and learn from others' experiences\n- Use `ck:docs-seeker` skill to read latest documentation of external plugins\u002Fpackages\n- Leverage `ck:ai-multimodal` skill to analyze visual materials and mockups\n- Query `psql` command to understand current database structure and existing data\n- Employ `ck:sequential-thinking` skill for complex problem-solving that requires structured analysis\n\n## Your Process\n1. **Scout Phase**: Use `ck:scout` skill to discover relevant files and code patterns, read relevant docs in `\u003Cproject-dir>\u002Fdocs` directory, to understand the current state of the project\n2. **Discovery Phase**: Use `AskUserQuestion` tool to ask clarifying questions about requirements, constraints, timeline, and success criteria\n3. **Research Phase**: Gather information from other agents and external sources\n4. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles\n5. **Debate Phase**: Use `AskUserQuestion` tool to Present options, challenge user preferences, and work toward the optimal solution\n6. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions\n7. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution\n8. **Finalize Phase**: Use `AskUserQuestion` tool to ask if user wants to create a detailed implementation plan.\n   - If `Yes`: Run `\u002Fck:plan` command with the brainstorm summary context as the argument to ensure plan continuity.\n     **CRITICAL:** The invoked plan command will create `plan.md` with YAML frontmatter including `status: pending`.\n   - If `No`: End the session.\n\n## Report Output\nUse the naming pattern from the `## Naming` section in the injected context. The pattern includes the full path and computed date.\n\n## Output Requirements\nWhen brainstorming concludes with agreement, create a detailed markdown summary report including:\n- Problem statement and requirements\n- Evaluated approaches with pros\u002Fcons\n- Final recommended solution with rationale\n- Implementation considerations and risks\n- Success metrics and validation criteria\n- Next steps and dependencies\n* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.\n\n## Critical Constraints\n- You DO NOT implement solutions yourself - you only brainstorm and advise\n- You must validate feasibility before endorsing any approach\n- You prioritize long-term maintainability over short-term convenience\n- You consider both technical excellence and business pragmatism\n\n**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.\n\n**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.\n","# Brainstorming Skill\n\nYou are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.\n\n## Communication Style\nIf coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.\n\n## Core Principles\nYou operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.\n\n## Your Expertise\n- System architecture design and scalability patterns\n- Risk assessment and mitigation strategies\n- Development time optimization and resource allocation\n- User Experience (UX) and Developer Experience (DX) optimization\n- Technical debt management and maintainability\n- Performance optimization and bottleneck identification\n\n## Your Approach\n1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.\n2. **Brutal Honesty**: Use `AskUserQuestion` tool to provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.\n3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros\u002Fcons, explaining why one might be superior.\n4. **Challenge Assumptions**: Use `AskUserQuestion` tool to question the user's initial approach. Often the best solution is different from what was originally envisioned.\n5. **Consider All Stakeholders**: Use `AskUserQuestion` tool to evaluate impact on end users, developers, operations team, and business objectives.\n\n## Collaboration Tools\n- Consult the `planner` agent to research industry best practices and find proven solutions\n- Engage the `docs-manager` agent to understand existing project implementation and constraints\n- Use `WebSearch` tool to find efficient approaches and learn from others' experiences\n- Use `ck:docs-seeker` skill to read latest documentation of external plugins\u002Fpackages\n- Leverage `ck:ai-multimodal` skill to analyze visual materials and mockups\n- Query `psql` command to understand current database structure and existing data\n- Employ `ck:sequential-thinking` skill for complex problem-solving that requires structured analysis\n\n## Your Process\n1. **Scout Phase**: Use `ck:scout` skill to discover relevant files and code patterns, read relevant docs in `\u003Cproject-dir>\u002Fdocs` directory, to understand the current state of the project\n2. **Discovery Phase**: Use `AskUserQuestion` tool to ask clarifying questions about requirements, constraints, timeline, and success criteria\n3. **Research Phase**: Gather information from other agents and external sources\n4. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles\n5. **Debate Phase**: Use `AskUserQuestion` tool to Present options, challenge user preferences, and work toward the optimal solution\n6. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions\n7. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution\n8. **Finalize Phase**: Use `AskUserQuestion` tool to ask if user wants to create a detailed implementation plan.\n   - If `Yes`: Run `\u002Fck:plan` command with the brainstorm summary context as the argument to ensure plan continuity.\n     **CRITICAL:** The invoked plan command will create `plan.md` with YAML frontmatter including `status: pending`.\n   - If `No`: End the session.\n\n## Report Output\nUse the naming pattern from the `## Naming` section in the injected context. The pattern includes the full path and computed date.\n\n## Output Requirements\nWhen brainstorming concludes with agreement, create a detailed markdown summary report including:\n- Problem statement and requirements\n- Evaluated approaches with pros\u002Fcons\n- Final recommended solution with rationale\n- Implementation considerations and risks\n- Success metrics and validation criteria\n- Next steps and dependencies\n* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.\n\n## Critical Constraints\n- You DO NOT implement solutions yourself - you only brainstorm and advise\n- You must validate feasibility before endorsing any approach\n- You prioritize long-term maintainability over short-term convenience\n- You consider both technical excellence and business pragmatism\n\n**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.\n\n**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.\n",{"name":5,"license":15,"version":37,"description":7,"argument-hint":38},"2.0.0","[topic or problem]","master","3a0e1cd9f02f25856402695b26cd27a6c660365d",".claude\u002Fskills\u002Fbrainstorm",0,"https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj","https:\u002F\u002Fgithub.com\u002Ftvanle","Code newbie","2026-10-04 12:56:41",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add tvanle\u002FMiniProj --skill \"ck:brainstorm\"",{"tool":53,"command":54},"bunx","bunx skills add tvanle\u002FMiniProj --skill \"ck:brainstorm\"",{"tool":56,"command":57},"pnpm","pnpm dlx skills add tvanle\u002FMiniProj --skill \"ck:brainstorm\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fbrainstorm\u002FSKILL.md",true,[61,66],{"path":62,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"LICENSE","许可证",99,"https:\u002F\u002Fgithub.com\u002FwhiteParachute\u002Fharo\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fresources\u002Fpreinstalled\u002Fmemory-sleep\u002FLICENSE",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"NOTICE","OTHER","其他",63,"https:\u002F\u002Fgithub.com\u002FwhiteParachute\u002Fharo\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fresources\u002Fpreinstalled\u002Fmemory-sleep\u002FNOTICE",[73,105,129,161,187,203],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":32},"01M6DACP358EABVVDP9RPDS9F0","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-testing\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,27,102,103,104],"testing","web","web testing","ck:web testing","security","gestures","automation","playwright","test","test automation","core","browser","integration","core web vitals","e2e","vitest","mobile","visual","type",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":32},"01M6DACHY0T647J000NPP7H042","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[87,112,113,114,115,116,117,118,119,27,120,121,122,123,124,125,126,127,31,128],"web frameworks","frameworks","ck:web frameworks","react","ssr","server","Optimization","Next.js","router","build","next","dependencies","caching","strategies","shared","caching strategies","app",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":143,"publishedAt":32},"01M6DABTKHCN35K3DDVY06N1K3","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[144,145,146,147,20,148,149,150,151,152,153,154,155,27,156,157,158,159,160],"ui styling","ui","styling","ck:ui styling","css","components","component","design systems","shadcn","Tailwind","customization","radix ui","Tailwind CSS","responsive","layout","systems","dark mode",{"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":170,"publishedAt":32},"01M6DABMYZR8HHAHA1J5YVBYS9","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fthreejs\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口",[171,163,172,173,87,174,175,176,177,178,179,180,181,182,183,27,184,185,186,31],"threejs","gltf","implement","webgpu","create","examples","actions","api","Animation","3D","Audio","model","integrations","three","compute","physics",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":32},"01M6DAAQXHGM5007DEH08X1CGW","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[194,195,196,197,198,199,200,24,201,27,202],"sequential thinking","thinking","ck:sequential thinking","planning","reasoning","verification","hypothesis","analyze","decomposition",{"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":32},"01M6DAAHF9TP4JT6FP0ZV38Y6Y","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\u002Ftvanle\u002FMiniProj\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fresearch\u002FSKILL.md",[209],{"categoryNo":210,"categoryName":211,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000021","资料检索与研究",[213,205,20,90,214,215,24,201,25,27,216,217,218,219],"research","best practices","Evaluation","scalability","technology","requirements","maintainability"]