brainstorming
Collaborative Brainstorming for Design
Also available from: Cycleaddict,Cygnusfear,obra,davila7,DMJGilbert,DYAI2025,ArieGoldkin,CodingCossack
This skill helps AI assistants turn vague ideas into concrete designs through structured dialogue, ensuring requirements are clear before implementation begins.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "brainstorming". I want to add a user notification system to my app
Expected outcome:
Great! Let me understand what you are building. First question: What is the primary purpose of these notifications - are they for user activity (like comments, likes), system alerts (maintenance, errors), or something else?
Using "brainstorming". What if I want push notifications too?
Expected outcome:
Good point. I have two approaches to consider:
1. **Single channel first**: Start with in-app notifications, add push later when you have more resources.
2. **Multi-channel from start**: Use a service like OneSignal or Firebase that handles both.
My recommendation is approach 1 if you are early stage - it keeps complexity down. Which direction interests you more?
Security Audit
SafeStatic analysis flagged external commands and cryptographic algorithms, but manual review confirms these are false positives. The skill contains only documentation text - no executable code. Backticks at line 38 are markdown formatting, not shell execution. No cryptographic code exists in the skill.
High Risk Issues (1)
Medium Risk Issues (1)
Quality Score
What You Can Build
New Feature Planning
When a user wants to add a new feature, guide them through understanding requirements, constraints, and success criteria before any implementation begins.
Component Design Sessions
Help design new UI components or backend services by asking targeted questions, presenting options, and iterating on the design through dialogue.
Architecture Exploration
Explore different architectural approaches for a system, presenting trade-offs and recommendations while validating understanding at each step.
Try These Prompts
I want to build something new. Can you help me brainstorm the design? The idea is: [describe your idea]. What questions do you have to understand what I am building?
We are designing [feature/system]. Based on what we discussed, what approaches would you recommend? Please present 2-3 options with trade-offs.
Here is my proposed design for [section]: [design content]. Does this look right? What should I clarify or change?
We have validated the design. Can you write this up as a design document at docs/plans/[topic]-design.md?
Best Practices
- Ask one question per message to avoid overwhelming the user
- Prefer multiple choice questions when possible for faster responses
- Present your recommendation first, then explain reasoning
- Validate understanding incrementally by presenting design sections
Avoid
- Asking multiple questions in a single message
- Jumping to implementation without validating the design first
- Presenting only one option without exploring alternatives
- Ignoring user feedback and continuing with the original plan