From the comical wizard prompts of 2024 to the heavy-lifting reality of Figma MCP, Davy and PJ chart the compressed timeline of design system and canvas automation.

Why do we build in public when corporate nature tells us to hoard our work? Davy and PJ break down the unglamorous reality of sharing open-source tools, micro-contributions, and why 90s music is a hill worth dying on.

We hit the Centennial! In our 100th episode, Davy and PJ look back on 4 years of our design systems chatter, before diving deep into the future of design systems: a community-driven, machine-readable schema that moves us past the "Figma-as-Source-of-Truth" era.

Davy talks about trading a week of manual Figma updates for a "code-to-canvas" workflow that gets us "close enough" while PJ talks about running multiple worker-based agents to do production and qa work in tandem. Are these burner tasks?

Davy and PJ dive into the Zeroheight's 2026 Design Systems Survey to figure out why 61% of teams are drowning in work while a third of them still have "no plans" to automate—plus, Davy forces PJ to listen to some truly questionable AI-generated design jokes.

Davy and PJ dive into the future of design tokens, exploring how to "tokenize everything" from complex color transformations (OKLCH) to utility tokens for motion and content strings.

Davy and PJ discuss why the future of design workflow isn't just better handoff—it’s starting with the code itself.

Davy and PJ discuss the "liability" of stale documentation and why AI still needs human oversight. They explore using Figma’s API to automate visual updates and kill the "pain in the butt" of manual maintenance.

Building vs. Inheriting: Davy and PJ discuss the performance cost of design system dependencies. Learn how to choose the right framework without bloating your system or losing control of your architecture.

Davy and PJ celebrate four years of Design System Office Hours by looking ahead at the shifting landscape of 2026. They explore how interoperability, open-source tooling, and AI-driven documentation being major themes to uplevel design system practices.

Davy and PJ tackle the notorious difficulty of naming in design systems, advocating for human-readable, descriptive language over "cute" metaphors and discussing how AI is making file cleanliness more critical than ever.