Why ad-hoc color names collapse under scale, how role-based naming survives redesigns, and why inheriting a naming convention beats inventing one.
Click a hex value to copy it
Early-stage projects name colors after feelings: calm blue, warm sand, deep forest. That works when three people share a Figma file. It stops working once marketing, product, and engineering each interpret those labels differently. The name becomes a source of ambiguity instead of clarity. Production-grade naming ties the label to a role in the interface, not to an aesthetic impression.
A token named brand-surface-muted keeps its meaning when the underlying hex changes from warm beige to cool grey. A token named sandy-warmth does not. The Monochrome Studio collection is a useful test case: the palette spans a wide neutral range, and the only thing that keeps it organized is role structure. Without that, five shades of grey become indistinguishable in code.
Consistency matters more than breadth here. Every chromatic color in the ColorArchive archive follows one pattern — hue root, lightness band, chroma band, as in amber-pearl-muted — so a primitive layer built from it can grow from one palette to the next without translating between two naming systems. Put the role layer on top, and the convention is already there; you just extend it.
