Design systems · since v1.5.0
Import from Claude Design
A Claude Design export lands in the studio as a first-class system — the colors, type scale and rules it carries become the kit your agent designs against.
Why it matters
A good-looking export trapped in one file is a dead end. Importing it as a system means every project, variant and template in the studio can draw on it — the tokens and rules stop being a picture and start being the grammar your agent must pass.
How it works
- 1Point at the exportSystems → Import takes a Claude Design export file. The studio reads the tokens, type and rules it contains.
- 2It becomes a systemThe import lands in your systems library with its own name, preview and edit history — a real system, not a one-off palette.
- 3Apply it anywherePick the imported system on any project and the design kit hands it to the agent as the rules of the run — gate included.
Capabilities
- Imports Claude Design exports into the systems library
- Tokens and rules become gate criteria, not just swatches
- Works across templates — slides, pages, 3D, brand kits
- Imported systems edit and version like native ones
FAQ
What exactly gets imported?
The export's design tokens, type scale and style rules — the parts the design kit can enforce as a system, not a flattened image of the design.
Can I edit the imported system?
Yes. Once imported it's a normal system: rename it, adjust its tokens, and save variants of it like any other.
Does it work the other way — export back to Claude Design?
The studio's design tokens export gives you a portable token file; how far that round-trips into Claude Design depends on what that tool accepts.
In the docs
Related features
Design with the agent you already have.
Free to try, buy once — the studio and your own coding CLIs do the rest.
Download