[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FSKXWZ0VDKF2B31CEJR0X":3,"skill-same:01M75FSKXWZ0VDKF2B31CEJR0X":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75FSKXWZ0VDKF2B31CEJR0X","Brainstorming Ideas Into Designs",null,"Interactive idea refinement using Socratic method to develop fully-formed designs","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbrainstorming-ideas-into-designs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: Brainstorming Ideas Into Designs\ndescription: Interactive idea refinement using Socratic method to develop fully-formed designs\nwhen_to_use: when partner describes any feature or project idea, before writing code or implementation plans\nversion: 2.2.0\n---\n\n# Brainstorming Ideas Into Designs\n\n## Overview\n\nTransform rough ideas into fully-formed designs through structured questioning and alternative exploration.\n\n**Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation.\n\n**Announce at start:** \"I'm using the Brainstorming skill to refine your idea into a design.\"\n\n## The Process\n\n### Phase 1: Understanding\n- Check current project state in working directory\n- Ask ONE question at a time to refine the idea\n- Prefer multiple choice when possible\n- Gather: Purpose, constraints, success criteria\n\n### Phase 2: Exploration\n- Propose 2-3 different approaches\n- For each: Core architecture, trade-offs, complexity assessment\n- Ask your human partner which approach resonates\n\n### Phase 3: Design Presentation\n- Present in 200-300 word sections\n- Cover: Architecture, components, data flow, error handling, testing\n- Ask after each section: \"Does this look right so far?\"\n\n### Phase 4: Worktree Setup (for implementation)\nWhen design is approved and implementation will follow:\n- Announce: \"I'm using the Using Git Worktrees skill to set up an isolated workspace.\"\n- Switch to skills\u002Fcollaboration\u002Fusing-git-worktrees\n- Follow that skill's process for directory selection, safety verification, and setup\n- Return here when worktree ready\n\n### Phase 5: Planning Handoff\nAsk: \"Ready to create the implementation plan?\"\n\nWhen your human partner confirms (any affirmative response):\n- Announce: \"I'm using the Writing Plans skill to create the implementation plan.\"\n- Switch to skills\u002Fcollaboration\u002Fwriting-plans skill\n- Create detailed plan in the worktree\n\n## When to Revisit Earlier Phases\n\n**You can and should go backward when:**\n- Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it\n- Validation shows fundamental gap in requirements → Return to Phase 1\n- Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives\n- Something doesn't make sense → Go back and clarify\n\n**Don't force forward linearly** when going backward would give better results.\n\n## Related Skills\n\n**During exploration:**\n- When approaches have genuine trade-offs: skills\u002Farchitecture\u002Fpreserving-productive-tensions\n\n**Before proposing changes to existing code:**\n- Understand why it exists: skills\u002Fresearch\u002Ftracing-knowledge-lineages\n\n## Remember\n- One question per message during Phase 1\n- Apply YAGNI ruthlessly\n- Explore 2-3 alternatives before settling\n- Present incrementally, validate as you go\n- Go backward when needed - flexibility > rigid progression\n- Announce skill usage at start\n","# Brainstorming Ideas Into Designs\n\n## Overview\n\nTransform rough ideas into fully-formed designs through structured questioning and alternative exploration.\n\n**Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation.\n\n**Announce at start:** \"I'm using the Brainstorming skill to refine your idea into a design.\"\n\n## The Process\n\n### Phase 1: Understanding\n- Check current project state in working directory\n- Ask ONE question at a time to refine the idea\n- Prefer multiple choice when possible\n- Gather: Purpose, constraints, success criteria\n\n### Phase 2: Exploration\n- Propose 2-3 different approaches\n- For each: Core architecture, trade-offs, complexity assessment\n- Ask your human partner which approach resonates\n\n### Phase 3: Design Presentation\n- Present in 200-300 word sections\n- Cover: Architecture, components, data flow, error handling, testing\n- Ask after each section: \"Does this look right so far?\"\n\n### Phase 4: Worktree Setup (for implementation)\nWhen design is approved and implementation will follow:\n- Announce: \"I'm using the Using Git Worktrees skill to set up an isolated workspace.\"\n- Switch to skills\u002Fcollaboration\u002Fusing-git-worktrees\n- Follow that skill's process for directory selection, safety verification, and setup\n- Return here when worktree ready\n\n### Phase 5: Planning Handoff\nAsk: \"Ready to create the implementation plan?\"\n\nWhen your human partner confirms (any affirmative response):\n- Announce: \"I'm using the Writing Plans skill to create the implementation plan.\"\n- Switch to skills\u002Fcollaboration\u002Fwriting-plans skill\n- Create detailed plan in the worktree\n\n## When to Revisit Earlier Phases\n\n**You can and should go backward when:**\n- Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it\n- Validation shows fundamental gap in requirements → Return to Phase 1\n- Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives\n- Something doesn't make sense → Go back and clarify\n\n**Don't force forward linearly** when going backward would give better results.\n\n## Related Skills\n\n**During exploration:**\n- When approaches have genuine trade-offs: skills\u002Farchitecture\u002Fpreserving-productive-tensions\n\n**Before proposing changes to existing code:**\n- Understand why it exists: skills\u002Fresearch\u002Ftracing-knowledge-lineages\n\n## Remember\n- One question per message during Phase 1\n- Apply YAGNI ruthlessly\n- Explore 2-3 alternatives before settling\n- Present incrementally, validate as you go\n- Go backward when needed - flexibility > rigid progression\n- Announce skill usage at start\n",{"name":5,"version":23,"description":7,"when_to_use":24},"2.2.0","when partner describes any feature or project idea, before writing code or implementation plans","main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Fbrainstorming-ideas-into-designs",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add RudyCity\u002Fsuperagent --skill \"Brainstorming Ideas Into Designs\"",{"tool":38,"command":39},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill \"Brainstorming Ideas Into Designs\"",{"tool":41,"command":42},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill \"Brainstorming Ideas Into Designs\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbrainstorming-ideas-into-designs\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]