06 Aug 2026
Design systems are dead. Long live the file.
Everywhere right now, designers are generating design systems from a prompt. Brand guidelines, a hundred pages, neatly structured, done in minutes. No fringe phenomenon: among teams using AI in their design system, 60 percent use it to generate documentation — the most common application right after code.
You can turn up your nose at that. I find it honest. Design system teams are chronically understaffed — 61 percent say they lack people; scarce resources are their most-cited problem. Of course they automate the work that feels most like a chore first: the document you make to have it. Not to use it.
But then you have to follow the thought all the way through. If a machine can write your most important brand document in minutes, it was never your most important brand document. It was decoration with a table of contents. The numbers say the same thing, just more politely:
A 47-point gap: documentation that exists, but doesn't carry
Outdated on arrival
And even the best documentation shipped with an expiry date: the day it was published. A brand doesn't hold still. A dark mode the manual has never heard of. A channel that didn't exist when it went to print. A word that sounds different since last summer. A competitor in a new suit. An economy in which the glossy tone suddenly reads as cynical. Everything about a brand keeps moving — only its rulebook went to print. The PDF is the tombstone, and the date is already on it.
The bookkeeping of design
Anyone who has ever worked inside a system knows the moment: the new design needs something that doesn't exist yet. A component, a state, a color for a case nobody saw coming. Sometimes the foundation itself starts to wobble. And then the real work begins — patching, back-porting, filing, aligning, republishing. The bookkeeping of design. It has cost smart people weeks and never bought the brand a single better appearance.
That work is exactly what disappears. The decision lands in the file the moment it's made. You see that it works, and you can point to it. Nobody back-ports anymore.
Long live the file
Hence the thesis: the design system as a document is dead. Not because nobody needs systems anymore — but because the living form already exists. The design system that carries its weight is a file in the project folder. Versioned like the code next to it. Read by humans and machines alike. Touched with every decision, corrected with every tenth. It never gets published, because it's never finished. It simply grows along.
This site works exactly that way. Its design system is a markdown file in the same folder as the code. Every change has to answer to it — and when a good decision contradicts it, the file changes. A working document in the literal sense.
The gap is the job
And that's the good news. Because two numbers are still missing:
A 46-point gap: this is exactly where taste works
The gap between those two numbers isn't a problem. It's a job description. It still takes someone with taste to decide what belongs in the file and what gets thrown out — someone who orchestrates the whole thing while it moves. You just don't have to produce the document yourself anymore. Or show it to anyone.
