brainstorming
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
The Process
Understanding the idea:
- Check out the current project state first (files, docs, recent commits)
- Ask questions one at a time to refine the idea
- Prefer multiple choice questions when possible, but open-ended is fine too
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
- Propose 2-3 different approaches with trade-offs
More from garbray/claude-config
uxui-designer
Excellent UX/UI Designer and critical thinker who translates product owner outputs into clear, elegant user experiences. Creates minimalist, high-quality interfaces inspired by Tesla and Apple. Produces precise ASCII UI layouts, component structures, and viewport variations (mobile, tablet, desktop). Designs micro-interactions, transitions, feedback states, loading patterns, and error messaging. Asks thoughtful design questions about intent, constraints, and edge cases. Welcomes feedback and iterates quickly. Use when designing user interfaces, creating wireframes, defining interaction patterns, building component systems, or refining designs.
41tech-architect-delivery
Technical Architect & Delivery Strategist who synthesizes product requirements and UI/UX designs into clear, actionable Technical Design Documents (TDD). Translates business flows into concrete system architecture and implementation plans. Defines end-to-end implementation paths with well-scoped phases and clear responsibility assignments. Specifies frontend-backend contracts (APIs, events, payloads, states, error models). Documents data models, integrations, security, and non-functional requirements. Explains happy paths and failure scenarios including edge cases, retries, fallbacks, and recovery. Enables confident implementation and smooth collaboration. Use when creating technical specifications, designing system architecture, planning implementation, defining APIs, or translating design into engineering work.
15ascii-design-reviewer
Review Phase 1 ASCII UI designs from a product owner perspective. Analyze user journeys, identify potential issues, ask clarifying questions about requirements and user flows, create Mermaid diagrams (flowcharts, sequence diagrams, state charts), provide detailed system behavior documentation, and document error handling strategies. Use when reviewing ASCII mockups to validate design against actual user needs, understand system workflows, and ensure completeness before moving to implementation.
12frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
10skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
10po-journey-architect
Product Owner & App Journey Architect role skill. Use when Claude needs to act as a seasoned product owner who translates business goals into clear, actionable product requirements; identifies gaps, ambiguities, and hidden assumptions; designs and documents user journeys, system flows, and state diagrams using Mermaid; reviews high-level designs for completeness and feasibility; uncovers edge cases, failure scenarios, and error-handling strategies; and validates specifications are build-ready. Triggered by requests to review product specs, design user journeys, create system flows, challenge requirements clarity, identify design gaps, or architect application flows.
10