I got tired of class-heavy UI code, so I started building Juice

<p>One of the easiest traps to fall into when building a design system is accidentally recreating CSS.</p> <p>At first, it seems harmless.</p> <p>You add a few utility

<p>I've spent a lot of the Road To KiwiEngine series talking about architecture from thirty thousand feet.</p> <p>Systems.</p> <p>Abstractions.</p> <p>Boundaries.</p>

<p>Let me ask you something.</p> <p>When was the last time you visited a website and thought <em>"wow, this UI has a personality"</em>?</p> <p>Be honest. Because I've been

<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

<blockquote> <p>“Programs must be written for people to read, and only incidentally for machines to execute.” - Harold Abelson</p> </blockquote> <p>Modern frontend applications

<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>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>Every project starts the same way:</p> <ul> <li>Rebuild navbar</li> <li>Rebuild hero section</li> <li>Add some basic animation</li> <li>Repeat… again and again.</li> </ul>