Murphy Trueman

@murphytrueman.com

⌘ Design systems. Product. Writing something, somewhere. http://murphytrueman.com

The question we hear most from design system teams right now is some version of: are we ready for this? This week's newsletter is about what being ready actually looks like, and why it has a lot less to do with the state of your system than you might expect. www.baselinedesign.com/posts/what-b...

What Being Ready Actually Means - Baseline Design

What Being Ready Actually Means – And why it has less to do with your system's polish than you might think

baselinedesign.com

"Teams that take #designsystems best practices seriously treat documentation as infrastructure, not a launch deliverable you forget about." In this post, @murphytrueman.com explores why docs often become a bottleneck and how to build maintenance into the workflow. Read it on @zeroheight.com:

Why your design system documentation goes stale (and how to fix it) - zeroheight

Murphy Trueman explains how to document a design system, why docs go stale, and practical steps to keep documentation current, findable, and useful.

zeroheight.com

The 5th edition of the Design Systems Report is here 📔 Design systems are now critical infrastructure—but they’re getting harder to sustain. Buy-in is dropping. Teams are stretched. Adoption is still the biggest challenge. Explore the report → hubs.li/Q04774jK0

AI tooling for design systems has matured. The operational work hasn't kept up. Token audits. Deprecation plans. Drift detection. Stakeholder briefs. I tidied up the Claude Code skills I've used for that work, and put them somewhere public. designsystemops.com

Design System Ops – Claude Code Skills for Design Systems Practitioners

The first Claude Code skill pack built for the people who run design systems – not just the people who use them.

designsystemops.com