Hi, @pierrelandoin-icypea!

I asked v0 for you 😃 Here's the response: https://v0.dev/chat/DKx7ujNuJzX

Pulling out specific points:

v0 is designed to generate components based on natural language descriptions and user requirements. - Storybook, on the other hand, is a tool for developing and showcasing UI components in isolation.

Importing Storybook components might restrict v0's flexibility in generating diverse and customized components tailored to specific user needs.

Keeping Storybook components in sync with v0's generated components could introduce additional complexity and maintenance challenges.

Let us know what you help up doing!

Thanks for the answer! Actually, when I use V0 alone, it creates some components that are not very well styled. I was wondering if V0 could try to stay as close as possible from my already existing components (stored in Storybook). Could I use Storybook as a "guideline" to follow for the creation of new pages using these existing components?

Why not give it a go and let us know how you get on? 😄

"restrict v0’s flexibility" is what I want when planning to upgrade account to use 'project' feature. Because I want it using my component, that was customized base on shadcn component.

I want my designer/BA to use v0 with the styled UI from my components, to setup what ever layout they want. Because I am not developing a single project, and all the UI should be the same to avoid confused from user.