Most design systems fail at neutrals, not at accent colors. The neutral palette carries 80% of the visual weight in a typical UI — backgrounds, surfaces, dividers, secondary text, placeholder text, disabled states. If the neutral scale is too flat (steps too close together) or too warm-cold mismatched (warm accent, cool neutral), the system feels off in ways that are difficult to diagnose but immediately visible.
True gray (equal R, G, B values) almost never looks neutral in practice because it reads against the color temperature of the ambient light and surrounding hues. On most screens, with most content, a very slightly warm gray (shifted toward yellow-red) reads as more neutral than mathematically pure gray. The specific neutrals used by Apple (Human Interface Guidelines), Google Material, and Tailwind are all slightly warm-shifted — this is intentional.
The warm-cool decision in neutrals should be driven by your accent palette, not by isolation preference. Warm accent colors (orange, yellow, red-orange) require a warm neutral family to avoid temperature conflict. Cool accent colors (blue, purple, teal) are more flexible but often look crisper on slightly cool-neutral backgrounds. The test: put your accent color on your neutral — do they feel like they belong to the same designed system, or do they look like they came from different sources?
