v0 by Vercel
Full stack vibe coding platform. Created by Vercel.
4.8•57 reviews•2.4K followers
Full stack vibe coding platform. Created by Vercel.
4.8•57 reviews•2.4K followers
Your collaborative AI assistant to design, iterate, and scale full-stack applications for the web.
This is the 5th launch from v0 by Vercel. View more
v0 Design Systems 2.0
Launching today
v0 Design Systems 2.0 is here. You can now import your system from the sources your team already uses: GitHub repos, public and private npm packages, Storybook and docs, Figma frames, screenshots, ZIPs, and real apps. v0 learns how your design system is actually used and creates a playground with your components and tokens. Preview the result, keep iterating in chat, and save it when it's ready.
Launch Team
Lovable
bolt.new
Replit
Tabstack by Mozilla
@v0 by Vercel Design Systems 2.0 is here.
Import your design system from @GitHub , @Figma, and more. Build with your real components, colors, fonts, and patterns.
Get started: v0.app
Importing from GitHub, npm and Storybook is the right set of sources. The question I'd want answered is how strictly it binds to the typed component API after import. When we fed our own component library into a codegen agent, the failures weren't wrong-component picks, they were invented prop names that looked plausible (variant="subtle" when only "soft" shipped) and reaching for deprecated variants Storybook still had stories for. Does 2.0 treat the imported system as a hard schema, or as reference the model can drift from?