TL;DR Ask for designs with
/design <brief>, which already creates a Claude Design artifact. Before December 14, move your design systems into Claude with "Move team design systems" and export the.zipof any project you won't move. For new work, drop/design-syncand the Claude Design MCP: both work against the site that's closing.
The standalone Claude Design site, claude.ai/design, closes on December 14, 2026: from that day it's read-only and takes no new projects. Claude Design isn't going away, it's moving into Claude: new designs, design systems and slide decks are created as artifacts. In Claude Code, v2.1.325 already has a foot on each side, and it pays to know which is which before the date.
What points where in v2.1.325
The terminal's command menu spells it out when you type /design:
❯ /design Make a new Design artifact from a brief
/design-sync Push your design system components to claude.ai/design
/design-login Authorize design-system access for /design-sync with your claude.ai account
| What you use today | What it does | What it works against |
|---|---|---|
/design <brief> |
Creates a Design artifact | Claude |
/design-sync |
Pushes your design system to a project | claude.ai/design |
/design-login |
Authorizes the access /design-sync needs |
claude.ai/design |
/design consent and /design revoke |
Grant or remove Claude's access to your Design projects | claude.ai/design |
| The Claude Design MCP | Reads and edits your Design projects | claude.ai/design |
Since v2.1.302, /design-sync and /design-login show the notice: "Standalone Claude Design (claude.ai/design) closes by December 14, 2026. Claude Design now lives in Claude." And since v2.1.317, /design-sync stops before building when your design system has already moved to Claude.
How to keep using it
1. Move your design systems into Claude
On Claude's Artifacts page, the "Claude Design lives here now" banner has a "Move team design systems" button (if you closed the banner, it's in the Claude Design menu). One move takes every design system in your organization, owners kept. Any that can't move show under "Didn't move" with the reason; the ones that do move turn read-only on claude.ai/design. Moving again later picks up new or changed systems and skips the ones you've already edited in Claude.
2. Move or export your projects
Each project moves from the pop-up or the banner at the top of the project itself, and only its owner can move it; the move is rolling out gradually to paid plans. An Owner also gets "Move everything" on the Artifacts page, which takes templates and design systems too. What doesn't travel: your chats with Claude and the comments. And public links stop working at the closing.
To keep a copy of a project: open it, Share, Project HTML (for a slide deck, under "More formats and apps"), keep Project archive selected and click Export. You get a .zip of every file, free and outside your usage.
3. Design with /design and a brief
/design a pricing card for a single plan: name, price, three features and a button
Per the docs, Claude Code draws the design as artboards on a canvas and publishes it as a Claude Design artifact, private until you share it; you open it in a desktop browser, edit any element and it saves on its own. What that editor is like is in the editable canvas tip.
One case to watch: in a test session whose account didn't offer the Design type, /design published a plain page instead of a canvas and said so in its answer ("This account has no Design type to start from"). On Enterprise, whether the Design template is on is an Owner's call, and without it /design doesn't draw designs.
4. Your design system, now an artifact
When it creates a design or a deck, Claude Code lists the design systems you can open and uses the one marked as default. If none is, it asks which one you want. To read one from the terminal, give it the link: it reads it with the Artifact tool, starting from its project/README.md, the brand book, with the tokens apart in project/tokens.json.
If what you had was the design system /design-sync compiled and you haven't moved it, ask Claude Code for a new one: it creates it as a Design System artifact and, in a repo, also offers to keep it as files.
Official docs: Share session output as artifacts and Move from standalone Claude Design to Claude
Requirements
/designwith a brief: Claude Code v2.1.265 or later, in the CLI or the desktop app 1.13576.0 or later, signed in with your claude.ai account on a Pro, Max, Ultra, Team or Enterprise plan, and with artifacts available to your organization (the conditions are in the artifacts docs). With-pit doesn't draw: it only handlesconsentandrevoke.- Checked on v2.1.325: the command menu,
/designwith a brief in the terminal (on an account without the Design type, with the fallback page) and the list of design systems from Claude Code. The move and export steps come from the support article.