How to use
- Start after the role owner already looks believable enough to call it semantic or component-first.
- Describe whether state and theme need their own override layers, then decide whether the public alias should be direct, bridged, or two-step.
- Review alias depth before you freeze naming, audit, diff, or export.
Set alias depth before naming locks it in
This page fills the gap between “the role owner looks believable” and “the key style is ready for docs or code.”
How to choose between nearby pages
Use Token Category Mapper when the open question is which layer should own a role. Use this page after that, when the ownership is mostly settled and the remaining question is how the alias chain should be wired. Use Token Fallback Map after this page when the alias chain already feels acceptable and the remaining question is who should win first when multiple layers can answer the same role. Use Color Token Naming after those choices when the last question is the exact key style.
FAQ
What does this page plan?
It suggests a token alias chain, alias depth, and fallback structure across semantic, component, state, and theme layers before naming, audit, or export.
When should I use this instead of Token Category Mapper?
Use Token Category Mapper when the open question is which layer should own a role. Use this page after that, when the ownership is mostly settled and the remaining question is how the alias chain should be wired.
When should I use this instead of Color Token Naming?
Use Color Token Naming when the alias chain is already acceptable and the remaining question is the exact key style. Use this page before naming when alias depth or fallback layers still feel unstable.
What is stored in the share URL?
The share URL stores base layer, component scope, state mode, theme mode, alias style, prefix, and role.