Overrides
Overrides let a single project diverge from the brand where it has to, without touching the brand itself. They are sparse: you override only the values that differ, and everything else continues to inherit from the brand.
Types of override
A project can apply three kinds of override:
- Token overrides change a brand style token for this app, such as a color, radius, or type size.
- Visibility overrides hide a component, block, or variant from this app, while the brand keeps it switched on for everyone else.
- Rule overrides change a brand rule for this app, including its text, Guidance, or Importance.
Each override is scoped to the project it lives on. Other projects and the brand are unaffected.
How the effective view is produced
The effective (resolved) view is what an AI tool actually receives. UI Rules produces it in two passes:
Start from the brand
Begin with the full brand ruleset: styles, rules, component vocabulary, and visibility settings.
Apply the project overrides
Layer the project's token, visibility, and rule overrides on top. Where an override and the brand disagree, the project wins. Where there is no override, the brand value carries through unchanged.
The result is the effective view, and it is exactly what the connected app reads over MCP. Because overrides are sparse, the effective view stays in sync with the brand for everything you have not explicitly changed.
Where overrides live
A project's overview lists every override it carries under Overrides, filterable by kind. A project with none serves the brand ruleset unchanged. Add one from the same screen: pick what to change, then edit the value, hide the target, or write the rule.
The brand is never modified
Overrides only ever change the project's effective view. The brand remains the source of truth for every other project and is never edited by an override. To change a value everywhere, edit the brand instead. See Overview.
