Exporting your design system artifacts
Every studio that holds a collection of artifacts lets you export that collection to a file with the Export action in its header. Exports run entirely in your browser and never leave your machine unless you choose to share the file.
What each surface exports
| Surface | Export action | File | Format |
|---|---|---|---|
| Presets | Export | <system>-registry.json | shadcn-compatible registry.json (the same format the Design system settings Export tab produces). Works with v0, Cursor, Windsurf, and any MCP tool. |
| Skills | Export | <system>-skills.json | JSON bundle of every skill (name, trigger, description, instructions, parameters, composition). |
| Skill builder | Export | <skill>.md | A single SKILL.md file for the skill you are editing. This is the same format the skill Import accepts, so it round-trips. |
| Patterns | Export | <system>-patterns.json | JSON bundle of every pattern (name, description, category, rules, accessibility, examples). |
Notes
- The Export action is disabled when a collection is empty.
- Exports reflect the artifacts currently resolved for your active layer, the same set the page is showing you.
- For the whole design system at once (tokens, presets, patterns, and coding agent adapters together), use the Export tab in Design system settings.
Related
- Design system settings has a broader Export tab covering tokens, CI and enforcement rules, and AI coding-agent adapters.
Last reviewed by @jschuyler