Marcus Andrey Study
Ler em português Library

AI for UX · Step 1 · 6 min read

Claude Design

A beginner's guide to Anthropic's Claude Design in late 2026: what it makes, how to set up your design system, what changed when it moved into every Claude conversation, how it compares with the Figma agent and Claude Code, and what to check first.

Claude Design turns a conversation into a design. You describe a screen, a prototype, a slide deck or a one-pager, and Claude builds it, using your design system if you've set one up. This note explains what it can make, how it fits with the tools you already use, and the settings to check before you use it on real work.

What you'll be able to do after reading:

  • Explain what Claude Design makes and where you find it now
  • Set up a design system so the output looks like your product, not a generic template
  • Choose between Claude Design, the Figma agent and Claude Code for a given task
  • Know the data and admin settings to ask about

Status as of November 2026. Check the product page before you rely on a detail.


1. What it is, and how it got here

  1. Apr17 Apr 2026

    Launched as an Anthropic Labs research preview, for paid plans.

  2. Sep16 Sep 2026

    Moves into every Claude conversation, Artifacts and Claude Code.

  3. Oct15 Oct 2026

    On by default for Enterprise organisations (not HIPAA).

  4. Dec14 Dec 2026

    The standalone claude.ai/design closes and becomes read-only.

Claude Design in four dates. Included on every plan, including Free. Diagram: Marcus Andrey, CC BY 4.0.

2. What it can make

Output Example request Good for
Screens and flows "A three-step onboarding for a budgeting app, mobile, with an error state on step 2" Exploring directions quickly
Interactive prototypes "Make the onboarding clickable, with real form validation" Early tests of a flow
Slides "Turn this research summary into an 8-slide readout" Stakeholder presentations
One-pagers "A one-page summary of the redesign: problem, change, results" Executive updates

Exports: PDF, PowerPoint, HTML and Canva. Handoff: to Claude Code for implementation, and through connectors to Adobe, Canva, Gamma, Lovable, Miro, Replit, Vercel and Wix.


3. Design systems: make it look like your product

Without a design system, Claude Design produces a pleasant but generic look. With one, it uses your colours, type, spacing and components.

You can build a design system from:

  • a GitHub repository or a local code base (the most accurate, because it's what ships),
  • design files,
  • or uploaded assets and guidelines.

In organisations, an admin can approve one standard system and lock it, so everyone starts from the same rules; the organisation's Owners can set it as the default. On Enterprise plans, design systems are off until enabled.

From Claude Code, the /design-sync command uploads a repository's React design system to Claude Design, so the two stay aligned.


4. Inside Claude Code: the /design command

Since August 2026, Claude Code has a /design command (a research preview on paid plans). You give a brief; it produces editable artboards with options; you pick one; Claude then implements it in the code base. Artboards can be exported as PNG or PDF (commands reference).

One limit matters in companies: /design needs Claude's artifacts, so it doesn't work when Claude is used through cloud platforms such as Amazon Bedrock, Google Vertex or Microsoft Foundry. Ask how your organisation provides Claude before you plan around it.


5. Claude Design, Figma agent or Claude Code?

Figma fileFigma agent

Edit or extend designs inside the team's Figma files.

Source of truth: the design file
ConversationClaude Design

A quick concept, prototype, deck or one-pager from words.

Source of truth: still to decide
Code baseClaude Code

A prototype with real coded components, checked in a browser.

Source of truth: the code
Which tool? Choose by where the source of truth lives and who will review the result. Diagram: Marcus Andrey, CC BY 4.0.

Choose by where the source of truth lives (Figma file or code base) and who will review the output. The tools overlap more every month; the question stays the same.


6. Data and admin settings

  • On by default for Enterprise: since 15 October 2026, Claude Design is enabled for Enterprise organisations, except those set up for health data (HIPAA). Admins manage it under Organization settings → Artifacts. Your colleagues may already be using it.
  • Ask before you paste. Which kinds of data is your organisation's Claude plan approved for? Customer data, research recordings and unreleased plans usually need explicit approval. See AI governance and data protection.
  • Freelance or personal plan: read the plan's data terms, and agree with clients what you may upload.

7. Using it well

  1. Set up the design system first. It's the difference between "nice" and "ours".
  2. Brief like you'd brief a person. User, task, constraints, states, tone. See Prompt patterns for designers.
  3. Ask for options, then direct. "Three directions" → pick one → "make the header calmer, keep the cards".
  4. Check everything that looks like a fact. Numbers, quotes and labels in slides and one-pagers are drafts until you verify them.
  5. Decide where the result goes next. Back into Figma, into code, or into a deck. Don't let a one-off prototype become the source of truth by accident.

Common mistakes:

  • Presenting generated numbers or quotes as real data.
  • Skipping the design system and then spending hours restyling.
  • Treating a polished prototype as validated, before any user has seen it.

8. Try it (no code needed)

  1. Write a short brief for a screen you know well (user, task, three states).
  2. Ask Claude Design for two directions, first without a design system, then with one (or with a few screenshots of your product as guidance).
  3. Compare: what changed? What would you still fix?
  4. Turn the better direction into a one-pager explaining the design to a stakeholder, and check every claim in it.

Reflection questions: Which of your deliverables are "first drafts that need speed" and which are "decisions that need care"? Who in your team would review a Claude Design output before it's shared?


9. If you lead a team

  • Clarify with IT: is it enabled, under which data terms, and for which data classes?
  • Ask the design system owners to set up, approve and lock one design system.
  • Pilot it on one real deliverable (a stakeholder one-pager and a prototype from the same spec) and compare with the Figma agent.
  • Add it to the team's list of approved tools, with what it's for and what it isn't.

Checklist

Learn more

Books, courses and videos to go deeper

Figma AI · AI tools landscape for designers · Generating design with Claude Code · Prompt patterns for designers · Design specs for AI · Design tokens · Context files

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close