Stop exporting SCSS variables from your design system
A developer took to Dev.to on April 25th to make a pointed argument: design systems should stop exporting SCSS variables. The post, which has attracted modest early traction with a score of 6.1, challenges what has become a quietly accepted practice in front-end architecture — the idea that shipping raw SCSS variables as part of your design system's public API is a reasonable way to distribute design tokens. The argument, in essence, is that this creates a tight coupling between consumers and the implementation details of your system. When your design system evolves — when you switch from SCSS to CSS custom properties, or restructure your token naming, or migrate to a different toolchain entirely — every consuming project breaks. The SCSS variable becomes a contract you never meant to sign. The piece appears to be advocating for CSS custom properties as the distribution layer instead, keeping implementation decisions internal and exposing only the stable, standards-based surface.
If confirmed as a perspective that gains traction in the design systems community, this matters in a quiet but persistent way. Every organisation running a design system at any meaningful scale has teams downstream who have wired SCSS variables directly into their component code. Those teams get fast feedback when the design system changes — in the form of broken builds. The second-order effect is more interesting: moving to CSS custom properties as the export format forces design system teams to think harder about their public API shape, which is discipline most teams frankly need. It also opens the door to runtime theming, reduced specificity battles, and interoperability across frameworks that SCSS never offered. The strategic implication is that design system maturity is being measured less by how many components you ship and more by how stable and technology-agnostic your token layer is.
Watch for senior design system practitioners — particularly those maintaining systems at scale — to either validate or push back on this framing publicly, and for any tooling announcements that treat CSS custom properties as a first-class export target.
<p>"Why do you need 3 layers of CSS variables? Just use brand-800 directly."</p> <p>That was me. Here's what changed my mind.</p> <p>I made a table of how shades map in light vs
<p>We're in an era where developers write UI with AI. You describe a screen, Claude or Copilot generates the code, and you ship it. But there's a gap nobody talks about:</p>
<p>Design tokens are a single source of truth for reusable design properties, stored in such a way that computers and humans can easily read and process them. They represent core
<p>Design systems exist to keep products consistent. So what happens when the system and the product are both AI-generated, in the same session.... by the same tool?</p> <p>I ran
<p><em>The whole industry seems to have agreed on a standard for design tokens. The shift it sets up is still on its way.</em></p> <p>Design tokens are not new. The term was
<p><em>Also available in <a href="https://dev.to/ortizfranklindev/construir-un-sistema-frontend-que-siga-teniendo-sentido-dentro-de-diez-anos-242o">Español</a></em></p> <h2> The
<p>** DesignKit is a library of 502 self-contained HTML components + 33 full-page designs (mobile + web). Every component uses CSS custom properties (<code>--kit-*</code>). Drop
<blockquote> <p><strong>"Tailwind becomes exponentially more maintainable when styling decisions become architecture — not scattered utility strings."</strong></p> </blockquote>
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →