Publishing and Applying Your Design System
A design system sits as a Draft until you flip one toggle. Published systems show up in every new project's setup flow, so anyone in the org can pick the right system at creation time. No re-uploading brand assets, no repeating brand prompts.
How to publish
Open organization settings
Click your organization name in the lower-left, then the 'Design systems' tab at the top. Every system you've created appears in the list, each with its own Draft/Published toggle.
Flip the toggle
Click the toggle in the right-hand column of your system's row. It switches from 'Draft' to 'Published' inline, no confirm dialog, no separate screen.
Check the sidebar
Head back to the homescreen. The New-prototype panel now shows a 'Design system' dropdown above Wireframe / High fidelity, proof your system is available for any new project.
Published vs. Make default
The 'Make default' button next to each system is a separate setting from the Publish toggle. Published means 'pickable at project creation'. Default means 'pre-selected in the dropdown'. You can publish many systems but only one is the default, useful when you have a primary brand plus a couple of sub-brands or white-label variants, and you want the primary one auto-selected.
Updating a published system
Open the system
From the design-systems list, click 'Open' on the right side of the row (not the toggle).
Remix via chat
Inside the system, use Remix to refine via chat. 'Add a dark-mode variant of the primary palette.' 'Introduce an error state for buttons.' Remix keeps the system published, your edits flow through live.
Flip back if you break it
If a Remix change makes the system worse, toggle back to Draft to pull it from new-project selection while you fix it, or delete the system and restore from an earlier source.
Before publishing widely, create a test project with a prompt representative of what your team builds. If the test output doesn't feel on-brand, the system source wasn't rich enough, go back to Lesson 7 and add more sources.
Your team inherits the system
- Published the system
- Know how to Remix it later
- Validated with a test project
Last design-system lesson: team and enterprise setup for admins.