The Spotify Encore team found that AI agents were bypassing their design system entirely. Developers went to Cursor first, got non-Encore output, and shipped it. A system built over years became invisible to the fastest-growing class of its users.
Google Labs hit the same wall from the other direction. They open-sourced DESIGN.md in April 2026 because, as the team described it, "every time a designer hands a project to a coding agent, the same problem appears. The agent builds something that looks close but not right. Wrong shade of blue, a font that doesn't match, spacing pulled from thin air." The root cause: agents have no reliable place to read the design system.
The most common fix has been to add a machine-readable layer on top. Google's DESIGN.md gives agents a structured understanding of tokens and brand identities. Solid engineering from a credible team. But also the localization mistake, replayed.
The same structural error
In the 2000s, companies built products in English, shipped them, then painted translations on top. The information architecture assumed English word lengths. The date formats assumed American conventions.
Localization teams worked heroically. The products fought them because the center of gravity was elsewhere. The structure had already decided who the default user was.
The teams adding agent-readable metadata to human-centered design systems are doing the equivalent. The conference analysis from Into Design Systems lays out the gap: agents "know about components but break every foundation: spacing is wrong, typography doesn't match, colors are off-brand. Components are technically correct but the page looks nothing like the product." A metadata file describing the system is not the same as a system structured to be described.
The MCP pattern shows how this breaks down in practice. MCP is on-demand. It returns only what the prompt asks for. A prompt that says "build me a card" gets card and button metadata. Spacing, typography, and colors go unrequested, so MCP does not send them.
The LLM fills those gaps from its training corpus. The metadata covers the named parts. Everything beneath them reverts to the model's default.
The membrane leaks what is actually inside
Brand works like a membrane: the inside of an organization leaks outward. The actual structure, not the documentation about it. You cannot cosmetically override what the inside produces. Branding from the outside in is decoration, and it reverts.
If the design system's internal structure was built for human eyes, that is what leaks through to agents. A JSON manifest on top does not change the architecture beneath it. The agent reads the manifest, encounters everything the manifest does not cover, and falls back to its training data. What leaks through is the truth of the structure: this system was never built for this kind of reader.
Spotify's response was structural. They rebuilt Encore into three independent layers: foundation (tokens and primitives), style (visual appearance), and behavior (interaction logic). This creates what they call "smaller context bubbles" for AI. The result: 220,000+ shared style uses with 50% year-over-year growth and 93% developer satisfaction. They changed the inside.
Meta's Astryx was built from the ground up to be AI-operable rather than retrofitted. Developed over eight years inside Meta's infrastructure, the system powers roughly 13,000 internal applications. The manifest works because it describes a system that was structured for machine readers from the start. The inside and the surface say the same thing.
Both cases point the same direction. Agent legibility holds up when it is architectural. It falls apart when it is cosmetic.
The pressure is already here
NN/G puts it plainly: "AI agents are now interacting with the same digital interfaces we design for people, navigating websites, filling out forms, comparing options, and executing transactions." These agents are already users of your product. Jakob Nielsen goes further, predicting autonomous agents will make traditional UI design obsolete as users stop visiting websites in favor of interacting solely through their agent.
You do not have to buy Nielsen's timeline to feel the pressure. If agents are already consuming your product, your design system's membrane is already leaking. What comes through is whether agent legibility was structural or cosmetic.
The localization teams of 2010 learned this the hard way. You cannot translate a house by repainting the walls. The design systems that survive the next three years will be the ones rebuilt for a new kind of reader. The teams that ship a DESIGN.md and call it done will be rewriting it in two years. The teams that restructure, the way Spotify and Meta did, will not.