How to use
- Start after layer ownership and alias depth already look believable enough to keep.
- Describe which layer should answer first, which layer should stay available as a fallback, and whether theme overrides are allowed to cut the line.
- Review the winner order before audit, diff, or export turns it into a contract.
Decide who wins when token layers overlap
This page fills the gap between “the alias chain looks acceptable” and “export is ready.”
How to choose between nearby pages
Use Token Category Mapper when the open question is where a role belongs. Use Token Alias Planner when the open question is how many alias hops are acceptable. Use this page after those are mostly settled, when the remaining question is who wins first and what the last fallback should be. Use Token Resolution Debugger after the winner order already looks believable and the remaining question is why one concrete token still resolves to the wrong value. Use Color Token Audit after this page when the architecture already looks acceptable and the remaining job is checking the built set.
FAQ
What does this page decide?
It suggests fallback order, effective winner, and last-resort source when semantic, component, state, and theme layers can all answer the same role.
When should I use this instead of Token Alias Planner?
Use Token Alias Planner when the open question is how many alias hops are acceptable. Use this page after that, when the open question is which layer should win first when multiple answers are available.
When should I use this instead of Color Token Audit?
Use Color Token Audit when you already have a token set and want to inspect duplicate roles or weak contrast. Use this page before audit when the architecture question is still unresolved: who wins, and what is the last fallback.
What is stored in the share URL?
The share URL stores source layer, component scope, state variant, theme override mode, forced fallback source, platform target, prefix, and role.