Anthropic plans to fold standalone Claude Design into Claude on December 14

• Standalone Claude Design closes on December 14. Integrated Design and Slides have “much higher” usage, according to nateparrott's announcement.
• Design inside Claude can use the conversation's context, files, and connectors, as the accompanying notice explains.
• Claude Code has a new codebase-aware /design skill, described in nateparrott's reply, but /design and /slides are still feature-flagged.

A single migration can bring over every design system in an organization, including other people's. The Claude Code setup route can read React tokens and components directly, while Design and Slides are now available on every plan, including Free.

Design has worked inside every Claude conversation since September 16. The standalone site at claude.ai/design remains accessible until December 14, 2026, then redirects to Claude.

Anthropic says maintaining two versions slows down fixes for both. In the announcement, nateparrott asks users to report where the integrated version falls short before the switchover.

Alongside the consolidation, Anthropic's October 8 update lists five changes across Docs, Slides, and Design:

• Enterprise controls: Artifacts support customer-managed encryption keys, and admins choose which artifact templates their organization uses.
• Team editing: Teammates and Claude can work on the same document, deck, design, or dashboard.
• External sharing: Designs, slides, dashboards, and animations can be shared outside an organization or through public links, if an admin allows it.
• Formatted exports: PowerPoint and PDF downloads retain the editor's formatting; decks can go directly to Google Slides as editable files.
• Mobile editing: Documents, decks, and designs can be changed in the Claude mobile app.

Better organization is still being worked on, according to nateparrott's reply.

Claude Code's new /design skill can work with an existing codebase, nateparrott said in a reply.

Both /design and /slides remain feature-flagged. While troubleshooting terminal access, he asked whether telemetry or artifacts had been turned off.

For an existing React design system, Anthropic's setup documentation describes a separate /design-sync command. It reads tokens and components directly, rather than extracting a brand system from references such as decks, logos, or fonts.

The Artifacts page now offers “Migrate team design systems.” Anthropic's migration guide specifies several rules beyond copying files:

• Organization-wide scope: Anyone who can use Claude Design can start migration, not just an owner. One run covers every design system in the organization.
• Ownership: Systems retain their owners and sharing permissions. If an owner has left, the organization's Primary Owner inherits ownership.
• Organization visibility: Published, non-private design systems become available to everyone in the organization. Individual-plan migrations do not share anything.
• Excluded systems: Empty systems and systems made from built-in starter themes are skipped, even if those themes were edited.
• Editing limitation: Migrated systems retain their files, but direct editing on their page is not available yet. Their editors see a note telling them to ask Claude for changes.
• Repeat migrations: New or changed standalone systems can be migrated again. Systems edited in Claude are skipped so those edits are not overwritten.

Original design systems remain unchanged in the standalone version until it closes. Failed migrations show a reason, such as excessive size, and can be retried after the underlying problem is fixed.

Turning off Artifacts blocks both new designs and migration. The migration guide identifies three additional access constraints:

• Enterprise settings: Design systems are off by default on Enterprise, while they are on by default on Team.
• Custom roles: On Enterprise, the design system owner's role must include design-system permissions for migration to succeed.
• Zero data retention: Organizations with zero data retention cannot enable Artifacts, so they cannot migrate into the integrated experience.

The admin guide also distinguishes the standalone site's setting from the integrated Design template. Enabling one does not describe the state of the other.

Existing projects keep working in the standalone version until closure. Up to 60 also appear on the Artifacts page, but those entries still open the standalone site; Anthropic says details about moving projects are coming soon.

The same guide identifies what will disappear:

• Chats with Claude do not transfer.
• Comments on projects and design systems do not transfer.
• Public links to standalone projects stop working after closure.
• Standalone originals are deleted after closure under Anthropic's data-retention practices.

For client work, losing the comment trail is the ugliest part of this move.

Project archives are downloadable individually, with no bulk-download option:

• Export path: “Share” → “Project HTML” → “Project archive” → “Export.”
• Slide decks: “Project HTML” sits under “More formats and apps.”
• Output: A .zip containing every file in the project. Exporting is free and does not count toward usage limits.