v0 just shipped Design Systems 2.0, a significant rethink of how the AI builder handles custom component libraries. Instead of asking you to manually re-explain your design system in every prompt, v0 now learns it once from the sources your team already maintains, and applies it automatically across every future chat.
The previous approach required teams to either build a shadcn/ui-compatible registry or paste component code into prompts repeatedly. v0 was tightly coupled to shadcn/ui, and working with any other design system required constant manual guidance. Design Systems 2.0 is a direct answer to that friction.
What gets imported, and from where
Design Systems 2.0 lets you teach v0 your design system once, so team chats can build with your real components, tokens, and conventions. A design system is saved as a team-shared skill , a focused set of instructions v0 keeps attached to your team's workspace and pulls in when relevant.
The import form accepts a wide range of sources:
- GitHub repositories , the design system source or any app that consumes it
- Public and private npm packages , including private registries via
NPM_TOKEN - Storybook and documentation sites , links to component docs and usage guidelines
- Figma frames or nodes , visual references for composition, density, and typography
- Attachments , screenshots, ZIPs, exported packages, or
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves