Luis on what the ​“shadcn-ification” debate is actually about — not the visual uniformity, but the organizational misread: ​“The mistake isn’t in the ingredient. It’s in thinking that having access to good ingredients is the same as knowing how to cook.”

Stakeholders are concluding that the design system infrastructure is done because a great foundation exists. The teams that have spent years practicing design systems understand exactly why that conclusion is dangerous.

Fantastic update to shadcn/​ui — now you can pick your component library (Radix UI or Base UI), visual style, theme, icon set, base color, fonts, and build something that doesn’t look like everything else. Shadcn/​ui was always highly customizable thanks to well-thought-out design primitives and treating components as a boilerplate, but this release takes it to the next level.

Speaking of shadcn, Vercel launched a free course on the fundamentals of modern UI development with shadcn/​ui. I’m happy to see a high-quality introductory resource for teams adopting this stack, as a mental shift from building with homegrown intertwined components to a composable, reusable, and themeable library could be challenging.

A great resource for front-end engineers from Vercel, authored by shadcn and Hayden Bleasel: ​“Modern web applications are built on reusable UI components and how we design, build, and share them is important. This specification aims to establish a formal, open standard for building open-source UI components for the modern web.”

As new tools blur the lines between design and engineering, I strongly believe that any designer working on or contributing to a design system will benefit from understanding these concepts.

Matt Wierzbicki shows how to turn Figma designs made with shadcn/​ui into production‑ready code by setting up Cursor to use shadcn/​ui and Figma MCPs.