[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75AMA2K87PE03ATXV512Z58":3,"skill-same:01M75AMA2K87PE03ATXV512Z58":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":20,"frontMatter":21,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75AMA2K87PE03ATXV512Z58","brainstorming",null,"0xRayAI\u002Fxray","0xRayAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274879952?v=4","01M75AEEVWK4S4G4N25HAYGB9V","01M75AEEWMHN7H4PQVCJS2938J",2,"MIT","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fdocs\u002Farchive\u002Fintegrations-costume\u002Fbrainstorming\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: brainstorming\nsource: antigravity-awesome-skills\nattribution: |\n  Originally from https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills\n  License: MIT (see LICENSE.antigravity)\nconverted: 2026-03-23T22:48:02.781Z\n---\n\n---\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","---\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",{"name":5,"source":22,"converted":23,"attribution":24},"antigravity-awesome-skills",1774306082781,"Originally from https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills\nLicense: MIT (see LICENSE.antigravity)\n","main","232f39ec089591afb70f9327b481e7428162a97e","docs\u002Farchive\u002Fintegrations-costume\u002Fbrainstorming",3,"https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray","https:\u002F\u002Fgithub.com\u002F0xRayAI","2026-11-13 22:20:55",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add 0xRayAI\u002Fxray --skill brainstorming",{"tool":38,"command":39},"bunx","bunx skills add 0xRayAI\u002Fxray --skill brainstorming",{"tool":41,"command":42},"pnpm","pnpm dlx skills add 0xRayAI\u002Fxray --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fdocs\u002Farchive\u002Fintegrations-costume\u002Fbrainstorming\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":17},"01M75AXZY4TX8Z6WF2G4EKYMAA","xray-orchestrator","Main orchestration skill for xray agents.\nProvides commands to coordinate agent work and invoke xray APIs\nthrough the local HTTP API server.","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fxray-orchestrator\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":17},"01M75AXT1TB9SX9JVSP16C85BP","ui-ux-design","User interface and user experience design with mobile-first approach, cognitive simplicity, and accessibility-first principles","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fui-ux-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":17},"01M75AXQERT17BTCCY7Y1HPXTA","testing-strategy","Design comprehensive testing strategies and optimize test coverage","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":17},"01M75AXM7TRVQXXKT0C287VWN7","testing-best-practices","Testing best practices and quality assurance","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":17},"01M75AXHAJZK2JBVG638K3RZ5F","tech-writer","Documentation writer for API docs, READMEs, ADRs, changelogs, and developer experience","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftech-writer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":17},"01M75AXE7P5MX15WA16TGFKJQG","strategist","Strategic guidance and complex problem-solving with architectural decision-making and risk analysis","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fstrategist\u002FSKILL.md",[],[]]