How Color Naming Systems Work — From Pantone to Design Tokens

A color name is a contract. When a brand designer says "use Ocean Blue" and a developer writes `--color-blue-600`, they are either describing the same thing or a future support ticket. This issue is about how color naming systems work — from museum-quality standards like Munsell and Pantone to the semantic token patterns used in modern design systems. Pantone's Matching System is the original industry lingua franca: each swatch has a number (PMS 286 C), a name when it has one, and a spectrophotometric measurement. Munsell adds structural logic — hue, value, chroma — that makes systematic color relationships legible across any hue family. NCS (Natural Color System) uses a perceptual model where any color is defined by its resemblance percentages to elementary colors. These systems exist to make color communication unambiguous across materials, countries, and years. In software design, the challenge is different. You need names that survive refactors, work in code, and communicate intent to people who are not looking at swatches. The two-tier model — primitive names (blue-500) plus semantic names (interactive-default) — solves this by separating what the color is from what it does. A well-named design token system means a developer can write `color: var(--text-secondary)` and know exactly when to use it, without needing to see the hex value. Poetic color names serve a third purpose: emotional alignment. Naming a muted sage green "Morning Dew" versus "Muted Green 3" changes how designers talk about and use the color. Product teams with shared color vocabulary make more consistent decisions — when everyone calls it "Ocean" it creates coherent intention around what the color should communicate.