Skip to main content

Search rules

Search all UI Guides rules by name, category, or source

designCustom

Colors That Clash

SHOULD

SHOULD: Use harmonious color combinations from a defined palette. Clashing colors create visual discomfort. Consider color temperature and saturation balance.

Use harmonious color combinations from a defined palette

Bad

Good

Why it matters

This is our own rule, not an upstream citation — the Rams review has no bullet for it, and we previously mislabelled it as one. The practical test is not "do these two hues look nice together" but "where did this hue come from": a palette generated in a perceptual space (OKLCH is the practical one) gives you hues at matched lightness and chroma, so a warning next to a success next to a primary read as members of one family instead of three separate accidents.

Ad-hoc picks fail in a specific way — they collide at the same lightness, so the eye cannot tell which one is meant to be louder. Choose the relationship (analogous, complementary, triadic) once, encode it as tokens, and let components consume tokens only.

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.