The latest articles on DEV Community by Quinn Foster (@quinnhacks). https://dev.to/quinnhacks https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210936%2F3f73a239-5a6a-4c4e-98a1-204efd07dda4.jpg https://dev.to/quinnhacks en Quinn Foster Tue, 27 Oct 2026 15:22:12 +0000 https://dev.to/quinnhacks/design-tokens-are-a-contract-not-a-color-list-2og4 https://dev.to/quinnhacks/design-tokens-are-a-contract-not-a-color-list-2og4 <p>We had a color palette that everyone partially followed. The problem wasn't the palette — it was that nobody knew which token was safe to use.</p> <p>What we did:</p> <ol> <li>Renamed tokens by intent (<code>surface-raised</code>, <code>text-muted</code>) instead of hue (<code>gray-200</code>).</li> <li>Deleted every token with zero usages.</li> <li>Added a CI check that fails on raw hex in components.</li> </ol> <p>The design system feels smaller now, and easier to extend. Weirdly, having fewer options made the UI more consistent.</p> <p>I'm learning GraphQL next — mostly to understand how schema design changes when the client picks the shape. Happy to hear war stories.</p> design css graphql