How to use
- Start after the token path and winner matrix already look good enough to defend in prose.
- Describe the scenario spread, alias depth, and which kind of conflict feels most suspicious.
- Read the matrix as a hotspot detector before you lock naming, audit, diff, or export.
Find direct conflicts, shadowed layers, and redundant overrides
This page fills the gap between “the winner flips are explainable” and “the token stack is safe enough to freeze.”
How to choose between nearby pages
Use Token Resolution Debugger when one concrete path still needs a local explanation. Use Token Override Matrix when the open question is still where the winner flips across scenarios. Use Color Token Audit or Color Token Diff when the scenario logic is already settled and the remaining work is set-wide cleanup or rollout review. Use this page in between, when the stack still feels collision-heavy.
FAQ
What does this page check?
It checks where one token role creates direct conflicts, shadowed layers, and redundant overrides across theme, state, and platform scenarios.
When should I use this instead of Token Override Matrix?
Use Token Override Matrix when the main question is where the winner flips across scenarios. Use this page after that, when the remaining question is whether those same scenarios now create conflict hotspots or redundant override layers.
When should I use this instead of Token Resolution Debugger?
Use Token Resolution Debugger when one concrete token path still needs a local explanation. Use this page when the path already makes sense, but the scenario spread still feels conflict-heavy.
What is stored in the share URL?
The share URL stores component scope, theme-set mode, state-set mode, platform-set mode, conflict focus, alias depth, prefix, and role.