[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CS4YM4XD6FZCTA2C0S0AWC":3,"skill-same:01M6CS4YM4XD6FZCTA2C0S0AWC":62},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6CS4YM4XD6FZCTA2C0S0AWC","brainstorming",null,"You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores the OPERATOR's intent, requirements, and design before implementation.","mrtolkien\u002FGHOST","mrtolkien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8489650?v=4","01M6CS32Q934XBQQE8BDV5Z6W2","Tolki","01M6CS32VBCD47F5E27WF9W6FC",5,"MIT","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fbrainstorming\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33],"design","components","operator","coding","work","behavior","use","creative","implementation","intent","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription:\n  You MUST use this before any creative work — creating features, building components,\n  adding functionality, or modifying behavior. Explores the OPERATOR's intent,\n  requirements, and design before implementation.\navailable: coding\n---\n\n# Brainstorming Ideas Into Designs\n\n## Overview\n\nHelp turn ideas into fully formed designs and specs through natural collaborative\ndialogue.\n\nStart by understanding the current project context, then ask questions one at a time to\nrefine the idea. Once you understand what you're building, present the design and get\nOPERATOR approval.\n\n\u003CHARD-GATE>\nDo NOT start any implementation, write any code, scaffold any project, or take any\nimplementation action until you have presented a design and the OPERATOR has approved it.\nThis applies to EVERY project regardless of perceived simplicity.\n\u003C\u002FHARD-GATE>\n\n## Anti-Pattern: \"This Is Too Simple To Need A Design\"\n\nEvery project goes through this process. A todo list, a single-function utility, a\nconfig change — all of them. \"Simple\" projects are where unexamined assumptions cause\nthe most wasted work. The design can be short (a few sentences for truly simple\nprojects), but you MUST present it and get approval.\n\n## Checklist\n\nYou MUST use `todo(action: \"plan\", ...)` to create a task for each of these items and\ncomplete them in order:\n\n1. **Explore project context** — check files, docs, recent commits\n2. **Ask clarifying questions** — one at a time, understand purpose\u002Fconstraints\u002Fsuccess\n   criteria\n3. **Propose 2-3 approaches** — with trade-offs and your recommendation\n4. **Present design** — in sections scaled to their complexity, get OPERATOR approval\n   after each section\n5. **Write design doc** — save to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md` and commit\n6. **Transition to implementation** — read the `writing-plans` skill to create\n   implementation plan\n\n## Process Flow\n\n```dot\ndigraph brainstorming {\n    \"Explore project context\" [shape=box];\n    \"Ask clarifying questions\" [shape=box];\n    \"Propose 2-3 approaches\" [shape=box];\n    \"Present design sections\" [shape=box];\n    \"OPERATOR approves design?\" [shape=diamond];\n    \"Write design doc\" [shape=box];\n    \"Read writing-plans skill\" [shape=doublecircle];\n\n    \"Explore project context\" -> \"Ask clarifying questions\";\n    \"Ask clarifying questions\" -> \"Propose 2-3 approaches\";\n    \"Propose 2-3 approaches\" -> \"Present design sections\";\n    \"Present design sections\" -> \"OPERATOR approves design?\";\n    \"OPERATOR approves design?\" -> \"Present design sections\" [label=\"no, revise\"];\n    \"OPERATOR approves design?\" -> \"Write design doc\" [label=\"yes\"];\n    \"Write design doc\" -> \"Read writing-plans skill\";\n}\n```\n\n**The terminal state is reading the writing-plans skill.** Do NOT jump to implementation\nor read any other skill. The ONLY next step after brainstorming is writing-plans.\n\n## The Process\n\n**Understanding the idea:**\n\n- Check out the current project state first (files, docs, recent commits)\n- Ask questions one at a time to refine the idea\n- Prefer multiple choice questions when possible, but open-ended is fine too\n- Only one question per message — if a topic needs more exploration, break it into\n  multiple questions\n- Focus on understanding: purpose, constraints, success criteria\n\n**Exploring approaches:**\n\n- Propose 2-3 different approaches with trade-offs\n- Present options conversationally with your recommendation and reasoning\n- Lead with your recommended option and explain why\n\n**Presenting the design:**\n\n- Once you believe you understand what you're building, present the design\n- Scale each section to its complexity: a few sentences if straightforward, up to\n  200-300 words if nuanced\n- Ask after each section whether it looks right so far\n- Cover: architecture, components, data flow, error handling, testing\n- Be ready to go back and clarify if something doesn't make sense\n\n## After the Design\n\n**Documentation:**\n\n- Write the validated design to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md`\n- Commit the design document to git\n\n**Implementation:**\n\n- Read the `writing-plans` skill to create a detailed implementation plan\n- Do NOT start implementing directly. writing-plans is the next step.\n\n## Key Principles\n\n- **One question at a time** — Don't overwhelm with multiple questions\n- **Multiple choice preferred** — Easier to answer than open-ended when possible\n- **YAGNI ruthlessly** — Remove unnecessary features from all designs\n- **Explore alternatives** — Always propose 2-3 approaches before settling\n- **Incremental validation** — Present design, get approval before moving on\n- **Be flexible** — Go back and clarify when something doesn't make sense\n","# Brainstorming Ideas Into Designs\n\n## Overview\n\nHelp turn ideas into fully formed designs and specs through natural collaborative\ndialogue.\n\nStart by understanding the current project context, then ask questions one at a time to\nrefine the idea. Once you understand what you're building, present the design and get\nOPERATOR approval.\n\n\u003CHARD-GATE>\nDo NOT start any implementation, write any code, scaffold any project, or take any\nimplementation action until you have presented a design and the OPERATOR has approved it.\nThis applies to EVERY project regardless of perceived simplicity.\n\u003C\u002FHARD-GATE>\n\n## Anti-Pattern: \"This Is Too Simple To Need A Design\"\n\nEvery project goes through this process. A todo list, a single-function utility, a\nconfig change — all of them. \"Simple\" projects are where unexamined assumptions cause\nthe most wasted work. The design can be short (a few sentences for truly simple\nprojects), but you MUST present it and get approval.\n\n## Checklist\n\nYou MUST use `todo(action: \"plan\", ...)` to create a task for each of these items and\ncomplete them in order:\n\n1. **Explore project context** — check files, docs, recent commits\n2. **Ask clarifying questions** — one at a time, understand purpose\u002Fconstraints\u002Fsuccess\n   criteria\n3. **Propose 2-3 approaches** — with trade-offs and your recommendation\n4. **Present design** — in sections scaled to their complexity, get OPERATOR approval\n   after each section\n5. **Write design doc** — save to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md` and commit\n6. **Transition to implementation** — read the `writing-plans` skill to create\n   implementation plan\n\n## Process Flow\n\n```dot\ndigraph brainstorming {\n    \"Explore project context\" [shape=box];\n    \"Ask clarifying questions\" [shape=box];\n    \"Propose 2-3 approaches\" [shape=box];\n    \"Present design sections\" [shape=box];\n    \"OPERATOR approves design?\" [shape=diamond];\n    \"Write design doc\" [shape=box];\n    \"Read writing-plans skill\" [shape=doublecircle];\n\n    \"Explore project context\" -> \"Ask clarifying questions\";\n    \"Ask clarifying questions\" -> \"Propose 2-3 approaches\";\n    \"Propose 2-3 approaches\" -> \"Present design sections\";\n    \"Present design sections\" -> \"OPERATOR approves design?\";\n    \"OPERATOR approves design?\" -> \"Present design sections\" [label=\"no, revise\"];\n    \"OPERATOR approves design?\" -> \"Write design doc\" [label=\"yes\"];\n    \"Write design doc\" -> \"Read writing-plans skill\";\n}\n```\n\n**The terminal state is reading the writing-plans skill.** Do NOT jump to implementation\nor read any other skill. The ONLY next step after brainstorming is writing-plans.\n\n## The Process\n\n**Understanding the idea:**\n\n- Check out the current project state first (files, docs, recent commits)\n- Ask questions one at a time to refine the idea\n- Prefer multiple choice questions when possible, but open-ended is fine too\n- Only one question per message — if a topic needs more exploration, break it into\n  multiple questions\n- Focus on understanding: purpose, constraints, success criteria\n\n**Exploring approaches:**\n\n- Propose 2-3 different approaches with trade-offs\n- Present options conversationally with your recommendation and reasoning\n- Lead with your recommended option and explain why\n\n**Presenting the design:**\n\n- Once you believe you understand what you're building, present the design\n- Scale each section to its complexity: a few sentences if straightforward, up to\n  200-300 words if nuanced\n- Ask after each section whether it looks right so far\n- Cover: architecture, components, data flow, error handling, testing\n- Be ready to go back and clarify if something doesn't make sense\n\n## After the Design\n\n**Documentation:**\n\n- Write the validated design to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md`\n- Commit the design document to git\n\n**Implementation:**\n\n- Read the `writing-plans` skill to create a detailed implementation plan\n- Do NOT start implementing directly. writing-plans is the next step.\n\n## Key Principles\n\n- **One question at a time** — Don't overwhelm with multiple questions\n- **Multiple choice preferred** — Easier to answer than open-ended when possible\n- **YAGNI ruthlessly** — Remove unnecessary features from all designs\n- **Explore alternatives** — Always propose 2-3 approaches before settling\n- **Incremental validation** — Present design, get approval before moving on\n- **Be flexible** — Go back and clarify when something doesn't make sense\n",{"name":5,"available":27,"description":7},"main","083d96429a2d05526f8a294b83c74f0336670def","assets\u002Fskills\u002Fsuperpowers\u002Fbrainstorming",0,"https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST","https:\u002F\u002Fgithub.com\u002Fmrtolkien","https:\u002F\u002Fblog.tolki.dev","Data Engineer \u002F Esports \u002F Keyboards","2026-04-24 15:41:08",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add mrtolkien\u002FGHOST --skill brainstorming",{"tool":54,"command":55},"bunx","bunx skills add mrtolkien\u002FGHOST --skill brainstorming",{"tool":57,"command":58},"pnpm","pnpm dlx skills add mrtolkien\u002FGHOST --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fbrainstorming\u002Fskill.md",true,[],[63,89,111,128,137,148],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":34},"01M6CS613RWD9CFJ3KFX47V1DS","system-management","Use when reading or changing GHOST configuration (providers, models, timing, compaction, services, any config.toml key), adding or switching LLM providers, answering questions about GHOST's own features or capabilities, a CLI tool is missing or \"not found\", services need starting\u002Fstopping\u002Fdebugging, updating GHOST to a newer version, managing the Nix shell environment, or troubleshooting GHOST setup.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsystem-management\u002Fskill.md",[],[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,30,86,87,88],"system management","management","system","shell","cli","nix","config","setup","debugging","capabilities","services","Providers","ghost","tool","troubleshooting","environment","version","models","configuration",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":106,"publishedAt":34},"01M6CS5XTK2884R9HE15YR8YZM","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fwriting-skills\u002Fskill.md",[95,98,101],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[107,108,27,28,109,30,110],"writing skills","writing","editing","deployment",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":119,"publishedAt":34},"01M6CS5V737R1DVB3TZEK0C6WT","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code. Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fwriting-plans\u002Fskill.md",[117,118],{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[120,108,121,122,123,27,124,125,30,126,32,127],"writing plans","spec","code","ZeRO","write","context","engineer","task",{"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":34},"01M6CS5S5S0YY56686G5CQ0WMP","verification","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fverification\u002Fskill.md",[],[130,27,28,30,135,136],"evidence","claim",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":34},"01M6CS5PD2ZSFWYRDZSACNTAJY","tdd","Use when implementing any feature or bugfix, before writing implementation code. Write the test first. Watch it fail. Write minimal code to pass.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Ftdd\u002Fskill.md",[143],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[139,108,122,145,27,124,30,146,32,147],"first","minimal","test",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":34},"01M6CS5K5WE2SHF1YV8D9C4C77","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fsystematic-debugging\u002Fskill.md",[154],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[156,78,29,30,27,147,157],"systematic debugging","bug"]