Send us feedback or episode suggestions.
Design systems were built to close the gap between a brand and the products that express it. Now an agent sits in that gap, and it arrives at every task like a new hire who has never seen the system. In this episode of Patterns, Chris Strahl talks with Mike Kamminga, CEO and founder of Tokens Studio, about what that changes for tokens, components, and the context teams hand to their agents.
Mike describes a design system as component definitions, design tokens, and translation rules, then explains why agents lean on what they learned in training, like Tailwind, over what a team intends. The conversation covers source of truth, guardrails built for slower release cycles, design.md, and what Mike calls an experience system.
We'll explore:
- Why an agent is "the new guy on the job" every time, and what that means for how a design system is documented and delivered
- Why models lean on what they saw in training, and what it takes to steer an agent toward something different
- Why Mike has yet to hear a good argument for code or design alone being the source of truth, and why a design system is a prescriptive ideal state
- Whether guardrails built for slow release cycles still pay off when an agent can fix a mistake in minutes
- Why a five-minute style guide is a good start for prototypes, and why Mike calls the next step an experience system
