Give v0 a written goal and your design system, and send its output to engineers as a GitHub branch, and its prototypes become work a team can use. The steps run in order: brief v0 before work, keep chats short during work, and review the branch before it merges.
When you need this
- Product managers and designers build v0 prototypes, but each one looks and behaves differently.
- Long chats drift, later prompts undo earlier decisions, and credits go to repairs.
- Engineers receive a v0 link or a ZIP and rebuild the screens from scratch.
- Nobody can say what a given prototype was meant to settle.
Steps
Before work: state what the prototype must prove
Can the person prompting v0 name the decision this prototype supports?
What good looks likeA one-line goal and the screens or flows in scope, written before the first prompt. For multi-feature work, Vercel's prompting guide says to plan first, for example by asking v0 for a PRD (product requirements document), then to build the core. One product manager built a v0 prototype only to win support for an internal pitch. Once a UX designer joined, the team threw out the v0 design and code, and the product manager says that is how the process should work.
Before work: load the design system and instructions
Does v0 build with your components and tokens, or with its defaults?
What good looks likeYour team's design system, imported through Design Systems 2.0, which saves it as a skill in the team scope so chats use real components, props, and tokens. Private packages need a shared NPM_TOKEN or NPM_RC. Saved Instructions, such as the built-in Plan Mode preset that asks for approval before code changes, carry team rules across chats. Neon's designers copy style values from Figma Dev Mode without relying on the Figma import, and get better results from prompts that spell out layout and behavior.
During work: size the model to the task
Is each prompt running on a model priced for the work?
What good looks likeBuilders use v0 Mini for small edits and v0 Pro or Max for complex generation. Per million tokens, Mini costs US$0.20 input and US$1.20 output, Pro US$2 and US$10, Max US$5 and US$25, and Max Fast US$10 and US$50. Chat history, source files, and Vercel context count as input on every message, so a long chat costs more per prompt than a fresh one.
During work: fork long chats
When a chat starts drifting, does the builder start a new branch of work or keep prompting?
What good looks likeOne new chat or duplicated branch for each separate idea, and a restore from version history when a change goes wrong. Restoring creates a new latest version. All 11 public accounts GILD read that discuss regressions complain about them. One builder spent more than US$30 of credits on a bug v0 had caused, then fixed it in Cursor in 20 minutes.
Before merge: hand off a reviewable branch
Does engineering receive the prototype as reviewable code in your repository?
What good looks likeEach chat connected to GitHub, where v0 commits to a working branch, opens a pull request against the base branch, and never pushes to main. One developer took a v0 design built on stand-in data into Cursor for the API calls and finished in two days. Another edited the code in GitHub, and v0's Pull button then failed to bring those edits back into the chat.
Questions for your team
- Which prototypes are meant to be thrown away, and which are expected to become production code?
- Is our design system imported as a team skill, and who keeps it current?
- Which model do builders default to, and do they know what a long chat costs per message?
- Who on the engineering side reviews v0 branches, and how fast?
Red flags
- Prototypes built on v0's default styling and then rebuilt in the team's design system by hand.
- One long chat per project, with repairs costing more than new work.
- Engineers receiving v0 output as a share link or ZIP with no branch behind it.
- No written goal for a prototype before the first prompt.
Products in this piece
Sources
- Official documentation
- 8
- Public source
- 5
- v0 docs: Text Prompting
- v0 docs: Instructions
- v0 docs: Design Systems 2.0
- v0 pricing
- v0 docs: Pricing
- v0 docs: Versions
- v0 docs: GitHub
- v0 docs: Import from GitHub
- ashryan on Hacker News: a v0 prototype for an internal pitch, then a designer's rebuild (Jan 22, 2025)
- Lachezar Petkov, Neon blog: Using v0 for UI design exploration (May 13, 2025)
- rockoswald in r/v0_: moving a v0 project to Cursor through GitHub (Feb 8, 2026)
- wazzaps on Hacker News: v0 for the first design, Cursor for the rest, in two days (Jun 26, 2025)
- rockoswald in r/v0_: the Pull button failing after edits made in GitHub (Apr 1, 2026)