brainstorming

# Brainstorming

## Purpose

This skill promotes collaborative brainstorming and creative exploration **before** jumping into implementation. It encourages Claude to think through options, discuss possibilities, and co-create solutions with users rather than immediately writing code.

## When to Use

Use this skill BEFORE starting implementation work on:

- **New features** - Exploring different approaches and design patterns
- **New components** - Discussing architecture, API design, and integration
- **Creative work** - Brainstorming solutions, evaluating alternatives, greenfield exploration
- **Functionality additions** - Considering multiple implementation paths

## Philosophy

Great software emerges from thoughtful exploration, not rushed implementation. Brainstorming means:

- 🤝 **Collaboration** - Working with the user to explore ideas together
- 💡 **Ideation** - Generating multiple options before committing to one
- 🎯 **Trade-offs** - Discussing pros/cons of different approaches
- 🗺️ **Context** - Understanding the bigger picture and constraints
- ✨ **Creativity** - Thinking beyond the obvious first solution

## Brainstorming Approaches

### 1. EnterPlanMode (For deep exploration)

Use when you need to thoroughly explore the codebase and design options:

```markdown
Let me explore the codebase and brainstorm some implementation approaches.
```

**In plan mode:**
- Discover existing patterns and conventions
- Identify multiple possible approaches
- Sketch out different architectural options
- Present trade-offs for user consideration
- Collaborate on the best path forward

### 2. AskUserQuestion (For collaborative ideation)

Use to brainstorm options and gather user preferences:

```markdown
Let me brainstorm some options with you.
```

**Discuss:**
- Different architectural approaches
- Technology/library alternatives and trade-offs
- UI/UX patterns and user experience considerations
- Performance vs simplicity trade-offs
- Integration strategies
- Futur