โ† Back to Resources

Prompt Database

๐ŸŽจ Claude Design โ€” Quick Start Guide + 5 Prompts

๐ŸŽจ Claude Design lets you collaborate with Claude to create polished visual work through simple conversation โ€” designs, interactive prototypes, slide decks, one-pagers, and more. No design background needed.

๐Ÿ”— Get started โ†’ claude.ai/design


๐Ÿ“Œ At a Glance

๐Ÿข Maker Anthropic
๐Ÿ’ณ Availability Pro, Max, Team, Enterprise subscribers
๐ŸŒ Access claude.ai/design
๐Ÿงฉ Interface Chat on the left ยท Canvas on the right
๐Ÿ“ค Exports PDF ยท PPTX ยท ZIP ยท HTML ยท Canva ยท Claude Code

๐Ÿš€ The 3-Step Setup

1๏ธโƒฃ Set Up Your Design System

When you first open Claude Design, Claude builds a design system for your brand by reading your existing files and assets. Your colours, typography, and components are then applied to every project automatically.

๐Ÿ’ก Already have a design system?

Upload it directly inside Claude Design and it will be applied to all your projects automatically.

๐Ÿ†• Don't have one yet?

Use Prompt 1 below to generate a complete design system from scratch.

2๏ธโƒฃ Create a New Project

Every project automatically uses your brand's colours, fonts, and components โ€” no reconfiguration needed.

You can add extra context by uploading:

3๏ธโƒฃ Start Building

Describe what you want โ†’ Claude builds it โ†’ you refine from there.


โœจ 3 Ways to Get Ahead

# Use Case What It Does
1 Build full app design flows Design entire apps from onboarding to dashboards โ€” all brand-consistent, in one conversation
2 Turn files into design assets Upload any doc/sheet/deck โ†’ get a polished PDF, slide deck, or landing page
3 Export to Claude Code ๐Ÿคซ Hit Export โ†’ Handoff to Claude Code to go from design to production in one workflow
๐Ÿคซ Secret hack: The Handoff to Claude Code export packages everything up and sends it straight to Claude Code for development. Not many people are talking about this one yet.

๐Ÿ’ก Tips for Best Results


๐ŸŽ The 5 Prompts (Upgraded)

These are enhanced versions of the original prompts โ€” more specific, more structured, and designed to give Claude Design the context it needs to produce production-grade output on the first try.

๐ŸŽจ Prompt 1 โ€” Generate a Complete Design System

๐Ÿ“‹ Click to expand prompt
You are a senior brand designer. I need you to create a complete, production-ready design system for my brand that I can upload into future Claude Design projects as the source of truth.

Brand Context

  • Business name: [YOUR BUSINESS NAME]
  • Industry: [YOUR INDUSTRY]
  • Target audience: [WHO THEY ARE + what they care about]
  • Brand personality (pick 3โ€“5 adjectives): [e.g. modern, minimal, warm, trustworthy, playful]
  • Competitors I admire visually: [2โ€“3 brands + what I like about each]
  • Competitors I want to look nothing like: [1โ€“2 brands]
  • Preferred colours (or leave blank): [HEX codes or description]
  • Must-have accessibility standard: WCAG 2.2 AA minimum

Deliver a structured design system with:

  1. Colour palette โ€” primary, secondary, accent, neutrals (9-step scale), and semantic colours (success, warning, error, info). Include HEX, RGB, and usage guidance for each.
  2. Typography scale โ€” font pairings (heading + body), a modular type scale (H1โ€“H6, body, small, caption), weights, and line heights.
  3. Spacing & layout grid โ€” 4px or 8px base unit, spacing scale, container widths, and responsive breakpoints.
  4. Component styles โ€” buttons (primary, secondary, ghost, destructive + all states), cards, inputs, badges, modals, and navigation. Include hover, focus, active, and disabled states.
  5. Iconography & illustration direction โ€” style (line/filled/duotone), stroke width, and a mood board description.
  6. Motion principles โ€” easing curves and duration tokens for micro-interactions.
  7. Do's and don'ts โ€” 5 of each, with visual examples where possible.

Format the output as a structured living style guide I can reference and upload into future projects. Flag any accessibility risks you spot in my colour choices.

```</code></pre></div></details>

What's new: senior-designer framing, competitor context (both positive and negative), accessibility standard baked in, full component states, motion tokens, and a requirement to flag risks.


๐Ÿ“ฑ Prompt 2 โ€” Design a Full App UI Flow

๐Ÿ“‹ Click to expand prompt
Using my uploaded design system, design the complete UI flow for my app. Treat this like you're shipping v1 โ€” every screen should be pixel-ready, not a rough sketch.

App Overview

  • App name: [APP NAME]
  • One-sentence description: [WHAT IT DOES]
  • Core user goal: [THE JOB THE USER IS HIRING THIS APP TO DO]
  • Primary user persona: [WHO THEY ARE + context of use]
  • Platform: [Web / iOS / Android / All]
  • Emotional tone the app should evoke: [e.g. calm &amp; focused / energetic &amp; fun / premium &amp; serious]

Screens to Design (in order)

  1. Splash / Onboarding โ€” 3-screen walkthrough that sells the core value prop before asking for anything.
  2. Sign up &amp; login โ€” email + social, with password-less option and clear error states.
  3. Main dashboard / Home โ€” the user&#x27;s first &quot;wow&quot; moment. Include empty state (first-time user) and populated state.
  4. [KEY FEATURE SCREEN] โ€” [e.g. booking flow / product listing / analytics view]. Include loading, success, and error states.
  5. Profile &amp; settings โ€” account, notifications, privacy, billing, and sign out.

For Each Screen Deliver

  • Layout structure with clear visual hierarchy
  • Every UI component used, tied back to my design system
  • Realistic copy (no Lorem Ipsum โ€” write actual microcopy)
  • Accessibility notes (contrast, tap targets, screen reader labels)
  • State variations: default, hover, active, empty, loading, error
  • Micro-interactions worth calling out

Output Format

Show screens in user-flow order with annotations, then end with a &quot;design decisions&quot; summary explaining why you made the key calls you did.

```</code></pre></div></details>

What's new: ship-ready framing, emotional tone, user persona, realistic copy requirement, accessibility notes, full state coverage, and a design-decisions recap.


๐ŸŽฅ Prompt 3 โ€” Animated Explainer Video

๐Ÿ“‹ Click to expand prompt
Create a 60-second animated explainer for [YOUR PRODUCT/CONCEPT] designed to convert cold viewers into interested leads.

Context

  • Product/concept: [WHAT IT IS]
  • Audience: [WHO IT&#x27;S FOR]
  • Single core message the viewer must walk away with: [ONE SENTENCE]
  • Call to action: [e.g. &quot;Start free trial&quot; / &quot;Book a demo&quot;]
  • Brand tone: [adjectives]

Structure (60 seconds, beat-by-beat)

  • 0:00โ€“0:03 โ€” Hook. Pattern interrupt or sharp question that stops the scroll.
  • 0:03โ€“0:15 โ€” Problem. Agitate the pain the viewer already feels.
  • 0:15โ€“0:40 โ€” Solution. Visualise how the product works using motion graphics and simple metaphors.
  • 0:40โ€“0:52 โ€” Proof. A stat, customer logo bar, or testimonial beat.
  • 0:52โ€“1:00 โ€” CTA. Clear, single action with visual emphasis.

Deliver

  1. Storyboard (frame-by-frame with timing)
  2. Voiceover script with pacing notes
  3. On-screen text and kinetic typography callouts
  4. Suggested music mood and sound design cues
  5. Motion principles (easing, duration) consistent with my design system

Keep it visual-first โ€” if a beat works without the voiceover, it&#x27;s strong.

```</code></pre></div></details>

What's new: beat-by-beat structure with timing, conversion framing, voiceover + on-screen text separation, sound design cues, and a "works without VO" quality bar.


๐Ÿ’ป Prompt 4 โ€” High-Converting Landing Page

๐Ÿ“‹ Click to expand prompt
Design a high-converting landing page for [PRODUCT NAME]. The single job of this page is to move visitors from cold traffic to [PRIMARY CTA โ€” e.g. free trial signup, demo booking].

Context

  • Product: [ONE SENTENCE]
  • Primary audience: [WHO THEY ARE + what they care about]
  • Stage of awareness: [unaware / problem-aware / solution-aware / product-aware]
  • Competitors they&#x27;re comparing us to: [2โ€“3]
  • Brand feel: [adjectives]
  • Primary CTA: [e.g. &quot;Start free trial&quot;]
  • Secondary CTA: [e.g. &quot;Watch 2-min demo&quot;]

Sections to Design

  1. Hero โ€” headline (outcome-focused, not feature-focused), subheading, primary CTA, and a visual or product screenshot.
  2. Problem/agitation โ€” 2โ€“3 pain points the visitor is nodding along to.
  3. Solution / how it works โ€” 3-step visual walkthrough.
  4. Features โ€” 4โ€“6 benefit-led feature cards (benefit in the headline, feature in the subtext).
  5. Social proof โ€” customer logos, testimonials with names and roles, and at least one metric (e.g. &quot;2.4x faster onboarding&quot;).
  6. Pricing โ€” 3 tiers with one marked as most popular; include annual/monthly toggle.
  7. FAQ โ€” 5โ€“7 questions that handle the top objections.
  8. Final CTA โ€” restate the promise, single big button.

Design Requirements

  • Mobile-first responsive design
  • Above-the-fold must communicate value in under 5 seconds
  • Clear visual hierarchy โ€” one dominant CTA per section
  • Accessibility: WCAG 2.2 AA, tap targets โ‰ฅ44px, contrast ratios called out
  • Write real copy โ€” no placeholders

End with a short conversion-rationale note explaining the key decisions (headline choice, CTA placement, pricing anchor).

```</code></pre></div></details>

What's new: awareness stage, primary + secondary CTAs, benefit-led feature cards, real metrics in social proof, pricing structure specifics, and a conversion-rationale recap.


๐Ÿ“Š Prompt 5 โ€” Investor-Ready Pitch Deck

๐Ÿ“‹ Click to expand prompt
Build an investor-ready pitch deck for my startup [STARTUP NAME]. Target a [PRE-SEED / SEED / SERIES A] round of [$AMOUNT]. The deck should be visual-first, scannable in under 3 minutes, and land the "why now, why us, why this" story.

Context

  • Startup: [ONE-SENTENCE DESCRIPTION]
  • Stage: [IDEA / BUILDING / LAUNCHED / REVENUE]
  • Monthly revenue or key traction metric: [NUMBER or &quot;pre-revenue&quot;]
  • What makes us uniquely positioned to win: [THE UNFAIR ADVANTAGE]
  • Brand colours: [HEX CODES]

Slide Sequence (12 slides max)

  1. Title โ€” company name, one-line positioning, founder names, date.
  2. Problem โ€” a specific, painful, universal problem. Use a story or stat, not bullets.
  3. Solution โ€” what we built, in one visual.
  4. Why now โ€” the shift in the world that makes this inevitable.
  5. Product demo โ€” 2โ€“3 screenshots with annotations showing the &quot;aha&quot; moment.
  6. Market size โ€” TAM / SAM / SOM with a credible bottoms-up calculation.
  7. Business model โ€” how we make money in one diagram.
  8. Traction โ€” the strongest metric we have, visualised.
  9. Competition โ€” 2ร—2 matrix or feature grid showing our wedge.
  10. Team โ€” founders + key hires with the one sentence that makes each one credible.
  11. The ask โ€” how much we&#x27;re raising, what we&#x27;ll do with it, milestones it unlocks.
  12. Contact / appendix โ€” email, calendar link, and any backup data investors typically ask for.

Design Principles

  • One idea per slide. If a slide has two ideas, split it.
  • Max 10 words of body copy per slide โ€” the rest is visual.
  • Consistent layout, typography, and colour usage across every slide.
  • Every chart must have a one-line takeaway callout.
  • Speaker notes underneath each slide (2โ€“3 sentences of what the founder actually says).

End with a page on what to cut if we need a 10-slide version.

```</code></pre></div></details>

What's new: fundraising stage and amount, "why now" slide, bottoms-up market sizing, 2ร—2 competition matrix, speaker notes, and a cut-down version instruction.


๐Ÿ” Export Options Cheat Sheet

Export Best For
๐ŸŸฃ Handoff to Claude Code Shipping design โ†’ production in one workflow
๐Ÿ—œ๏ธ ZIP download Archiving or handing off to another dev
๐Ÿ“„ PDF Client review or slide-printing
๐ŸŽž๏ธ PPTX Traditional pitch contexts
๐ŸŽจ Canva Collaborative editing with a non-technical team
๐ŸŒ HTML Quick standalone preview or prototype hosting

๐Ÿง  Remember: Start with your design system first. Every prompt in this doc assumes Claude Design already knows your brand. Skip that step and your output will look generic.