claude-design--end-to-end-workflowslisted

# Claude Design — End-to-End Workflows ## When to activate - Starting a new project and need a repeatable design-to-production process rather than ad hoc prompting - A team member is new to Claude Design and needs a structured approach to avoid wasted sessions - Switching between design contexts — startup speed, product-team consistency, design-led exploration, or marketing launch - Existing Claude Design sessions are consuming excessive tokens without converging on a direction ## When NOT to use - One-off throwaway prototypes with no downstream implementation — skip the workflow, prompt directly - Projects where Figma is the source of truth and the team must approve Figma files before any development starts — use Figma's AI tools and import to Claude Code manually - When pixel-perfect client approval mockups are required before any engineering begins — Claude Design is not a Figma replacement for that gate - When a design direction is already locked in Claude Code — do not return to Claude Design; iterate in code ## Instructions Four workflows covering the four most common usage contexts. Each is designed to minimize token waste and time-to-production. --- ### Workflow 1: Rapid Validation (Startup / MVP) Goal: validated UI direction from spec to working code in under six hours, same day. **Phase 1 — Concept (30 minutes, one session)** Open a fresh Claude Design session. Provide: - Target audience (one sentence) - Core features to show (3–5 maximum) - Brand constra