Token naming conventions

A design-token name should let an agent or linter derive the token's class and contrast obligation from the name alone. The universal shape that makes this possible is hyphen-separated, prefix-loaded, and redundantly encoded in token metadata so a validator can catch a name that disagrees with its own class.

These are system-neutral principles. For one worked instantiation — concrete prefix families, spec fields, and worked chains — see udts-naming-convention.