When Design Systems Start Acting Like Infrastructure
#Issue 51
After reading enough article submissions, you start to notice patterns.
Not trends in the buzzword sense, but recurring questions teams are quietly trying to answer. How firm should a design system be? Where should opinions actually live? What happens when the system has to hold up in code, in tooling, and increasingly, in front of AI?
This issue reflects that shared line of inquiry. The articles here aren’t circling the basics, they assume the system exists and ask what it means to take it seriously. That shows up in pieces about enforcing constraints, structuring tokens so they survive real usage, documenting rationale so decisions don’t evaporate, and experimenting with AI in ways that don’t unravel hard-won consistency.
Taken together, it feels less like debate and more like a community tightening its practice. Fewer hypotheticals. More “this is where it breaks, and this is what we did about it.”
If your own system is somewhere between useful and foundational, there’s a good chance you’ll recognise the shape of the problems, and maybe steal a few solutions.
In this issue
📚 Featured Articles
📰 Published in the Last Week
✨ Inspiration
🎗️Support us
📝 Closing Thoughts
📚 Featured Articles
Must-read articles at www.designsystemscollective.com.
💡 Have an article to share? Submit it here!
Your design system has opinions. They’re just not being enforced by Murphy Trueman
Why We Like It: A practical, urgent argument for turning design systems into enforceable infrastructure with validation at design-, build- and runtime. It gives clear pathways and examples for teams to reduce shipping risk and support AI consumers of components.
Pro Tip: If your system still lives primarily in docs and hope, start enforcing a small set of validation rules on the components teams misuse most. The article shows how to encode required children, forbid bad prop combos and use TypeScript and linting to catch errors earlier—benefits that scale as AI agents start producing UI.
Design Tokens in Webstudio: A Practical Implementation Guide by Roberto Moreno Celta
Why We Like It: A comprehensive, hands-on walkthrough of token architecture, mapping from Figma and pragmatic tips for building scalable token systems in Webstudio using real CSS custom properties. It is unusually implementation-focused for design tooling content.
Perfect For: Frontend engineers and design system leads who need a practical token-first workflow. The piece covers primitive, semantic and component token layers, dark mode, responsive tokens, deprecation strategies and export workflows so teams can align design and code without surprises.
Why Engineers Can Say “This Is Wrong” and Designers Can’t by Kevin Muldoon
Why We Like It: A sharp, evidence-driven critique of design critique culture that recommends making design decisions falsifiable through documented rationale and accessible decision logs. It offers a clear roadmap to make critique outcomes decisive.
Hot Take: Design teams should treat rationale as first-class documentation. Muldoon argues that documenting the why for every spec creates falsifiable criteria that resolves debates, prevents design-by-committee and scales design authority beyond individuals—an essential read for anyone trying to professionalise design practice.
How I Use Claude Code Agent with VS Code as a Design System Designer by Dhika Endi Astowo
Why We Like It: A concise, practical workflow showing how an AI coding agent can accelerate component creation when paired with a single-source-of-truth CLAUDE.md. It balances speed gains with useful caveats about security and governance.
Pro Tip: Use a project-level CLAUDE.md to encode tech stack, tokens and accessibility rules so generated components match your standards. This article is a useful playbook for teams experimenting with agent-assisted coding while protecting consistency and compliance.
📰 Published in the Last Week
To stay updated on the latest articles, we share every new article on our LinkedIn page.
👉 Chesterton’s Fence and the New Hire Trap by J Gibbens
👉 Why Engineers Can Say “This Is Wrong” and Designers Can’t by Kevin Muldoon
👉 Your design system has opinions. They’re just not being enforced by Murphy Trueman
👉 Sil Bormüller on Why Design Systems Are Becoming the Language of AI by Shane P Williams
👉 Systems Thinking Will Save Your Career by J Gibbens
👉 How I Use Claude Code Agent with VS Code as a Design System Designer by Dhika Endi Astowo
👉 UX Writing: Microcopy for Components That Guide and Engage Users by Omotola Oginni
👉 The ROI of Cohesion by J Gibbens
👉 A Brief History of Design Systems, Part 1 by Jim Gulsen
👉 Design System: Pages – A Practical Content & Structure Breakdown by Deeneesh
👉 Design Systems — An introduction for iOS developers by Jake Strickler
👉 Design Tokens in Webstudio: A Practical Implementation Guide by Roberto Moreno Celta
👉 Design Systems are not just libraries by Tina Singh
✨ Inspiration
Are you constantly searching for innovative ideas and fresh insights in design? Look no further! Here’s a curated list of intriguing content that has sparked our interest lately:
🔗 Transform Your Design System into an API
Discover how design systems are evolving into flexible APIs. This approach can revolutionize how teams collaborate and enhance scalability.🔗 Vibe Coding with MCP Design
Uncover the dynamics of Vibe Coding in design, offering a fresh perspective on creating cohesive and immersive user experiences.🔗 “Code Only” Props in Figma by Nathan Curtis
Explore the efficiency of using “code only” props in Figma, streamlining design processes by reducing redundancies.
🎗️ Support us:
If you find our content helpful, here’s how you can support us:
Forward this email to a friend and invite them to subscribe
Support our writers by visiting the Design Systems Collective website
📝 Closing Thoughts
One of the clearest signals of a maturing practice is when the questions change.
Less “what is a design system?” and more “where does this rule actually live?”
Less “does this scale?” and more “what breaks when it does?”
The work in this issue sits firmly in that territory. It’s practical, opinionated, and focused on the moments where systems stop being abstract ideas and start behaving like real infrastructure—subject to constraints, trade-offs, and the occasional hard decision.
If there’s a throughline worth keeping, it’s this: clarity compounds. When opinions are encoded, rationale is captured, and tools are expected to respect the system, the work gets quieter in the best possible way. Fewer debates. Fewer surprises. More energy spent on the problems that actually matter.
That’s rarely flashy progress, but it’s the kind that lasts.
Founding Editor, Design Systems Collective