How to prompt v0
By Steven Van ·
Vercel's new guide frames v0 prompts around product surface, context of use, and constraints, backed by three head-to-head generation tests.
Vercel published a prompting guide for v0 built around a three-part framework the team says came from building hundreds of applications and watching v0's power users. Good prompts, it says, consistently produce faster generation (30-40% faster, with less unnecessary code and fewer credits spent), smarter UX decisions, and cleaner code.
The framework asks for three inputs in every prompt:
- Product surface: the actual components, data, and actions, not a generic description like "a dashboard".
- Context of use: who is using it, in what moment, and what decision they're trying to make.
- Constraints & taste: platform or device, visual tone, layout, colour system, and any accessibility or responsiveness needs.
The guide backs this with three side-by-side tests. Adding context of use to an e-commerce prompt took 26 seconds longer to generate but produced a fully functional, mobile-responsive site, versus a version with a non-functional search and cart that would have needed 1-2 more prompts to fix. A specific product-surface prompt for a profile page generated in 1m 19s at 443 lines versus 1m 38s at 595 lines for a vague one. Detailed constraints on a support dashboard took 10 seconds longer but produced 110 fewer lines and a genuinely mobile-first layout rather than a shrunk desktop one.
For iterating after generation, the guide recommends prompting for logic and structural changes, and using Design Mode, where you select an element visually, for quick visual tweaks like colour, spacing, or typography.
