Apply a brand change everywhere
How do I change the brand across every screen at once? Bind your properties to tokens, and write the brand as a small file. A brand file is often three or four lines, and switching to it re-skins every bound element. The work is in the binding: do it once, and the switch is free.

How do I run a rebrand?
Three steps. The first one is the only real work.
Bind properties to roles.
Reach for semantic roles like color.surface, spacing.md and radius.lg, because they are mode-aware. The right toolbar binds a property to a token with a click, and an agent uses tokens on its own when a system is active. Type and shadows bind too, as composites like typography.h1 and shadow.md.
Write the brand as an overlay.
Brands are sibling .ds files beside default.ds that hold only their deltas: a seed, maybe a font family, a few overrides. Or ask: "add an alternate brand called sunset with a warm orange primary."
Switch and watch.
The Design system section sits at the top of the right toolbar, with a dropdown per mode axis and the brand picker. Hover to preview, click to commit. With nothing selected you set the canvas; with a selection, the element.
primary: boldness(color(#FF6A00))
font.family: Inter
color.primary { $default: primary.firm, dark: primary.subtle }Can one area stay on the old brand?
Yes. The cascade runs per element, then per canvas, then per folder, so one screen can hold while the rest moves, and a Marketing folder can carry its own overrides. See Modes and brands.

Common questions
What will not follow the switch?
A raw hex stays that hex. Select the element and tell the agent to bind the fill to the closest token, then switch again.
Can a value differ per mode?
Yes, through a semantic. Primitives stay the same in every mode on purpose.
Where next?
Theming and multi-brand: Modes and brands.
Every token type: Tokens.
Start from the beginning: Design system overview.
Follow a re-skin: Design tutorials.
Keep agents on the system: Build feature UI.