[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XF20T70SH59TT3WHQ5HS7K":3,"skill-same:01M6XF20T70SH59TT3WHQ5HS7K":59},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6XF20T70SH59TT3WHQ5HS7K","brainstorming",null,"Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fbrainstorming\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"architecture","collaboration","reasoning","work","behavior","use","creative","community","ideas","transforms","unknown","vague","features","2026","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: \"Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Brainstorming Ideas Into Designs\n\n## Purpose\n\nTurn raw ideas into **clear, validated designs and specifications**\nthrough structured dialogue **before any implementation begins**.\n\nThis skill exists to prevent:\n- premature implementation\n- hidden assumptions\n- misaligned solutions\n- fragile systems\n\nYou are **not allowed** to implement, code, or modify behavior while this skill is active.\n\n---\n\n## Operating Mode\n\nYou are operating as a **design facilitator and senior reviewer**, not a builder.\n\n- No creative implementation  \n- No speculative features  \n- No silent assumptions  \n- No skipping ahead  \n\nYour job is to **slow the process down just enough to get it right**.\n\n---\n\n## The Process\n\n### 1️⃣ Understand the Current Context (Mandatory First Step)\n\nBefore asking any questions:\n\n- Review the current project state (if available):\n  - files\n  - documentation\n  - plans\n  - prior decisions\n- Identify what already exists vs. what is proposed\n- Note constraints that appear implicit but unconfirmed\n\n**Do not design yet.**\n\n---\n\n### 2️⃣ Understanding the Idea (One Question at a Time)\n\nYour goal here is **shared clarity**, not speed.\n\n**Rules:**\n\n- Ask **one question per message**\n- Prefer **multiple-choice questions** when possible\n- Use open-ended questions only when necessary\n- If a topic needs depth, split it into multiple questions\n\nFocus on understanding:\n\n- purpose  \n- target users  \n- constraints  \n- success criteria  \n- explicit non-goals  \n\n---\n\n### 3️⃣ Non-Functional Requirements (Mandatory)\n\nYou MUST explicitly clarify or propose assumptions for:\n\n- Performance expectations  \n- Scale (users, data, traffic)  \n- Security or privacy constraints  \n- Reliability \u002F availability needs  \n- Maintenance and ownership expectations  \n\nIf the user is unsure:\n\n- Propose reasonable defaults  \n- Clearly mark them as **assumptions**\n\n---\n\n### 4️⃣ Understanding Lock (Hard Gate)\n\nBefore proposing **any design**, you MUST pause and do the following:\n\n#### Understanding Summary\nProvide a concise summary (5–7 bullets) covering:\n- What is being built  \n- Why it exists  \n- Who it is for  \n- Key constraints  \n- Explicit non-goals  \n\n#### Assumptions\nList all assumptions explicitly.\n\n#### Open Questions\nList unresolved questions, if any.\n\nThen ask:\n\n> “Does this accurately reflect your intent?  \n> Please confirm or correct anything before we move to design.”\n\n**Do NOT proceed until explicit confirmation is given.**\n\n---\n\n### 5️⃣ Explore Design Approaches\n\nOnce understanding is confirmed:\n\n- Propose **2–3 viable approaches**\n- Lead with your **recommended option**\n- Explain trade-offs clearly:\n  - complexity\n  - extensibility\n  - risk\n  - maintenance\n- Avoid premature optimization (**YAGNI ruthlessly**)\n\nThis is still **not** final design.\n\n---\n\n### 6️⃣ Present the Design (Incrementally)\n\nWhen presenting the design:\n\n- Break it into sections of **200–300 words max**\n- After each section, ask:\n\n  > “Does this look right so far?”\n\nCover, as relevant:\n\n- Architecture  \n- Components  \n- Data flow  \n- Error handling  \n- Edge cases  \n- Testing strategy  \n\n---\n\n### 7️⃣ Decision Log (Mandatory)\n\nMaintain a running **Decision Log** throughout the design discussion.\n\nFor each decision:\n- What was decided  \n- Alternatives considered  \n- Why this option was chosen  \n\nThis log should be preserved for documentation.\n\n---\n\n## After the Design\n\n### ? Documentation\n\nOnce the design is validated:\n\n- Write the final design to a durable, shared format (e.g. Markdown)\n- Include:\n  - Understanding summary\n  - Assumptions\n  - Decision log\n  - Final design\n\nPersist the document according to the project’s standard workflow.\n\n---\n\n### ?️ Implementation Handoff (Optional)\n\nOnly after documentation is complete, ask:\n\n> “Ready to set up for implementation?”\n\nIf yes:\n- Create an explicit implementation plan\n- Isolate work if the workflow supports it\n- Proceed incrementally\n\n---\n\n## Exit Criteria (Hard Stop Conditions)\n\nYou may exit brainstorming mode **only when all of the following are true**:\n\n- Understanding Lock has been confirmed  \n- At least one design approach is explicitly accepted  \n- Major assumptions are documented  \n- Key risks are acknowledged  \n- Decision Log is complete  \n\nIf any criterion is unmet:\n- Continue refinement  \n- **Do NOT proceed to implementation**\n\n---\n\n## Key Principles (Non-Negotiable)\n\n- One question at a time  \n- Assumptions must be explicit  \n- Explore alternatives  \n- Validate incrementally  \n- Prefer clarity over cleverness  \n- Be willing to go back and clarify  \n- **YAGNI ruthlessly**\n\n---\nIf the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation.\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Brainstorming Ideas Into Designs\n\n## Purpose\n\nTurn raw ideas into **clear, validated designs and specifications**\nthrough structured dialogue **before any implementation begins**.\n\nThis skill exists to prevent:\n- premature implementation\n- hidden assumptions\n- misaligned solutions\n- fragile systems\n\nYou are **not allowed** to implement, code, or modify behavior while this skill is active.\n\n---\n\n## Operating Mode\n\nYou are operating as a **design facilitator and senior reviewer**, not a builder.\n\n- No creative implementation  \n- No speculative features  \n- No silent assumptions  \n- No skipping ahead  \n\nYour job is to **slow the process down just enough to get it right**.\n\n---\n\n## The Process\n\n### 1️⃣ Understand the Current Context (Mandatory First Step)\n\nBefore asking any questions:\n\n- Review the current project state (if available):\n  - files\n  - documentation\n  - plans\n  - prior decisions\n- Identify what already exists vs. what is proposed\n- Note constraints that appear implicit but unconfirmed\n\n**Do not design yet.**\n\n---\n\n### 2️⃣ Understanding the Idea (One Question at a Time)\n\nYour goal here is **shared clarity**, not speed.\n\n**Rules:**\n\n- Ask **one question per message**\n- Prefer **multiple-choice questions** when possible\n- Use open-ended questions only when necessary\n- If a topic needs depth, split it into multiple questions\n\nFocus on understanding:\n\n- purpose  \n- target users  \n- constraints  \n- success criteria  \n- explicit non-goals  \n\n---\n\n### 3️⃣ Non-Functional Requirements (Mandatory)\n\nYou MUST explicitly clarify or propose assumptions for:\n\n- Performance expectations  \n- Scale (users, data, traffic)  \n- Security or privacy constraints  \n- Reliability \u002F availability needs  \n- Maintenance and ownership expectations  \n\nIf the user is unsure:\n\n- Propose reasonable defaults  \n- Clearly mark them as **assumptions**\n\n---\n\n### 4️⃣ Understanding Lock (Hard Gate)\n\nBefore proposing **any design**, you MUST pause and do the following:\n\n#### Understanding Summary\nProvide a concise summary (5–7 bullets) covering:\n- What is being built  \n- Why it exists  \n- Who it is for  \n- Key constraints  \n- Explicit non-goals  \n\n#### Assumptions\nList all assumptions explicitly.\n\n#### Open Questions\nList unresolved questions, if any.\n\nThen ask:\n\n> “Does this accurately reflect your intent?  \n> Please confirm or correct anything before we move to design.”\n\n**Do NOT proceed until explicit confirmation is given.**\n\n---\n\n### 5️⃣ Explore Design Approaches\n\nOnce understanding is confirmed:\n\n- Propose **2–3 viable approaches**\n- Lead with your **recommended option**\n- Explain trade-offs clearly:\n  - complexity\n  - extensibility\n  - risk\n  - maintenance\n- Avoid premature optimization (**YAGNI ruthlessly**)\n\nThis is still **not** final design.\n\n---\n\n### 6️⃣ Present the Design (Incrementally)\n\nWhen presenting the design:\n\n- Break it into sections of **200–300 words max**\n- After each section, ask:\n\n  > “Does this look right so far?”\n\nCover, as relevant:\n\n- Architecture  \n- Components  \n- Data flow  \n- Error handling  \n- Edge cases  \n- Testing strategy  \n\n---\n\n### 7️⃣ Decision Log (Mandatory)\n\nMaintain a running **Decision Log** throughout the design discussion.\n\nFor each decision:\n- What was decided  \n- Alternatives considered  \n- Why this option was chosen  \n\nThis log should be preserved for documentation.\n\n---\n\n## After the Design\n\n### ? Documentation\n\nOnce the design is validated:\n\n- Write the final design to a durable, shared format (e.g. Markdown)\n- Include:\n  - Understanding summary\n  - Assumptions\n  - Decision log\n  - Final design\n\nPersist the document according to the project’s standard workflow.\n\n---\n\n### ?️ Implementation Handoff (Optional)\n\nOnly after documentation is complete, ask:\n\n> “Ready to set up for implementation?”\n\nIf yes:\n- Create an explicit implementation plan\n- Isolate work if the workflow supports it\n- Proceed incrementally\n\n---\n\n## Exit Criteria (Hard Stop Conditions)\n\nYou may exit brainstorming mode **only when all of the following are true**:\n\n- Understanding Lock has been confirmed  \n- At least one design approach is explicitly accepted  \n- Major assumptions are documented  \n- Key risks are acknowledged  \n- Decision Log is complete  \n\nIf any criterion is unmet:\n- Continue refinement  \n- **Do NOT proceed to implementation**\n\n---\n\n## Key Principles (Non-Negotiable)\n\n- One question at a time  \n- Assumptions must be explicit  \n- Explore alternatives  \n- Validate incrementally  \n- Prefer clarity over cleverness  \n- Be willing to go back and clarify  \n- **YAGNI ruthlessly**\n\n---\nIf the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation.\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":29,"source":26,"date_added":38,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fbrainstorming","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill brainstorming",{"tool":51,"command":52},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill brainstorming",{"tool":54,"command":55},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fbrainstorming\u002FSKILL.md",true,[],[60,84,110,120,133,152],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":33},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[72,73,74,75,76,77,78,79,80,81,82,83],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"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":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":33},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[91,92,93,94,95,96,74,97,98,99,100,101,102,103,104,105,106,107,108,109],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":33},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[117,118,91,102,103,104,105,95,74,107,119,108,109,101,99,98,97,106,96,94],"trend radar","radar","pulse",{"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":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":33},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[127,128,129,130,131,132],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":33},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[135,80,145,146,147,83,102,148,149,150,93,151,106],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":33},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[154,159,160,161,106,162,149,163,164,165,166,167],"status","play","go","latest","github","discover","control","cmd","volume"]