Dark palette · your decisions
What we need from you
We want to shrink the dark palette to your 34 primitives + 36 dark tokens. That needs two real design calls from you (1 and 2); the other three mostly follow. Nothing has been deleted.
✓ 34/34 primitive values already correct
✓ 6 dark tokens re-aliased
✓ 0 deleted
1
Reconcile your own dark colours
Blocker
14 of your dark tokens use 9 colours that aren't in your 34-stop palette. Your spec and your palette disagree, so these tokens have no approved primitive.
Do: for each of the 9 colours, either add it to the palette, or swap the token to an approved stop.
Add to palette (no close match)
Neutral-975, Green-900, Red-900, Yellow-900
Swap or confirm (near-duplicate exists)
Neutral-300, Blue-400, Yellow-300, Yellow-200, Neutral-900
See the 9 and the tokens they back →
2
Set the rule
Decides the rest
Is your 34 + 36 a hard limit, or a guideline? This decides how much work 3 to 5 below are.
Do: pick one — Hard cap (delete everything else, needs code migration) or Working palette (legacy colours stay available internally, just unpromoted).
▸ Our recommendation: working palette.
3
The product’s off-palette colours
Only if “hard cap”
The app uses ~50 colours not on your list: deal / entity / badge / premium, gold, info blues, overlays, glass, extra status depths.
Do: per family, approve it as an exception, or name a replacement and we migrate the code.
▸ Our recommendation: approve as internal exceptions for now.
See the families →
4
Light mode
Park it
98 light tokens exist but none are designed against the new palette yet.
Do: confirm we leave light mode untouched until the dedicated light pass. Nothing to design now.
5
Safe cleanup
Quick yes
16 unused and test tokens are sitting in the file with no alias and no code use.
Do: say yes and we delete them. No design impact.
See the 16 →