How to use
- Start after layer placement, alias depth, and fallback order already look believable enough to keep.
- Describe one token role, the active scope, override mode, and how many alias hops still exist before the final answer.
- Read the trace as a local explanation for one token path, not as a full audit of the whole token set.
Explain why one token wins after alias and fallback overlap
This page fills the gap between “the fallback order looks acceptable” and “I can explain one concrete token failure.”
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 Token Fallback Map when the open question is what the general winner order should be. Use this page after those are mostly settled, when one concrete token still needs a trace that explains why its final value won.
FAQ
What does this page debug?
It traces one token request through alias hops, layer candidates, the winning layer, and the last-resort fallback source.
When should I use this instead of Token Fallback Map?
Use Token Fallback Map when the open question is what the general winner order should be. Use this page after that, when one concrete token still needs a trace that explains why its final value won.
When should I use this instead of Color Token Audit?
Use Color Token Audit when you want a set-wide check for duplicates or contrast problems. Use this page before audit when the unresolved question is still local to one token path.
What is stored in the share URL?
The share URL stores source layer, component scope, state variant, theme override, fallback source, platform target, alias depth, prefix, and role.