Setup takes five minutes: open Claude, find Claude Design in the sidebar, optionally grant design system access
Specific prompts beat buzzwords, name fonts, name colors, name counts, and state exclusions so Claude does not guess
Use sliders for nuance, inline comments for element-specific fixes, direct edits for anything numeric or textual
Export to Canva for polish, PDF for delivery, URL for feedback rounds, PPTX only when corporate demands it
My first real test: 15 minutes prompt to production for a 10-slide deck, roughly half that on the second try
I spent the last few hours running Claude Design through real work, not demo scenarios. A pitch deck for a client, a landing page hero, an onboarding flow mockup for a side project. Here is exactly how I used Claude Design, which prompts actually worked, and where I got stuck along the way.
If you want the launch explainer, I wrote that separately. This post is the hands-on workflow guide.
Step 1: Getting Set Up
Access first. Log into claude.ai on a paid plan (Pro, Max, Team, or Enterprise). Claude Design appears in the left sidebar under the main chat. If you do not see it yet, rollout is gradual. Check again in a few hours.
First launch drops me into a welcome screen with three options.
Start from scratch. Fastest way to play. It opens a blank canvas and a prompt box. Type my request, hit enter, Claude builds.
Build from a design system. Where teams get the real value. Claude asks for access to a codebase, a Figma file, or a design tokens file. I pointed it at my raxxo-brand repo. Onboarding took under two minutes. Claude pulled out my lime green (#e3fc02), my Outfit typography, my spacing scale (2/4/6/8/12/16/20/24/32/48/64), and my rounded corner conventions. Then it rendered a test card showing all the tokens applied correctly. No manual configuration required.
Starter template. Common formats like pitch decks, landing pages, mobile app flows, marketing one-pagers. Good if you are not sure what you want and need a prompt scaffold to work against.
My advice: do the design system onboarding once, even if it takes ten minutes. Everything you generate afterwards starts on-brand automatically, and that is worth the up-front cost on day one.
Step 2: Writing Prompts That Work
The thing nobody tells you about AI design tools: how you prompt matters more than the underlying model. Claude Design is powered by Opus 4.7, which is strong, but it still wants specifics.
Prompts that flop in my testing:
"Make me a modern landing page"
"A nice pitch deck for my startup"
"Something minimal and clean"
Prompts that actually work:
"Landing page for a Shopify app that saves store owners 10 hours per week on inventory. Hero with the 10-hour claim, three testimonial logos below, feature grid with 6 items, dark background, warm yellow accent, no stock photos."
"10-slide pitch deck for a B2B SaaS called Glasswing. Cover slide with logo placeholder, problem, solution, market size (40B), product screens, traction (20 percent MoM), team, financials, roadmap, ask. Dark theme, editorial typography, no gradients."
"Mobile app mockup for a daily journaling app. Lock screen widget view, home feed with three sample entries, writing screen with keyboard visible, settings screen. Warm neutral palette, serif typography, plenty of breathing room."
What actually lands: specific numbers, specific counts, visual vocabulary (dark, warm, editorial), and explicit exclusions (no gradients, no stock photos). Claude handles a brief like that directly.
Skip the adjectives. "Modern, clean, minimal" means nothing to the model. "Outfit sans-serif at 14px base, black background, four-column grid" means everything. Treat the prompt like a design brief you would give a freelancer who bills 150€ per hour. Specific beats vibes every time.
Step 3: Iterating With Sliders and Comments
First draft is never right. Revision is where Claude Design earns its price.
Conversation revision works like a regular Claude chat. "Make the hero headline bigger. Swap the accent color to lime green. Remove the second testimonial row." All handled in one reply. Useful for sweeping directional changes.
Inline comments are where I spent most of my time. Click an element, type a note like "this padding is too tight" or "this button should be secondary style." Claude fixes that one element without rewriting the rest of the design. Think of it as giving a designer a feedback round without scheduling a meeting.
Direct edits skip Claude entirely. Change a text value, move a box, tweak a color in the picker. Instant. Use this for anything numeric or textual that I already know the exact answer to.
Sliders are the feature I did not expect to love. When I ask Claude about a specific property, it spins up a custom slider for that property with a live preview. Ask "what if the headline was heavier?" and a font-weight slider appears. Ask about "tighter layout" and a density slider appears. The slider only exists because I asked about it. Then it disappears when the conversation moves on.
My rule after two days of use: sliders for nuance, comments for element-specific fixes, conversation for sweeping direction changes, direct edits for anything I already know the exact answer to. Switching between these four modes is what makes the iteration feel fast instead of clunky.
Step 4: Exporting and Handing Off
Four export options ship today, and picking the right one matters more than the launch materials make it sound.
Send to Canva. The best option if I plan to keep editing. Claude Design runs on Canva's Design Engine, so the export opens as a fully editable Canva file. All layers, text, and components remain editable. Plus I get access to the full 200M-asset Canva library to extend the design further. I use this for about 80 percent of outputs.
PDF. For finished work that does not need more editing. Email, Notion embeds, print-ready. The export preserves typography at vector quality, so nothing pixelates when someone zooms in.
URL. Hosted link to the live prototype. Great for stakeholder review rounds where I want comments on the design itself. No login required for whoever I send the link to.
PPTX. PowerPoint file. I use this only when a client explicitly requests it. Corporate workflows that refuse to die.
One gotcha I hit. PPTX export flattens some of the more advanced layout behavior. Responsive grid bits become static layouts on export. If the final home for the design is PowerPoint, let Claude know up front. It will prefer layouts that translate cleanly across formats instead of assuming a web target.
Bottom Line
My first real test: 15 minutes from prompt to a 10-slide pitch deck I would actually send to a client. Second try, roughly half that time. The speed is real.
But speed is not the whole story. Claude Design is strongest as a drafting tool. Start in Claude, polish in Canva, ship the final version from whichever tool fits the delivery format best. Do not treat the first Claude output as final. Treat it as a smart first pass that skips the blank canvas problem that eats so much of my day.
If you have been on the fence about AI design tools because they all produce generic output, Claude Design's design system integration changes that objection specifically. Once Claude knows my brand, everything it generates stays on-brand. That alone is worth opening Claude tonight if you are on a paid plan.
One tip before you start. Have the design system ready. A Figma file, a tokens.json, or a CSS variable set. Feeding Claude garbage gives me garbage back. Feeding it a clean brand system gives me on-brand output from the first prompt. Worth an hour of prep before the first real session.
A second tip I learned the hard way. Treat Claude Design sessions like a conversation with a new hire who is fast but needs context. Paste the project goal at the top. State the target audience. Name the platform (web, iOS, PowerPoint) so Claude picks a layout that survives the export format. When I skipped that and fired off prompts blind, the first draft was always weaker and I spent longer fixing it than I would have spent writing a proper brief. Three extra sentences of setup saves ten minutes of cleanup.
Last thing. Keep a scratchpad of prompts that worked. My best outputs came from prompts I refined over multiple sessions, not first attempts. Paste them into a notes file with the output thumbnails. Next time a similar design job comes through, start from a proven prompt and tweak from there. Claude Design rewards the same prompt library discipline that makes any LLM workflow faster over time.
Top comments (0)