r/DesignSystems • u/otc_playDraft • 17h ago
A design-system gate caught 46 color violations, then exposed the palette I did not have
I added a deterministic “steel curtain” to my portfolio repo. It checks only the lines a pull request adds and blocks things it can prove are wrong: raw colors that already have tokens, classes with no stylesheet, images without alt text, and a few other mechanical rules.
On my homepage redesign it finished in 38 seconds and stopped the merge on 46 findings. Every blocker was a color I had already named. Twenty-nine were exact token values typed by hand, and 14 of those were inside one sticker component.
The report-only findings were more interesting. Thirteen colors were too far from any token to block. Ten of the twelve unique colors were drawing materials: sticker release paper, aluminum, glass, a bezel, and a lens.
My system has a brand palette. It does not have a material palette.
The gate also writes proposed components and patterns into a registry for me to review. It has proposed 18 additions so far. I have promoted none. The script can spot drift and collect evidence; deciding what the system should keep is still manual.
I am trying to decide what the correct layer is for those material colors. Would you:
- promote them into the main token system;
- create a separate material palette with its own rules;
- keep them local to the illustrated objects;
- or treat this as evidence that the gate is checking at the wrong level?
Full write-up with the receipt and swatches:
https://www.rdeboerdesigns.com/notes/the-gate-stopped-my-redesign/