Skip to main content

Search rules

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

aestheticsimpeccable

The Cream Background Is a Default, Not a Choice

NEVER

NEVER: Reach for the reflexive warm cream/beige page surface — mechanically: `min(r,g,b) >= 209`, channels ordered `r >= g >= b`, and warmth `r - b` between 6 and 48, which catches `bg-amber-50/100`, `bg-orange-50/100`, `bg-yellow-50`, and `bg-stone-50/100/200`. If you can guess the palette from the product's domain alone, it is the training-data reflex. Derive the surface instead: hold the brand hue angle and drop chroma to roughly 0.01.

Derive the page surface from the brand hue rather than reaching for the reflexive warm beige

Bad

Good

Why it matters

Cream is mechanically identifiable: min(r,g,b) >= 209, channels ordered r >= g >= b, and warmth (r - b) between 6 and 48. That window also catches Tailwind's bg-amber-50/100, bg-orange-50/100, bg-yellow-50 and bg-stone-50/100/200 — the exact classes a generator picks when it wants to look considered. Pair the check with the skill's category-reflex test: if you can guess the palette from the product's domain alone (fintech blue, wellness sage, AI-tool cream), it is the training-data reflex talking, not a decision.

The fix is derivation, not avoidance — take the brand hue, hold the hue angle, and drop chroma to roughly 0.01 for a tinted neutral that belongs to this product and no other.

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.