Shrimpton Agency

It's 11pm, launch is Monday, and you've just handed your gorgeous Figma file to an AI agent. Under the hood it's Frame 1268, Group 5 copy copy, a button that's three rectangles and a prayer, eleven shades of almost-black nobody asked for, and a swatch called "Blue (new) FINAL v2." Someone types "implement this design," the agent reads every single one of those things as gospel, and an hour later you've got a codebase with gray-17, five slightly different primary buttons and a brand color you've never seen in your life.

Then everyone blames the AI.

Wrong suspect.

The bot doesn't know it's wrong

Here's the thing nobody tells designers about AI agents. They thrive on clear, organized information, and they have zero instinct for whether that information is right for your brand. Give them something wrong and they don't question it. They take it and roll with it.

An unnamed style isn't a mistake to an agent. It's a new style. That random hex you eyedropped off a mood board at 2am isn't a stray. It's a real color now, it gets a name, and it starts showing up in places you really don't want it.

AI agents don't know what's wrong. They only know what's there.

Even Figma says so, in its guide to MCP for designers: its MCP server can't "guarantee accurate code if your design system is messy or inconsistent." Anthropic's own engineers say the same thing about agents in general: instructions fail when they're vague or falsely assume shared context.

Figma is literally spelling it out for you

You don't have to take my word for it. Read the manual.

Figma's developer docs on structuring your file for better code read like a brand-guidelines refresher from 1998. Use components for anything that repeats. Use variables for color, spacing, corner radius and typography "so your agent can reference your tokens instead of hardcoded values." Rename the default junk, Frame1268 and Group5, to things like CardContainer and CTA_Button. Without Code Connect, "your agent has to guess which code component matches."

Their help article on prepping your design system for the Figma agent is even blunter. A component called Card/Product/Default is "immediately interpretable; a component called Frame 42 copy is not." Default layer names like Group 7 or Rectangle 3 "give the agent nothing to work with." And my favorite: "A variable called blue-500 tells agents nothing about when to apply it; color/brand/primary does."

That's not an AI feature. That's a style sheet. With a class naming system. Exactly what good brand designers have been nagging everyone about since before "the cloud" was a thing.

The receipts

When Coinbase's design system team tested coding agents with and without Code Connect, their technical lead said agents "had been notorious for hallucinating illustration and icon names. After completing our adoption of Code Connect, that problem disappeared overnight." Same design, same prompt, same model: token use down 11.5%, time to implementation down 22.3%, cost down 22.5%. His warning for anyone skipping it: "The agent can go wild in how it interprets the design."

Go wild. On your brand. At scale.

Meanwhile, Figma's AI report found 68% of developers use AI to write code, but only 32% of designers and developers trust the output. Figma's diagnosis: "context is everything."

And the people who actually maintain design systems? In zeroheight's Design Systems Report 2026, only 7% say their system is fully adopted across all teams, and only 54% have tokens set up across design tools, code and documentation. One respondent summed up the AI tooling gap better than any keynote: "none of these AIs support a design system out of the box without hallucinating."

So the system exists, half-finished, half-used, and we're pointing robots at it and acting surprised.

It's not just Figma

The same rule applies to everything you feed an agent. Sitemaps. Brand guidelines. Content models. Instructions. Folder structures. File names.

Anthropic points out that "folder hierarchies, naming conventions, and timestamps all provide important signals that help both humans and agents understand how and when to utilize information." A sitemap with three "About" pages and a folder called final_FINAL_use-this-one isn't a quirky creative mess. It's three About pages and a set of instructions the bot will follow straight off a cliff.

Organization isn't admin. It's the brief.

Old-school brand discipline is the new AI skill

This is the bit that should make every designer feel quite smug.

The skill that makes AI agents brilliant isn't prompting. It's the boring, traditional, slightly nerdy craft of brand organization: a proper style sheet, every style applied to the designs, a naming system that actually means something, a palette with no orphans, components instead of detached copies.

Figma has even built Check designs to hunt down hard-coded colors, text styles, spacing and detached components, and it doesn't use AI at all. Its docs say it "works best with a published, variables-based design system." Of course it does. A linter can't check you against a system you never built, and neither can an agent.

"Name it, or the bot will."

Do the organizing first and something great happens. Agents stop inventing and start iterating. They pull your real tokens, reuse your real components, and spin out variations that actually look like your brand, at a speed that frankly is a bit annoying. The design gets better because the foundation was good to begin with.

AI doesn't replace a strong design. It amplifies whatever you give it, the brilliant and the janky alike.

So designers, the robots aren't coming for your job. They're coming for your Figma file.

Make it worth copying.