These 40 prompts are written for v0 by Vercel, the AI builder that turns a natural-language message into production-ready Next.js (App Router), Tailwind, and shadcn/ui code you can preview and deploy. Every prompt uses v0's real three-part structure: the product surface (the exact components, data, and actions), the context of use (who uses it and to decide what), and constraints and taste (platform, tone, layout, and exact design tokens).

Fill the [bracketed placeholders] with your own product, data, and colors. Because every generation burns credits, a tight prompt is the cheapest prompt. Copy the ones you need, and keep this page as your v0 hub. For the reasoning behind each pattern, see how to prompt v0 for UI; for focused sets, jump to v0 prompts for landing pages or v0 prompts for dashboards.

Advertisement

Landing & marketing pages

Landing pages are v0's fastest win: describe the exact sections, the single conversion goal, and your design tokens, and let it emit responsive Next.js and Tailwind. Name the shadcn/ui components you want so the output matches your system.

1. SaaS landing page hero with product surface

Build a landing-page hero for [product name], a [one-line description]. Product surface: an eyebrow tag, an H1 headline, a one-sentence subhead, a primary CTA ([Start free]) and a secondary ghost CTA ([Book a demo]), a trust line of 5 customer logos, and a framed product screenshot on the right. Used by [first-time visitors from a paid ad] to decide whether to sign up in under 10 seconds. Constraints: Next.js App Router, Tailwind, shadcn/ui Button. Desktop-first, responsive down to 360px. Design tokens: primary #4F46E5, background #FFFFFF, text #0F172A, radius 12px, font Inter, generous spacing. Do not add a nav bar or footer yet.

Why it works: the exact section list plus one conversion goal keeps v0 from padding the hero with filler.

2. Pricing section with three tiers

Build a pricing section with three plans: [Starter $0], [Pro $20/mo], [Team $60/mo]. Product surface: three shadcn/ui Card columns, a feature list with checkmarks per plan, a "Most popular" badge on Pro, a monthly/annual toggle that updates prices, and a CTA button per card. Used by [an evaluator comparing plans] to pick the right tier. Constraints: Next.js, Tailwind, shadcn/ui Card, Badge, Switch. Highlight Pro with the primary color border. Design tokens: primary #4F46E5, muted #64748B, radius 12px. Responsive: stack to one column under 768px.

Best for: a conversion-critical section where the middle tier must visually win.

3. Feature grid with icons

Build a feature section: a centered heading, a subhead, and a responsive grid of 6 features. Each feature: a lucide icon in a tinted rounded square, a short title, and two lines of copy. Features: [list your 6 features and one-line benefits]. Used by [a visitor skimming for the one feature they need]. Constraints: Next.js, Tailwind, lucide-react icons, shadcn/ui styling. Grid is 3 columns on desktop, 2 on tablet, 1 on mobile. Design tokens: icon tint from primary #4F46E5 at 10% opacity, radius 10px, text #0F172A. Keep copy tight, no lorem ipsum.

Why it works: forcing real feature copy over lorem ipsum makes the block usable on the first pass.

4. Testimonial and logo wall

Build a social-proof section: a grayscale row of 6 customer logos, then a 3-column grid of testimonial cards. Each card: a quote, an avatar, a name, and a role/company. Use [these 3 quotes or generate realistic placeholders]. Used by [a skeptical buyer looking for proof it works]. Constraints: Next.js, Tailwind, shadcn/ui Card and Avatar. Design tokens: card background #F8FAFC, radius 12px, subtle 1px border #E2E8F0. Logos are monochrome and pop to color on hover. Responsive: 1 column of testimonials on mobile.

Best for: adding credibility below the hero without a heavy redesign.

5. Waitlist landing page with capture

Build a single-screen waitlist landing page for [product]. Product surface: centered logo, an H1, a one-line value prop, an email capture (input + "Join the waitlist" button) with inline validation and a success state, and a small "No spam" reassurance line. Used by [early adopters from a launch tweet] to reserve access in one action. Constraints: Next.js App Router, Tailwind, shadcn/ui Input and Button. Wire the submit to a server action that logs the email for now (I will connect a database later). Design tokens: dark theme, background #0B0F1A, primary #22D3EE, radius 10px. Fully responsive and keyboard-accessible.

Why it works: it defines the whole page as one screen with one action, so v0 ships a focused, complete result.

6. Full marketing site plan first

Before building, write a short PRD for a marketing site for [product]: the pages ([Home, Features, Pricing, About, Contact]), the sections on each, the shared nav and footer, the primary conversion goal, and the design-token set (colors, radius, font, spacing scale). List the components you will reuse across pages. Do not generate code yet. When I approve the PRD, build the Home page first using Next.js App Router, Tailwind, and shadcn/ui, and reuse the shared nav and footer.

Best for: multi-page sites where a plan-first pass prevents inconsistent, credit-burning rebuilds.

Dashboards & admin

Dashboards succeed when you spell out the exact metrics, tables, and actions rather than asking for "a dashboard." Give v0 the app shell, the data each widget shows, and the decision the viewer needs to make. For a deeper set, see v0 prompts for dashboards and admin panels.

7. Analytics dashboard overview

Build an analytics dashboard overview page. Product surface: a top row of 4 KPI cards ([MRR, Active users, Churn %, Trial conversions]) each with a value, a delta vs last period, and a sparkline; a large line chart of [signups over 30 days] with a range selector; a bar chart of [revenue by plan]; and a table of the [10 most recent signups]. Used by [a founder checking growth each morning] to spot what changed overnight. Constraints: Next.js App Router, Tailwind, shadcn/ui Card and Table, recharts for charts. Design tokens: primary #4F46E5, positive #16A34A, negative #DC2626, radius 12px. Responsive: KPI cards wrap to 2x2 on tablet. Use realistic sample data.

Why it works: naming the four metrics and their deltas gives v0 concrete widgets instead of generic placeholders.

8. Admin table with filters and bulk actions

Build an admin users table. Product surface: a shadcn/ui Table of users ([avatar, name, email, role, status, last active]), a search input, filter dropdowns for [role] and [status], column sorting, row checkboxes with a bulk-actions bar ([Suspend, Delete, Export]), pagination, and a right-side drawer that opens on row click to show user detail. Used by [a support admin managing accounts] to find and act on users fast. Constraints: Next.js, Tailwind, shadcn/ui Table, Input, Select, Checkbox, Sheet. Design tokens: radius 10px, muted #64748B. Responsive: collapse less-critical columns under 900px. Use sample data.

Best for: the CRUD-heavy admin screen at the center of most internal tools.

9. Support tickets dashboard

Build a support dashboard. Product surface: KPI cards for [open tickets, avg first response time, tickets solved today, SLA breaches]; a "tickets by priority" donut ([urgent, high, normal, low]); an agent list showing each agent's name, avatar, and current workload; and a table of open tickets ([subject, requester, priority, age, assignee]). Used by [a support lead deciding how to route work right now]. Constraints: Next.js, Tailwind, shadcn/ui Card, Table, Badge, recharts. Design tokens: urgent #DC2626, high #F97316, normal #4F46E5, radius 12px. Responsive down to tablet. Sample data.

Why it works: it ties each widget to a routing decision, so the layout serves the moment of use.

10. Sidebar app shell with nav

Build a reusable dashboard app shell. Product surface: a collapsible left sidebar with a logo, primary nav items ([Overview, Customers, Orders, Reports, Settings]) with lucide icons and an active state, a secondary section ([Help, Log out]) pinned to the bottom, a top bar with a search input, a notifications bell, and a user avatar menu, and a main content slot for the page. Used across every authenticated page. Constraints: Next.js App Router with a layout, Tailwind, shadcn/ui Sidebar and DropdownMenu. Design tokens: sidebar background #0F172A, active item primary #4F46E5, radius 10px. Sidebar collapses to icons under 1024px and to a drawer on mobile.

Best for: the layout wrapper every other dashboard page will live inside.

11. Settings page with tabs

Build a settings page with left-rail tabs: [Profile, Account, Notifications, Billing, Team]. Product surface: Profile has name, email, avatar upload, and a bio textarea; Notifications has grouped toggle rows; Billing shows the current plan, a usage meter, and a payment-method card. Each tab has a sticky "Save changes" bar that enables only when a field is dirty. Used by [an account owner adjusting their workspace]. Constraints: Next.js, Tailwind, shadcn/ui Tabs, Input, Switch, Card. Design tokens: radius 10px, primary #4F46E5. Responsive: tabs move to a top scroll strip on mobile.

Why it works: a dirty-state save bar is a concrete behavior v0 can implement, not a vague ask.

12. KPI card row with trends

Build a reusable KPI cards row as one component that takes an array of metrics. Each card: a label, a big value, a delta pill (green up / red down) with a percentage, a caption ([vs last 30 days]), and a small sparkline. Render [4] sample cards ([Revenue, New users, Conversion, Refunds]). Constraints: Next.js, Tailwind, shadcn/ui Card, recharts sparkline. Props-driven so I can pass real data. Design tokens: positive #16A34A, negative #DC2626, radius 12px, subtle border #E2E8F0. Responsive: wrap to 2 per row on tablet, 1 on mobile.

Best for: a data-driven component you will reuse across several dashboard pages.

Advertisement

Full-stack apps (database, auth, server actions)

The 2026 v0 runs in a sandbox and can add server actions, API routes, a database, and auth. For anything beyond a single screen, ask for a PRD first and build component by component, then deploy to Vercel.

13. PRD-first full-stack app

I want to build [app: e.g. a team task tracker]. First write a short PRD: the core user stories, the data model (entities and fields), the pages and routes, the server actions/API routes needed, and where a database and auth are required. Propose the shadcn/ui components and the design-token set. Do not write code yet. After I approve, build it in this order: (1) the data model and Supabase tables, (2) the app shell and auth, (3) the main list page, (4) create/edit, (5) polish. Stack: Next.js App Router, Tailwind, shadcn/ui, server actions.

Why it works: a PRD plus an explicit build order turns a big app into safe, reviewable steps.

14. CRUD app with Supabase

Build a [projects] CRUD feature backed by Supabase. Product surface: a list page with a table of [projects] ([name, status, owner, updated]), a "New project" button opening a dialog form, inline edit, and delete with a confirm. Wire it to a Supabase table [projects] with the matching columns and RLS off for now. Use server actions for create, update, and delete, and revalidate the list after each. Constraints: Next.js App Router, Tailwind, shadcn/ui Table, Dialog, Form. Design tokens: radius 10px, primary #4F46E5. Add optimistic UI on delete. Connect the Supabase integration and set the env vars.

Best for: the data-backed core of most internal apps, wired end to end.

15. Auth flow with protected routes

Add authentication to this app using [Supabase Auth]. Product surface: a sign-in and sign-up page (email + password, with an OAuth [Google] button), a sign-out action in the user menu, and route protection so [/dashboard/*] redirects unauthenticated users to /login. Show the signed-in user's name and avatar in the top bar. Constraints: Next.js App Router, server actions, middleware for route protection, Tailwind, shadcn/ui. Design tokens: match the existing theme. Handle and display auth errors inline. Do not build a password-reset flow yet.

Why it works: naming the exact protected route pattern and deferring password reset keeps scope tight.

16. Server action form submission

Build a [contact] form that submits via a Next.js server action. Product surface: fields [name, email, message], a shadcn/ui Form with client and server validation using Zod, a pending state on the button, inline field errors, and a success toast. On submit, the server action validates, then [inserts into a Supabase table `messages` / sends via the [Resend] integration]. Return a typed result and show errors from the server. Constraints: Next.js App Router, Tailwind, shadcn/ui Form, Input, Textarea, Button, Toast. Design tokens: radius 10px. Keep it accessible and responsive.

Best for: any form that must actually persist or send, not just look right.

17. API route handler with validation

Add a route handler at [app/api/webhooks/route.ts] that accepts a [POST] with JSON body [{ event, data }]. Validate the body with Zod, verify a [signature header] against an env secret, handle the [order.created] event by inserting a row into Supabase, and return 200 with a JSON ack or 400/401 on failure. Log failures. Constraints: Next.js App Router route handler, TypeScript, typed responses. Add a short comment block documenting the expected payload. Set the env var placeholders and tell me which ones to fill in Vercel.

Why it works: it specifies the exact path, method, validation, and error codes, so v0 emits a real handler.

18. Realtime notifications feature

Add realtime notifications. Product surface: a bell in the top bar with an unread count badge, a dropdown list of the latest [10] notifications ([icon, message, timestamp, read state]), a "Mark all read" action, and toast pop-ins for new events. Back it with a Supabase table [notifications] and subscribe to realtime inserts so new rows appear without refresh. Used by [a user who needs to see activity as it happens]. Constraints: Next.js App Router, Tailwind, shadcn/ui DropdownMenu, Badge, Toast, Supabase realtime. Design tokens: unread dot primary #4F46E5, radius 10px. Handle the empty state.

Best for: adding a live, database-backed feature onto an existing app.

19. Deploy to Vercel and wire env vars

Prepare this app for deployment to Vercel. List every environment variable it needs ([SUPABASE_URL], [SUPABASE_ANON_KEY], [SUPABASE_SERVICE_ROLE], any API keys), what each is for, and which must stay server-only. Add a short README section on setup, confirm the build passes, and flag anything that will break in production (missing env vars, client-side use of secrets). Then walk me through deploying to Vercel and connecting the GitHub repo so future changes ship on push.

Why it works: it makes v0 audit env and build readiness before you ship, catching secrets leaked to the client.

UI components

For single components, describe the states and props, name the shadcn/ui primitive to build on, and give the design tokens. v0 returns a self-contained, reusable component. See the best Lovable prompts for a sibling builder's take on the same patterns.

20. Command palette component

Build a command palette component. Product surface: opens on [Cmd/Ctrl+K], a search input, grouped results ([Pages, Actions, Recent]), keyboard navigation with arrow keys and Enter, a highlighted match, and an empty state. Actions are passed in as props. Constraints: Next.js, Tailwind, shadcn/ui Command and Dialog. Fully keyboard-accessible with proper focus trap and aria roles. Design tokens: radius 12px, muted #64748B, subtle border #E2E8F0. Closes on Escape and on selection.

Best for: a power-user shortcut that needs correct keyboard and focus behavior.

21. Data table component with sorting

Build a reusable data table component that takes columns and rows as props. Features: column sorting, a global search, per-page pagination, sticky header, row selection, and a slot for a per-row actions menu. Include loading skeleton rows and an empty state. Render a sample of [8] rows of [orders]. Constraints: Next.js, Tailwind, shadcn/ui Table, Input, Checkbox, DropdownMenu. Design tokens: radius 10px, header background #F8FAFC, border #E2E8F0. Make it generic with TypeScript generics so any row shape works.

Why it works: asking for generics and prop-driven columns yields a table you can reuse everywhere.

22. Reusable card with variants

Build a flexible Card component with variants: [default], [elevated], [outline], and [interactive] (hover lift + focus ring). It accepts a header slot, a body slot, and an optional footer with actions. Show one example of each variant in a demo grid. Constraints: Next.js, Tailwind, built on the shadcn/ui Card, variants via class-variance-authority. Design tokens: radius 12px, shadow soft, border #E2E8F0, primary #4F46E5 for the focus ring. Keep it accessible: interactive cards are focusable and keyboard-activatable.

Best for: a design-system primitive with clean, named variants.

23. Toast and notification system

Build a toast system with a provider and a useToast hook. Types: [success, error, warning, info], each with an icon and color, an optional action button, auto-dismiss with a progress bar, and stacking in the bottom-right. Include a demo panel with buttons to fire each type. Constraints: Next.js App Router, Tailwind, shadcn/ui Toast primitives. Design tokens: success #16A34A, error #DC2626, warning #F97316, info #4F46E5, radius 10px. Respect prefers-reduced-motion and make toasts screen-reader announced.

Why it works: defining each type and its accessibility behavior produces a complete, usable system.

24. Empty and loading states

For @file:[the list/table on the current page], add proper empty, loading, and error states. Empty: a centered icon, a short headline, one line of guidance, and a primary CTA ([Create your first item]). Loading: shimmer skeletons matching the real layout. Error: a friendly message with a Retry button. Constraints: Next.js, Tailwind, shadcn/ui. Design tokens: muted #64748B, radius 10px. Keep each state as its own component so I can reuse them. Do not change the happy-path layout.

Best for: the states teams skip that make a UI feel finished.

25. Accessible modal dialog

Build an accessible confirmation dialog component. Product surface: a title, a description, a destructive primary action ([Delete]) and a cancel action, with the confirm button showing a pending spinner while an async action runs. Constraints: Next.js, Tailwind, shadcn/ui AlertDialog. Must trap focus, close on Escape, restore focus to the trigger on close, and have aria-labelledby/aria-describedby wired correctly. Design tokens: destructive #DC2626, radius 12px. Provide a small usage example.

Why it works: spelling out focus trap and aria wiring forces v0 to get the accessibility details right.

Forms & flows

Multi-step flows need the steps, validation, and progress made explicit. Describe each step's fields and the success path, and v0 wires the state machine and validation for you.

26. Multi-step onboarding wizard

Build a 3-step onboarding wizard. Steps: (1) [workspace name + logo], (2) [invite teammates by email, add rows], (3) [pick a starting template]. Product surface: a progress indicator, Back/Next buttons, per-step Zod validation that blocks Next until valid, state preserved across steps, and a final "Finish" that shows a success screen. Used by [a new user setting up their account]. Constraints: Next.js App Router, Tailwind, shadcn/ui Form, Input, Button, Progress. Design tokens: primary #4F46E5, radius 10px. Responsive and keyboard-navigable. Submit the final payload via a server action.

Best for: first-run setup where each step must validate before advancing.

27. Checkout form with validation

Build a checkout form. Product surface: contact ([email]), shipping address fields, a payment section (card number, expiry, CVC with formatting/masking), an order summary card with line items and a total, and a "Pay [$amount]" button with a pending state. Client and server validation with Zod, inline errors, and a disabled submit until valid. Used by [a buyer completing a purchase] and it must feel trustworthy. Constraints: Next.js App Router, Tailwind, shadcn/ui Form, Input, Card. Design tokens: primary #4F46E5, error #DC2626, radius 10px. Do not integrate a real payment provider yet; stub the submit as a server action.

Why it works: the explicit "stub the submit" line lets v0 build the full UX now and wire payments later.

28. Search and filter flow

Build a searchable, filterable [product catalog] page. Product surface: a search input with debounce, a left filter rail ([category checkboxes, price range slider, in-stock toggle]), a sort dropdown, a responsive results grid of product cards, active-filter chips with clear buttons, and a "no results" state. Reflect filters in the URL query so state is shareable. Used by [a shopper narrowing down options]. Constraints: Next.js App Router with searchParams, Tailwind, shadcn/ui Input, Checkbox, Slider, Select. Design tokens: primary #4F46E5, radius 10px. Sample product data.

Best for: a browse experience where filter state should live in the URL.

29. File upload with progress

Build a file upload component. Product surface: a drag-and-drop zone plus a browse button, accepted types [images and PDFs] with a size limit, a list of queued files each with a thumbnail/icon, name, size, a progress bar, and a remove button, plus overall progress and a done state. Validate type and size before upload and show clear errors. Constraints: Next.js App Router, Tailwind, shadcn/ui, upload to [Supabase Storage / a stubbed server action] with a signed flow. Design tokens: primary #4F46E5, error #DC2626, radius 12px. Keyboard-accessible and screen-reader friendly.

Why it works: listing every per-file affordance yields a complete uploader instead of a bare input.

30. Booking and scheduling flow

Build a booking flow for [a 30-minute call]. Product surface: a month calendar with available days highlighted, a time-slot list for the selected day (in the user's timezone), a details step ([name, email, notes]), and a confirmation screen with an add-to-calendar link. Disable past and unavailable slots. Used by [someone scheduling a meeting] to book in under a minute. Constraints: Next.js App Router, Tailwind, shadcn/ui Calendar, Button, Form. Design tokens: primary #4F46E5, radius 10px. Responsive: calendar and slots stack on mobile. Persist the booking via a server action.

Best for: a self-serve scheduler with clear availability logic.

Cloning & redesign from a reference

Attach a screenshot or image and v0 rebuilds it as real code. Say what to match and what to change so it does not copy a reference wholesale. You can also import Figma frames or an existing repo.

31. Clone a UI from a screenshot

[Attach a screenshot.] Rebuild this screen as production code. Match the layout, spacing, and component hierarchy, but rebuild it with our stack, not raw HTML: Next.js App Router, Tailwind, and shadcn/ui components. Replace any brand colors with our design tokens: primary #4F46E5, background #FFFFFF, text #0F172A, radius 10px, font Inter. Make it responsive down to 360px and keyboard-accessible. Use realistic placeholder content, not lorem ipsum. Tell me anything in the screenshot you had to guess.

Why it works: matching structure but swapping in your tokens gives a clone you can actually ship.

32. Redesign an existing page

[Attach a screenshot of the current page, or paste its code.] Keep the same content and information hierarchy, but redesign the visuals to feel [modern, calm, and premium]. Improve spacing rhythm, typographic scale, and contrast; simplify the color palette to primary #4F46E5 on a neutral base; and add subtle depth with soft shadows and 12px radii. Keep it Next.js, Tailwind, and shadcn/ui. Do not remove any functionality or fields. Show a before/after summary of what you changed and why.

Best for: a visual refresh that must preserve every existing feature.

33. Import a Figma frame

[Import from Figma / attach the exported frame.] Turn this design into a responsive Next.js page. Map the Figma text and spacing styles to Tailwind tokens, use shadcn/ui components where they fit (buttons, inputs, cards), and extract repeated blocks into reusable components. Keep it pixel-close on desktop and gracefully responsive on mobile. Design tokens: read colors and radii from the frame, font Inter. Flag any Figma layer that does not map cleanly to a component so I can decide.

Why it works: asking v0 to extract repeated blocks avoids one giant unmaintainable component.

34. Restyle to a new brand

Restyle this app to a new brand without changing structure or copy. New design tokens: primary [#0EA5E9], secondary [#F59E0B], background [#0B1120] (dark), text [#E2E8F0], radius [14px], font [Geist]. Apply them through the Tailwind theme and shadcn/ui CSS variables so the change is centralized, not hard-coded per component. Update focus rings, hover states, and charts to match. Keep contrast accessible (WCAG AA). Show me the tokens you set so I can reuse them.

Best for: rethemeing a whole app from one central set of tokens.

35. Import my repo and add a page

[Import my GitHub repo.] Study the existing structure, Tailwind config, and shadcn/ui setup, then add a new [reports] page that matches the conventions already in the codebase (routing, component patterns, naming, and design tokens). Reuse existing components rather than creating new ones where possible. Product surface: [describe the page]. When done, open a pull request with a clear description of what you added. Do not change unrelated files or reformat code you did not touch.

Why it works: importing the repo lets v0 match your real conventions and ship the change as a reviewable PR.

Iteration & Design Mode

Once the layout is close, switch to Design Mode for visual polish and use prompt queuing to chain refinements. These prompts cover the last mile: tokens, responsiveness, and branching a design.

36. Set design tokens and theme

Set up a centralized theme before we build more. Define these design tokens as Tailwind theme values and shadcn/ui CSS variables: colors (primary #4F46E5, secondary #22D3EE, success #16A34A, danger #DC2626, neutral scale), radius 10px, font Inter, a spacing scale (4/8/12/16/24/32), and shadow presets (sm, md, lg). Apply them app-wide so every component reads from the tokens, not hard-coded values. Add a light and dark variant. Show me the token file so I can tweak it.

Best for: establishing one source of truth so later prompts stay consistent.

37. Polish visuals in Design Mode

The layout is right; now polish the visuals. Tighten vertical rhythm so section spacing is consistent, increase the heading-to-body size contrast, soften the card shadows, align the icon sizes, and make the primary buttons the clear focal point on each screen. Keep everything on the existing design tokens. Small visual tweaks only, no structural or functional changes. [Then use Design Mode to nudge specific colors and spacing without spending generations.]

Why it works: it separates a visual-only pass from structure, and points you to Design Mode to save credits on nudges.

38. Make it responsive and accessible

Make this page fully responsive and accessible without changing its content. Responsive: verify layouts at 360px, 768px, and 1280px; stack multi-column sections on mobile; make tables scroll or collapse; ensure tap targets are at least 44px. Accessible: proper heading order, labels tied to inputs, visible focus rings, AA color contrast, and aria attributes on interactive components. Keep Next.js, Tailwind, and shadcn/ui. List the specific issues you found and fixed.

Best for: a final quality pass before you ship or hand off.

39. Queue a build-then-refine sequence

[Queue these prompts in order.] 1) Build the [dashboard overview] layout with the KPI row, main chart, and recent-activity table using sample data. 2) Wire the data to a Supabase table [metrics] via a server action and revalidate. 3) Add empty, loading, and error states to every widget. 4) Make it responsive down to 360px and keyboard-accessible. 5) Do a visual polish pass on spacing, shadows, and the primary color. Stack: Next.js App Router, Tailwind, shadcn/ui. Report after each step.

Why it works: queuing chains a clean build order so v0 layers structure, data, states, and polish in sequence.

40. Fork a generation to branch a design

[Fork this generation.] From the current version, produce an alternative design direction: same content and features, but a [bolder, editorial] look with a larger type scale, a warmer palette (primary [#EA580C]), more whitespace, and full-bleed section imagery. Keep it Next.js, Tailwind, and shadcn/ui. I want to compare this branch side by side with the original, so do not overwrite the current version. Summarize the key differences in direction.

Best for: exploring a second visual direction without losing the first.

That is the full set of 40. If you keep one habit: name the exact product surface, say who uses it and to decide what, and hand v0 your design tokens up front. For focused packs, see the landing-page prompts and dashboard prompts, and the guide to prompting v0 for UI.

Frequently Asked Questions

What is v0 by Vercel?

v0 by Vercel is an AI generative-UI and app builder. From a natural-language prompt it produces production-ready React, Next.js (App Router), Tailwind CSS, and shadcn/ui code you can preview, iterate on, and deploy to Vercel in one click. The 2026 version is full-stack, with a sandbox runtime, server actions, API routes, database connections, and GitHub integration.

How should I structure a v0 prompt?

Use v0's three-part framework: the product surface (the exact components, data, and actions), the context of use (who uses it, in what moment, to make what decision), and the constraints and taste (platform, visual tone, layout, and exact design tokens like colors, radius, font weights, and spacing). Vercel's template is: Build [product surface]. Used by [who], in [what moment], to [decision]. Constraints: platform, visual tone, layout assumptions.

What is Design Mode in v0?

Design Mode is a visual editor inside v0 for tweaking colors, spacing, typography, and component states without writing code or spending generation credits. Use prompts for functional and structural changes, and Design Mode for quick visual polish once the layout is close.

Can v0 build full-stack apps with a database and auth?

Yes. The 2026 v0 runs in a sandbox that mirrors a real environment and can add server actions and route handlers, wire a database such as Supabase, Neon, or Postgres, manage environment variables, and add authentication. Ask it to write a short PRD first, then build the app component by component.

How do I redesign or clone a UI from a screenshot in v0?

Attach a screenshot or image to your message and describe what to match and what to change. v0 reads the reference and rebuilds it as real Next.js and Tailwind code. You can also import a Figma design or paste an existing component and ask v0 to restyle it against your design tokens.

What is prompt queuing?

Prompt queuing lets you chain several sequential instructions (roughly up to ten) so v0 works through them in order without waiting for each to finish. It is useful for a build-then-refine sequence: generate the layout, then wire data, then add states, then polish, all queued at once.

How do I save credits in v0?

Every generation, even a failed one, burns token-based credits, so a tight, specific prompt is the main saver. Give the exact product surface and design tokens, state what NOT to build, iterate visual polish in Design Mode instead of re-prompting, and ask for a plan or PRD before large builds. Prompting technique matters more than the model tier you pick.

Which stack does v0 output?

v0 emits React with Next.js App Router, Tailwind CSS, shadcn/ui components, and TypeScript. On the backend it can add server actions and route handlers and connect Supabase, Neon, or Postgres, then deploy to Vercel. Because it targets shadcn/ui, referencing those components and your CSS variables in the prompt keeps the output consistent.

Advertisement