Murphy Trueman

I learned about the principle of least privilege a few months ago, while reading about AI agent security.

I finished writing an article recently.

GitClear published a report this year that got me thinking about how we measure design system adoption.

Design systems have spent years borrowing from how software gets built.

Twelve months ago I argued in Your next design system user is an agent that the next user of your design system would be an agent.

What changed, coming back to design after a stint in front-end development, was Figma.

A year ago I wrote a piece called your next design system user is an agent.

Most design system teams already know they should version their components, communicate deprecation in advance, and measure system health.

Three file formats have moved from proposal to working convention in the design systems conversation in roughly twelve months.

In March, Ian Guisard from Uber's design systems team published a write-up of uSpec, an agentic system he built to automate component documentation.

I was on Elyse Holladay's podcast On Theme earlier this week.

Design system teams are governing AI output.

Most of what's written about design systems assumes you're building one.

Design systems teams have always been short on honest data about their own work.

Every component you build in Figma is a collection of decisions.

Every time an engineer opens Cursor or Claude Code and starts building against your design system, the AI is already reading.

The way design systems get consumed is changing.