The reader that can't ask

A design system’s most important reader is now one that can’t ask what you meant.

On October 15, at its first Config India in Bengaluru, Figma announced Specs: a Markdown document where a team writes down its design language, for its designers and for the AI agents now working in its files. A Markdown file is a modest feature. It’s also an admission that the component library was never enough.

What the library never said

A component library carries the mechanics: the button, the spacing scale, the token for red. It never carried the judgment. When red is allowed. What goes first on a crowded screen. Which of two correct layouts this product prefers, and why. Designers learned that in review, over years, from the person beside them.

In Design systems at scale I argued that a system can enforce mechanics and only influence judgment. People absorb influence. An agent reads what’s written down, and where nothing is written, it fills the gap with the average.

Rules with no adjectives

The rules that hold up are the ones a stranger can follow cold. They say what goes where, in what order, and leave no room for “make it feel premium.”

I’d hold any spec written for agents to that. “Clean, modern, friendly” tells an agent nothing it didn’t already assume. A rule like “red only for actions that can’t be undone” tells it exactly what to do, and gives a reviewer something to check.

Rules go stale

Writing judgment down is slow, and it’s never finished. Every rule you write becomes a rule people can argue with, and teams that never wrote anything down never had to have that argument. Some of them will find out they didn’t agree.

Written rules also go stale. A spec nobody updates is a confident wrong instruction, read by every agent on every run. It needs an owner and a queue like any other part of the system, and the same review the components get. A team starting one should begin with the comments it leaves most often in design review, rewritten as rules a stranger could check.