Vibe Coding Has a Design System Problem

Everybody's talking about vibe coding like it's the future of building products. Describe what you want, AI generates the code, ship it. Feels like being Tony Stark talking to Jarvis while building the first Iron Man suit. But Jarvis worked because he was plugged into every spec, every schematic, and every standard Stark Industries ever produced. Your average vibe coding setup is more like talking to Jarvis after someone unplugged him from the workshop.

A PM generates a checkout flow using Cursor. An engineer spins up a settings page with Claude Code. A founder builds a landing page with Bolt over the weekend. Three people, three tools, three interfaces that all look almost right. Different button radii. Slightly off brand colors. Spacing that's close but not from your token library.

Multiply that across a product team and you've got drift moving at the speed of AI.

It's like a D&D campaign where every player is writing their own house rules. Individually, each set probably makes sense. But the moment they sit at the same table, nothing works together and the game falls apart. Not because anyone made a bad rule, but because nobody was playing from the same book.

The tools can actually connect to your design system. Figma MCP exists. Cursor and Claude Code can pull design context. But by default, none of that is wired up. Teams are probably vibe coding without giving the AI any awareness of their tokens, components, or accessibility requirements. It generates plausible UI, which is a very different thing from correct UI.

This is where design operations earn its seat. Making the system available where the code gets generated. MCP connections to your Figma libraries. Linting rules that catch drift before it ships. Treating your design system like infrastructure the AI depends on, not a reference doc it's never seen.

The speed is real. But speed without guardrails is just chaos with good typography. Or not.