[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71T28HAMRFS3DDPBRGW7WZZ":3,"skill-same:01M71T28HAMRFS3DDPBRGW7WZZ":64},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M71T28HAMRFS3DDPBRGW7WZZ","brainstorm",null,"Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.","mantrandev\u002Fmydotbot","mantrandev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F120156244?v=4","01M71SZTTYS2EQQWXVKD3N63XF","maybe","01M71SZTVY4J7DYNEST4Q4DEV9",2,"MIT","https:\u002F\u002Fgithub.com\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fbrainstorm\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"use","feasibility","trade","solutions","ideation","with","architecture","analysis","decisions","technical","design","assessment","for","feature","problem","exploration","2026-11-10 13:02:02",false,"---\nname: 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":40,"description":7,"argument-hint":41},"2.0.0","[topic or problem]","main","eef4c392da382583063c3d53246bc0e899c6fdaa","ai\u002Fweb\u002Fbrainstorm",1,"https:\u002F\u002Fgithub.com\u002Fmantrandev\u002Fmydotbot","https:\u002F\u002Fgithub.com\u002Fmantrandev","Promt monkey ","2026-11-11 14:16:51",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add mantrandev\u002Fmydotbot --skill brainstorm",{"tool":56,"command":57},"bunx","bunx skills add mantrandev\u002Fmydotbot --skill brainstorm",{"tool":59,"command":60},"pnpm","pnpm dlx skills add mantrandev\u002Fmydotbot --skill brainstorm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fbrainstorm\u002FSKILL.md",true,[],[65,96,120,153,180,201],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":35},"01M71T6Z4TTFZYG03A4J74K3J5","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fweb-testing\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[78,79,80,81,82,83,84,85,86,87,88,89,90,91,31,92,93,19,94,95],"testing","web","web testing","unit","vitals","browser","a11y","mobile","security","k6","target","gestures","vitest","core","e2e","cross-browser","load","automation",{"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":35},"01M71T6W6NANEWEDNSG9FVTFB6","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fweb-frameworks\u002FSKILL.md",[],[103,104,79,105,106,107,108,109,110,111,112,113,114,115,116,117,118,32,31,119],"frameworks","web frameworks","shared","app","apps","caching","react","router","strategies","server","rsc","next","ssr","rendering","turborepo","framework","Optimization",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":35},"01M71T6HRD7RKWKDKBP0TN5VPG","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fui-styling\u002FSKILL.md",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[136,137,138,139,140,141,29,142,143,144,145,146,147,148,149,150,31,151,19,152],"ui styling","styling","ui","css","Tailwind","mode","themes","design systems","components","component","layout","responsive","shadcn","color","dark","ui components","dark mode",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":35},"01M71T6DR4C0XPDXG3S81VJS3Y","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fthreejs\u002FSKILL.md",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000010","后端与接口",[155,163,164,165,166,167,168,169,170,171,107,172,173,174,175,176,177,178,179,32],"Animation","3D","processing","Audio","physics","model","actions","webgpu","effects","api","create","3d scene","shaders","post-processing","vr","add","integrations",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":35},"01M71T5W9JNWPGRJX943MMRC20","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fsequential-thinking\u002FSKILL.md",[],[187,188,189,190,33,191,31,19,192,26,193,24,194,195,196,197,198,199,200],"thinking","sequential thinking","adaptive","course","planning","apply","analyze","multi","verification","decomposition","reasoning","revision","hypothesis","capability",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":35},"01M71T5QPEKZ5ETRQQ3HYT2KDW","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\u002Fmantrandev\u002Fmydotbot\u002Fblob\u002Fmain\u002Fai\u002Fweb\u002Fresearch\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000021","资料检索与研究",[203,211,31,212,29,213,28,19,214,215,26,216,193,22,217,218,219,86],"architectures","gather","technology","best practices","requirements","scalability","solution","maintainability","Evaluation"]