AI didn't break your design system. It showed you it was never real.

Something we keep running into, and I want to know if it's just us.

Before AI, a design system could be half-fiction and nobody noticed. The Figma file said one thing, the code said another, and two people who happened to remember the real value quietly absorbed the gap.

Then you point Cursor or Claude at the repo and ask for a settings page. It ships in ninety seconds. It also ships a blue that exists nowhere in your tokens, a 13px label, and a card radius that is close to yours but not yours. That isn't really a hallucination. The model found no system to read, so it invented a reasonable one.

The part that surprised us: this happens to teams who genuinely have a design system. Theirs just isn't machine readable. It's a library of components with names, not a set of rules with constraints. Gartner's 2026 UX Hype Cycle lands on the same shift, from static component libraries toward rule based systems that agents can actually interpret.

Three questions I'd love real answers to.

One: when your agent goes off system, do you catch it in review, in QA, or three sprints later when a designer opens the app?

Two: has anyone found a setup that actually holds? Cursor rules, MCP, a linter, a CI check, something else entirely.

Three, the honest one: do your designers and developers agree today on what the source of truth even is?

We built Flash on the assumption that the answer to the third one is usually no, and that most of the drift downstream starts right there. Genuinely curious whether that matches what you see, or whether we've over indexed on it.