Design Tokens Belong in the Document
When tokens travel with the design, generated work can become part of a system instead of remaining a one-off visual.
value → meaning
A hex value can make one object blue. A semantic token can make an entire product understand what “accent” means.
That distinction becomes more important when agents participate in design. An agent that copies values can imitate a screenshot. An agent that understands tokens can extend a system.
Tokens are decisions, not swatches
A token links a visual value to a role. The role survives when a team changes theme, brand or accessibility requirements. It also gives reviews a shared vocabulary: the question becomes whether an element uses the right semantic choice, not whether two hex strings happen to match.
Fanta stores variables and modes as part of the same document the canvas uses. The inspector can bind a property to a token, and the rendered result updates when the active mode changes.
Systems give agents useful constraints
Creative agents are more reliable when the space of valid choices is explicit. A collection of semantic colors, spacing values and component properties is more useful than a paragraph asking the model to stay on brand.
The document keeps token bindings explicit in readable source, while typed content operations leave a structured change that a human can review.
- Variables expose named choices.
- Modes express coordinated themes or contexts.
- Component properties limit valid variation.
- History shows which system decision changed.
Turn generated output into system material
Generated imagery often arrives at the edge of a design system. The composition may be compelling, but type, color and spacing still need to become repeatable.
A structured document lets the team keep the useful visual material while rebuilding the surrounding decisions with tokens and components. Generation becomes input to the system rather than an exception to it.
Portable semantics are the long game
When token bindings live in readable design source, other tools can understand them. Build systems, agents and future editors can all see that a fill refers to a role rather than a literal value.
That is how visual intent survives beyond one application session—and how design and implementation can converge without flattening one into the other.
The strongest guardrail for AI-generated design is not a longer prompt. It is a better-defined system.
The takeaway