StackBlitz builds a design system agent in Bolt on Claude Agent SDK to generate production-ready, on-brand prototypes
Companies lack a single, unified design system: typography lives in Google Docs, components are scattered across Figma files, Storybook instances, and GitHub repositories, and spacing guidelines may exist only in an engineer's head. Without access to a company's actual design language, AI-generated prototypes look generic and end up as throwaways that engineers must rewrite entirely before anything can ship.
The design system agent generates a consolidated design system in an autonomous run averaging 53 minutes.
From that point, any team member can produce on-brand prototypes in roughly five minutes, with code that can go to production with minimal rework. StackBlitz sees roughly 90% cache efficiency on the Agent SDK, and more than 10,000 users have already uploaded their own design systems to Bolt.
Show all 6 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
The design system agent generates a consolidated design system in an autonomous run averaging 53 minutes.
What tools did this team use?
Bolt, Claude Agent SDK, Claude Opus 4.7, Storybook, GitHub, Figma, npm.
What results were reported?
Research phase duration (range): 40 minutes to an hour and a half; Research phase duration (average): averaging around 53 minutes; cache efficiency on Agent SDK: roughly 90%; users who uploaded design systems to Bolt: More than 10,000 (source-reported, not independently verified).
How is this back office ops AI workflow structured?
Design sources submitted → Multi-source ingestion and analysis → Sustained reasoning with Claude Opus 4.7 → Parallel sub-agent processing → Design system library built in Bolt → User prompts prototype generation → On-brand code generation → Agent self-review loop → Production-ready prototype delivered.