Token Naming Quick Reference
Recall practical token naming rules for primitives, semantics, aliases, and component tokens.
Layer check Primitive or semantic? Ask what should remain stable if the visual value changes. Objection Why not just call it newBlue while we experiment? A teammate wants a temporary name during a theme update. Your line If it ships, consumers will build meaning around it. Let's call it by purpose now and mark the value experimental if needed. Temporary names become permanent contracts when other teams copy them. The response protects experimentation without creating durable ambiguity. Recall When should a token be component-specific? When the decision belongs to one component's contract rather than a shared semantic role. Example: button.primary.background.hover…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in