On inheriting my mum's sentences, and watching them read as a machine's

Murphy Trueman explores why AI agents need explicit, up-to-date design system rules — and what this means for governance and documentation.

Design systems news is a weekly design systems editorial by PJ Onori.

The shape behind your tokens, screens, and pull requests

The Reach and the Recipe – What MCP and Skills are, and when to use each

How the graph keeps going up anyway

Authored change has outpaced the review model, and that breaks more than it looks.

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

Governance Without Gatekeeping – What a good contribution process is actually protecting

The practices exist. The discipline hasn't caught up

AGENTS.md, SKILL.md, DESIGN.md, and where each one fits

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

Reading a system you didn't build, and why the first 90 days look nothing like building

The most useful feedback your system has ever produced is on a thirty-day timer

Why every layer name, variant, and token reference is an architectural decision

How your design system vocabulary becomes AI context

Four open-source systems. One component. What the implementation choices actually say.

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

The technical preparation is well underway. The organisational questions it creates are a different problem entirely.

Lessons from Baldurs Gate 3 on contracts, governance, and judgment at the edges

On Figma's code-to-canvas announcement, and why smoother translation might be making the structural problem harder to fix

Patterns from Stripe, GitHub, and Twilio that fixed my component architecture

Read the book online for free.