Skip to main content
Design and Slides are in beta. They’re off by default.
Design and Slides let users of Claude Desktop on third-party (3P) ask Claude for a design, such as a wireframe, or a slide deck, and directly edit the result in the artifact. With design systems, you can provide brand and style templates that Claude follows when it creates designs and slides. Both require Claude Desktop 4.16336.0 or later.

Turn on Design and Slides

In the Enterprise Admin Console

In the Enterprise Admin Console:
  1. Go to Organization settings > Desktop 3P > Capabilities.
  2. Turn on the Artifacts switch. The Design and Slides switches appear under it.
  3. Turn on the Design switch, the Slides switch, or both.
  4. Click Save changes.
A group’s permission policy has the same switches, and its settings override the organization’s settings for that group.

In MDM or a bootstrap server

Set these keys in your MDM configuration or bootstrap response. To turn on only one of Design and Slides, leave out the other’s key.
The other two keys work only while artifactsEnabled is true. artifactsEnabled controls only Design and Slides artifacts, so live artifacts (interactive pages) don’t depend on it.

Use Design and Slides

Design and Slides work in Unified Claude, which is on by default. All of a user’s designs and decks are listed under Artifacts in the sidebar. Claude can’t make or change designs and decks in Code sessions or in runs of scheduled tasks. These restrictions apply to Design and Slides in Claude Desktop on 3P:
  • Sharing with other users: not available.
  • Comments: not available. Users can ask Claude for a change or make the edit themselves.
  • Export: designs export to HTML, PDF, and PNG. Decks export to PowerPoint, PDF, and HTML. Users can’t export a design to PowerPoint, or send designs and decks to Google Slides, other tools, or Claude Code.
  • Connectors: designs and decks can’t use connectors.

Design systems

A design system gives Claude your brand: your colors, type, logos, and rules, in a folder of plain files. Claude uses it when it creates designs and slide decks. Design systems require Claude Desktop 5.11492.0 or later. Artifacts must be on, and so must Design, Slides, or both. In versions before 6.6395.0, Design must be on. Users can have both kinds and choose which one Claude uses.

Create a design system

Write the files yourself, or have Claude draft them with a skill:
  1. Put your brand’s logos, fonts, guidelines, and any decks or code that show the brand well in one folder.
  2. Start a conversation from the home screen, add that folder with Project or folder, type /, choose draft-design-system, and describe what you want. For example: “Draft a design system for Acme from the files in this folder.”
  3. Claude writes the design system as a new folder, and tells you what it assumed and what’s missing.
A design system has these files. To change them later, edit them yourself or ask Claude. To create a design system by hand instead of with the skill, write a README.md, a tokens.json, and a tokens.css. Below is an example tokens.json. Keep its structure, use each name only once, and write colors as hex, rgb(), hsl(), or oklch().
tokens.json
Below is an example tokens.css with the same values.
tokens.css
In Claude Desktop 6.6395.0 or later, you can leave out tokens.css when you add a folder in Settings. Claude Desktop generates it from tokens.json. It also replaces any tokens.css whose first comment says it was generated from tokens.json. Plugins must always include tokens.css.

Add a design system on one computer

  1. Go to Settings > Design systems and click New design system.
  2. Choose the folder, with README.md at its top level, and confirm. The folder’s name becomes the design system’s title.
  3. Open the ⋯ menu on its row to make it the default, update it, or remove it.
Settings, Design systems, with one design system named Acme Design System. Its menu offers Update, Set as your default, and Remove.

A design system added from a folder, with its menu open.

You can add up to 1,024 files and 256 MB. Files larger than 20 MB are skipped. If you set allowedWorkspaceFolders, the design system folder must be inside one of the folders you allow.

Package a design system as a plugin

To share a design system with your organization, put it in a plugin marketplace, such as a Git repository. Make one plugin for each design system. Inside the plugin, name the folder exactly design-system:
Add the following to .claude-plugin/marketplace.json:
.claude-plugin/marketplace.json
Add the following to acme-design-system/.claude-plugin/plugin.json:
acme-design-system/.claude-plugin/plugin.json
If you don’t use Git, a marketplace can also be a file on a web server. For design systems, serve it from your inference gateway or bootstrap server. In Claude Desktop 6.6395.0 or later, you can use another web server if you set manifestSha256 in the marketplace’s entry and sha256 for the plugin’s archive in marketplace.json.

Choose which plugins are design systems

Write each design system as plugin@marketplace, using both names from marketplace.json. The first one in the list is your organization’s default. In the marketplace entry, set ref to a full 40-character commit, not a branch or tag. For the other fields, see Plugin marketplaces. In the Enterprise Admin Console:
  1. Go to Organization settings > Desktop 3P > Plugins and add the marketplace. Enter the commit in Ref.
  2. Go to Organization settings > Desktop 3P > Capabilities and list the plugins in the Design systems row.
  3. Click Save changes.
The Design systems row in the Enterprise Admin Console, listing acme-design-system@acme-brands and acme-events@acme-brands.

The Design systems row on the console's Capabilities page.

In MDM or on a bootstrap server, set allowedPluginMarketplaces and artifactsDesignSystemPlugins. In an MDM profile, write each list as a string, as shown in Configuration format.
After you change the list of design systems, users see the new list once they restart Claude Desktop.
Settings, Design systems, with Acme Design System marked Org default and Acme Events marked Organization.

What users see in Settings.

Users can choose their own default, but they can’t update or remove your organization’s design systems. When a user asks for a design or a deck, Claude uses the default or the one the user requests.

If a design system doesn’t appear

Open main.log in the app’s logs folder and look for the plugin’s name and one of these words: If the design system appears but Claude can’t read it, check that its folder is named design-system.