Bolt.new's Design System Agents assume you already have one
By The WAALEE Team · · 4 min read
Two more platforms shipped a "make the agent build on your design system, not its own" feature this cycle: Bolt.new's Design System Agents and Replit's Bring Your Own Design System import. Read past the announcement copy and both make the same assumption Lovable, Webflow, and v0 already made earlier this year: a clean design system to feed the agent already exists somewhere. Neither one goes and gets it off a site that's live today but was never turned into a token file.
What Bolt.new's Design System Agents actually ingest
Per Bolt's own announcement, Design System Agents ingest source files that define your company's visual identity: UI components straight from your codebase, npm packages, Storybook sites, documented component specs, logos, iconography, proprietary fonts, and brand guidelines. Once it has those, the agent builds with "the exact same bin of pre-molded Lego bricks" your engineering team already uses, instead of inventing a plausible-looking button or card from training data. That's a real fix for a real cost Bolt calls the "translation tax": the weeks engineers spend rebuilding an AI prototype to match production before it can actually ship.
The catch: it assumes the bin of bricks already exists
Notice what's on that source list. A coded component library, a live Storybook, a written brand guideline doc, real font files, an actual npm package. Every one of those is something a team has to have already organized and exported. If your "design system" is really just a live marketing site nobody ever componentized, or a Webflow or Squarespace build with hex codes typed into the color picker one page at a time, there's no bin of bricks yet to hand the agent. Bolt's agent is genuinely good at reusing a system that exists. It has no feature for authoring one it was never given.
Replit's version has the same shape, plus two more gates
Replit shipped something structurally similar on nearly the same beat: Bring Your Own Design System, which lets you import a design system from Figma, or upload a package containing your design tokens and rules, and apply it to new Agent-built apps. Two details in the announcement are worth reading closely. First, it's explicitly "Beta for Enterprise Customers" only. Second, quoted directly: "This release supports all new apps built with Replit, with support for previously built apps on the way." So even inside Replit, an app you already built can't retroactively adopt the imported system yet. And outside Replit, a live site's real colors and type still have to be extracted and turned into a Figma file or token package before the import step even starts.
- Bolt's Design System Agents need your components, brand guidelines, and fonts already assembled as source files, not read off a live URL.
- Replit's import needs a Figma file with real variables, or a token package already built, and it's gated to Enterprise beta, new apps only.
- Neither one has a "paste a URL" step, because neither one is trying to answer where the tokens come from in the first place.
- Both fixes are aimed downstream of that question: building faithfully once a system exists, not producing the system itself.
The step before either agent can help
None of this is a gap in the engineering. Reusing real components instead of guessing at new ones is a genuine, overdue fix, and two serious platforms shipping it within weeks of each other says something about where the actual bottleneck moved this year. It moved to sourcing. If your brand's real colors, type, and spacing only live on a rendered page today, built years ago, by an agency, in a stack neither importer reads, someone still has to go get those values before "bring your own design system" means anything.
The fastest way there is the same move for either platform: extract the computed colors, type scale, spacing, and radius straight off the live page where your brand actually renders, then hand the resulting token file to Bolt as one more brand-guideline source, or upload it as the token package Replit's importer is waiting for. That turns "bring your own" from a requirement you can't meet into a five-minute step.
Two agents built to reuse a design system faithfully, and where the tokens have to come from first:
- Bolt.new Design System Agents: Reads your components, npm packages, Storybook, brand guidelines, and fonts once they're organized as source files. No step that reads a live, un-componentized site.
- Replit: Bring Your Own Design System: Imports from Figma or an uploaded token package, Enterprise beta, new apps only. Assumes the Figma file or package already has real values in it.
- WAALEE: Paste a live URL and get the real colors, type scale, spacing, and radius back as W3C tokens in seconds, ready to feed either agent as the source file it's waiting for.
None of this is a knock on Bolt or Replit. Reusing a real design system faithfully, instead of an agent's own defaults, is a genuine upgrade, and shipping it twice in the same month says the market agrees on where the pain was. The gap is just upstream of both releases: an agent that reuses your system perfectly still needs somebody, or something, to hand it the real one first.