Token Naming Conventions

Use when designing, auditing, or critiquing a design-token naming scheme for any design system. Names the universal principles: hyphen-separated kebab-case names; prefix-loaded naming where the first segment declares the token's class and kind, so a linter or agent can derive contrast obligations from the name alone; redundant class encoding in metadata so validators catch name/metadata mismatches; physical, non-semantic primitive names (hue angles, not accent-teal) with semantic labels reserved for the theme layer; resolution-chain naming (direct vs via-semantic component-token shapes); and the rule that theme and density are runtime axes that never appear in a token name. Cite when an agent proposes dot-separated paths, semantic primitive names, or names whose class isn't derivable from the prefix. For UDTS's concrete instantiation see udts-naming-convention.

thrillmade Updated 3 repo stars

File contents

thrillmade/agent-skills commit cf3ef76130

Frequently asked questions

npx get-skill add thrillmade/token-naming-conventions