Claude Design gives you a decent first draft in one prompt, then a mediocre second and third if you keep typing at it. The fix is rarely a better prompt. It is knowing which of the tool's controls to reach for at each stage. A video from RoboNuggets titled "25 Tricks to Level Up Claude Design in 13 Mins" prompted this post. I haven't built it from the video. These steps come from Anthropic's own documentation.
Step 1: Set up your design system before the first project
Anthropic's announcement says Claude analyzes your codebase and design files during onboarding and builds a design system from them. After that, every project uses your colors, typography and components automatically.
So do this first, and do it properly. Link the GitHub repo, or the design files, that hold the real tokens. Don't link a half-finished prototype. If the source is messy, the system is messy, and every project inherits it.
Claude Code users also get a /design-sync command, which the help center lists as one way to bring a design system in.
Step 2: Start with a short brief that names the job
Write three things: who the screen is for, the one task it must support, and the constraints. For example: "A settings page for a billing app. The user needs to change their plan in under three clicks. Desktop first, dense but calm."
Leave out colors and fonts. Your design system already holds them, and repeating them in the prompt only invites Claude to override them.
Step 3: Feed it real material, not descriptions
Claude Design accepts uploaded files (DOCX, PPTX, XLSX and images), codebase references, and elements captured from a website. Use them.
If you want a layout like one you already like, capture it instead of describing it. If you have real copy in a document, upload the document. Real content exposes layout problems that "Lorem ipsum" hides, like a long plan name wrapping onto three lines.
Step 4: Use chat only for big moves
Chat is for structure. The help center's own examples are "Make the color scheme darker and more minimal" and "Add a settings panel on the right side."
Once the structure is right, stop. Each broad request gives Claude permission to change things you were happy with. Think of chat as a wide brush: good for the first pass, wrong for details.
Step 5: Switch to inline comments for fixes
Click the element on the canvas and comment on that element alone. "Make this button padding larger." "Change this to a dropdown instead of radio buttons."
A comment is anchored to one thing, so the rest of the screen stays put. That is the whole reason to prefer it over chat once you are past the rough stage.
Step 6: Edit text and spacing by hand
Some changes are faster to do than to explain. Claude Design lets you edit text directly, and the announcement describes adjustment knobs for live tweaking of spacing, color and layout. The help center also mentions layout controls to drag, resize and align elements.
If you catch yourself writing a sentence to move something 8 pixels, grab the control instead.
Step 7: Ask for a change across the whole design, on purpose
Sometimes you do want a global edit: tighter spacing everywhere, or sentence case on every button. The announcement lists applying changes across the full design as a refinement method.
Do it as its own request, with one rule per request. "Use sentence case for all button labels" is clean. "Make it feel more modern and fix the buttons" is not.
Step 8: Save a version before you explore
Before trying something risky, say it in plain words. The help center suggests: "Save what we have and try a completely different approach."
That keeps the version you like and gives you a branch to compare against. Exploring without a saved baseline is how a good draft gets lost with no record of what changed.
Step 9: Review before you share
Designs are private by default. When you click Share, you choose whether colleagues can view, comment or edit.
Give reviewers comment access first. Edit access invites someone to fix your spacing in a way you'll have to undo.
Step 10: Pick the export that matches the next person
The export options depend on who picks it up next. Both sources list several formats, so match them to the reader.
| Who is next | Export |
|---|---|
| A client or stakeholder | PDF or an internal organization URL |
| A presentation audience | PPTX |
| A marketing team | Canva |
| Anyone who needs to click through it | Standalone HTML |
| An engineer | Handoff bundle for Claude Code |
According to Anthropic, the handoff bundle can be passed to Claude Code with a single instruction. That is the route I'd choose for anything headed to production, because it carries the design system with it.
One more check for this stage: open the standalone HTML export in a real browser and resize the window. A canvas preview can look fine while the layout breaks at a narrow width. Five minutes of dragging the window edge will catch most of it before an engineer does.
Step 11: Add icons last, and keep them consistent
Generated screens often come with placeholder icons from mixed styles. Replace them in one pass at the end, once the layout is final. Pick one icon style and use it everywhere.
Thridy icons are free for personal and commercial use. On the free plan a credit to Thridy is needed. On a paid plan (Designer or Studio) no credit is needed.
Quick reference
1. Build the design system from real source files first.
2. Brief the job and the constraints, not colors and fonts.
3. Upload real files and captured pages.
4. Chat for structure, comments for fixes, controls for pixels.
5. Make global changes one rule at a time.
6. Save a version before exploring.
7. Share with comment access, then export for the next reader.
Use chat for the big moves, comments for the small ones, and save a version before you try anything new.
Free 3D icons for this
Every icon on Thridy is free to download and use. A few that fit this piece:
