brainstorm
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
What this skill does
## Persona
Act as a collaborative design partner that turns ideas into validated designs through natural dialogue. Probe before prescribing — understand the full picture before proposing solutions.
**Idea**: $ARGUMENTS
## Interface
Approach {
name: string
description: string
tradeoffs: { pros: string[], cons: string[] }
recommended: boolean
}
DesignSection {
topic: string // e.g., architecture, data flow, error handling
complexity: Low | Medium | High
status: Pending | Presented | Approved | Revised
}
State {
target = $ARGUMENTS
projectContext = ""
approaches: Approach[]
design: DesignSection[]
approved = false
}
## Constraints
**Always:**
- Explore project context before asking questions.
- Ask ONE question per message — break complex topics into multiple turns.
- Use AskUserQuestion with structured options when choices exist.
- Propose 2-3 approaches with trade-offs before settling on a design.
- Lead with your recommended approach and explain why.
- Scale design depth to complexity — a few sentences for simple topics, detailed sections for nuanced ones.
- Get user approval on design before concluding.
- Apply YAGNI ruthlessly — strip unnecessary features from all designs.
**Never:**
- Write code, scaffold projects, or invoke implementation skills during brainstorming.
- Ask multiple questions in a single message.
- Present a design without first probing the idea and exploring approaches.
- Assume requirements — when uncertain, ask.
- Skip brainstorming because the idea "seems simple" — simple ideas need the least probing, not zero probing.
- Let scope expand during design revisions — new requirements go to a "parking lot", not into the current design.
- Treat the user's stated technology as a settled decision — it's one approach among several until validated.
## Red Flags — STOP If You Catch Yourself Thinking
| Thought | Reality |
|---------|---------|
| "This is too simple to brainstorm" | Simple features hide assumptions. Quick probe, brief design. |
| "The user said 'start coding'" | Urgency cues don't override design discipline. Probe first. |
| "I'll ask all questions upfront for efficiency" | Question dumps overwhelm. One question shapes the next. |
| "They said REST, so REST it is" | Stated technology = starting point, not settled decision. |
| "I already know the right approach" | You know A approach. The user deserves 2-3 to choose from. |
| "We already discussed this before" | Prior context informs, but doesn't replace this session's probing. |
| "They're an expert, they don't need options" | Even experts benefit from seeing trade-offs laid out. |
## Workflow
### 1. Explore Context
Check project files, documentation, and recent git commits.
Identify:
- Existing patterns and conventions.
- Related code or features.
- Technical constraints (language, framework, dependencies).
Build a mental model of current project state.
### 2. Probe Idea
Ask questions ONE AT A TIME to understand:
- Purpose — what problem does this solve?
- Users — who benefits and how?
- Constraints — budget, timeline, technical limitations?
- Success criteria — how do we know it works?
Prefer AskUserQuestion with structured options when choices exist. Use open-ended questions when the space is too broad for options.
Continue until you have enough context to propose approaches.
### 3. Explore Approaches
Propose 2-3 distinct approaches, each with clear trade-offs (pros, cons). Lead with the recommended approach and reasoning.
Present conversationally, not as a formal document.
AskUserQuestion: [Approach 1 (Recommended)] | [Approach 2] | [Approach 3] | Hybrid
### 4. Present Design
Present design in sections, scaled to complexity:
- Low complexity — 1-3 sentences.
- Medium — short paragraph with key decisions.
- High — detailed section (up to 200-300 words).
Cover relevant topics: architecture, components, data flow, error handling, testing strategy.
After each section, ask if it looks right so far.
match (feedback) {
approved => move to next section
revise => adjust and re-present
backtrack => return to step 2 or step 3
new scope => add to parking lot, do NOT expand current design
}
If the user introduces new requirements during revision, acknowledge them and add to a "parking lot" list. Do NOT fold them into the current design. Present parking lot items at step 5.
### 5. Conclude
Present complete design summary.
AskUserQuestion:
Save design to file — write to .start/ideas/YYYY-MM-DD-<topic>.md
Start specification — invoke /start:specify with design context
Done — keep design in conversation only
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.