How to use
- Start after the token value itself looks acceptable enough for design-system discussion.
- Describe whether the token is global or component-specific, interaction-dependent, theme-dependent, and broadly reusable.
- Review the recommended category before you move into naming, audit, or export.
Wave 63 expansion
Decide token placement before naming
This page fills the gap between “the colors exist” and “the key naming contract is ready.”
How to choose between nearby pages
Use Color Token Naming when the layer placement is already decided and the remaining question is the exact key pattern. Use Theme Color Tokens when you are already building theme bundles. Use this page earlier, when the layer itself still needs one more governance pass.
FAQ
What does this page decide?
It suggests whether a token should live in semantic, component, state, or theme layers before naming, audit, or export.
When should I use this instead of Color Token Naming?
Use Color Token Naming when the layer placement is already decided and the remaining question is the exact key pattern. Use this page first when the layer itself is still unclear.
When should I use this instead of Theme Color Tokens?
Use Theme Color Tokens when you are already building the actual theme bundles. Use this page when you still need to decide whether the token belongs in theme space at all.
What is stored in the share URL?
The share URL stores token purpose, component scope, state dependency, theme variance, platform reuse, and prefix.