Your design system just got a new consumer. It doesn't attend standups, it doesn't read Slack, and it definitely can't interpret what you meant by naming that token blue-3-alt-FINAL.
If you're feeding your design system into AI tools and wondering why the output feels off, the problem probably isn't the AI. It's your system.
What happened
There's a growing push to make design systems "AI-ready" — structured so that AI-powered tools can reliably parse and use them when generating prototypes, layouts, or UI suggestions. The core argument is disarmingly simple: the quality of what comes out depends on how well your system is organised going in.
This means clean naming conventions, thoroughly documented components, well-structured tokens, and guidelines that are machine-parseable — not just human-scannable. The messy shorthand that your team learned to navigate over three years? AI can't learn that from context. It takes your inconsistencies at face value and amplifies them.
At the same time, there's a parallel conversation happening in branding circles about how guidelines capture how a brand looks but often fail to encode how it behaves. Tone of voice, interaction personality, the way a brand responds in different contexts — these are rarely documented with any rigour.
Put these two threads together and you get an uncomfortable truth: most design systems are incomplete documentation of incomplete thinking. And AI is exposing that faster than any new hire ever could.
The bigger picture
We've spent years thinking about design systems as tools for human collaboration. A shared language between designers and developers. A way to onboard people faster and ship more consistently.
That framing still holds. But there's a new audience now, and it's far less forgiving.
When a junior designer encounters a token called surface-secondary-v2, they can ask someone what it means. They can look at how it's used in production. They can piece together intent from context. AI doesn't do that — or rather, when it tries, it guesses. And guesses at scale become drift.
I find that most design systems I've audited over the past year have the same structural problems: tokens with no semantic meaning, components documented with screenshots but no usage guidelines, and entire behavioural patterns — loading states, error handling, empty states — that live in tribal knowledge rather than the system itself.
This used to be a nuisance. Now it's a bottleneck.
If you're using AI to accelerate prototyping or generate UI, every gap in your system is a place where the output will diverge from your intent. The AI doesn't know your brand's personality. It doesn't know that your team never uses that particular shade of grey even though it's technically in the palette. It doesn't know that your button labels are always sentence case because someone decided that four years ago and never wrote it down.