Learn
Five ways to think about design systems.
Foundations, Playbook, Frameworks, DesignOps — plus the AI-ready track. Pick the one that matches today’s question.
01 / The primitives
The constraints you lock first.
Color, type, spacing, motion, accessibility and voice, each calibrated so components compose without negotiation.
Color · type · space
The scales, with the reasoning that survives a rebrand.
Motion with a job
Duration, easing, and when stillness is correct.
A maturity model
Where your system is, and what moves it to the next stage.
02 / How to build it
Zero to operating, in ninety days.
Eight chapters sequenced from Day 1 to Day 90, with a Migrate track for products already in flight.
Days 1–7 · Orient
The smallest set of decisions to lock in week one.
Days 8–60 · Build and ship
The spine first, then composition under real product work.
Days 61–90 · Operate
The handoff from building the system to running it.
03 / How to organize it
The org chart decides what ships.
Centralized, federated, hybrid, distributed — the topology sets what your system can deliver before any code does.
Four topologies
And the consistency–autonomy axis they trade along.
Implementation timing
When to formalize, and what breaks if you wait.
Governance shapes
Contribution models that survive contact with deadlines.
04 / How to run it
The layer that keeps it alive.
Workflows, adoption, tooling, measurement: the operating tracks that decide whether the system gets used or ignored.
The adoption funnel
Where systems stall in the funnel, and how to restart each stage.
Workflows and RFCs
Release cycles that keep product teams unblocked.
Metrics that matter
Measurement beyond a component-usage vanity number.
05 / How to ship it for agents
Make it legible to agents.
Tokens, components and docs that Cursor, Claude Code and v0 can read, plus the independent index that benchmarks the field.
The structure guide
Tokens, naming and docs, in the order agents resolve them.
MCP and registries
The queryable surface a docs site can't provide.
The Agent-Ready Index
37 public systems scored on five signals, evidence attached.
Onramps
Arrive with a question, leave with a page.
- “What does a real spacing scale look like?”/foundations
- “What's the smallest set of decisions to lock in week one?”/playbook
- “We have three UI kits and a rebrand — not a blank slate.”/playbook/migrate
- “Centralized or federated — when does the model break?”/frameworks
- “We built it, no one uses it. Now what?”/designops/adoption
- “What number justifies this to my director?”/tools/roi-calculator
Featured
If you only read three things, read these.
Motion has a job. or it has no business shipping.
The four jobs of motion, the motion budget, choreography, and reduced-motion accessibility.
Read itBuild a design system in ninety days.
Eight chapters mapped to a 90-day path, with three time-budget entry points.
Read itWhy your design system isn't being adopted.
Six reasons it stalls, the funnel that shows where, four moves that work.
Read itThe frame is here. the proof is in the gallery.
120 real systems with engineering-facet filters, and the AI-ready hub for the 2026 wedge — MCP, W3C Design Tokens, components agents can use.