v0 Prompt Crafter
Produce a copy-paste-ready prompt for Vercel v0 that is specific enough to generate a memorable interface. The deliverable is the prompt, not application code.
Parse The Product
Extract these facts from the user input or PRD:
- Product name and one-line pitch
- Core features, data fields, and user actions
- Target user and their technical comfort
- Context of use, such as device, environment, urgency, and attention span
- Decision or outcome the UI helps the user reach
- Industry or vertical
- Scope: component, landing page, marketing site, dashboard, full app, or multi-screen flow
If facts are missing, propose two or three concrete options and ask the user to choose. Do not silently invent product facts.
Missing facts matter most when they affect trust, privacy, conversion, or layout. For health, finance, legal, education, and AI products, explicitly resolve or label assumptions about privacy posture, regulated context, primary differentiator, and the most important user action before writing the final prompt.
Read The Industry
Give a one-paragraph industry read before choosing a style. Mention the visual expectations of comparable products, such as density, trust cues, typography, color conventions, and layout patterns.
Use current docs or web research when the task depends on up-to-date v0, shadcn, Magic UI, Aceternity, or Motion details.
Choose A Strong Direction
Avoid generic "clean modern" prompts. Pick one coherent aesthetic and commit to it.
Possible directions:
- Brutalist editorial
- Retro terminal
- Soft luxury
- Neo-brutalist memphis
- Glassmorphic depth
- Organic biomorphic
- Industrial technical
- Playful toy-like
- Minimal Swiss grid
- Ink editorial print
Write an aesthetic statement with:
- Name of the direction
- Feeling in two or three adjectives
- One signature visual detail
Then lock the design tokens:
- Theme: light or dark
- Background, surface, foreground, and one or two accents as hex values
- Display, body, and mono fonts by exact name
- Radius, spacing unit, density, texture, and motion language
Colors must be hex values. Fonts must be real fonts or known platform fonts.
Choose Libraries
Use library choices that support the aesthetic rather than adding effects for novelty.
shadcn/ui: app chrome, forms, cards, dialogs, tables, tabs, command palettes@magicui: marquee, number ticker, animated grid, border beam, terminal, shimmer, orbiting circles@aceternity: spotlight, aurora, bento grid, infinite moving cards, tracing beam, meteors, sparklesmotion/react: custom page-load, hover, scroll, and layout animationslucide-react: iconsrecharts or tremor: dashboards and chartsreact-three-fiber plus @react-three/drei: only when 3D is central to the concept
Minimal Swiss should not use heavy animated backgrounds. Retro-terminal or playful community pages can justify stronger effects.
Build The Prompt
The v0 prompt must include:
- Product surface: every section, component, data field, and action
- Context of use: who, where, and what decision they need to make
- Aesthetic direction and signature detail
- Visual system with concrete tokens
- Component and library stack
- Layout from top to bottom or screen by screen
- Motion rules
- Responsive behavior
- Accessibility requirements
- What to avoid
If the user asked for speed and essential facts are missing, include an Assumptions To Confirm line before the prompt and make the assumptions visible inside the prompt. Do not bury them in the explanation.
Length guidance:
- Single component: 80-150 words
- Landing page: 250-450 words
- Full app: 500-900 words, or split into one prompt per screen
Output Format
Return exactly:
- Industry Read: one paragraph
- Aesthetic Statement: two or three sentences
- Design Tokens: bullets with hex colors, fonts, radius, spacing, density, texture, motion
- Library Stack: bullets with purpose for each library/component
- The v0 Prompt: one fenced code block that is self-contained
- How To Use It: three short bullets
- Follow-Up Prompts: three to five one-line iteration prompts
Quality Bar
- The prompt should be self-contained enough that a developer can paste it into v0 with no extra context.
- Never default to Inter, purple gradients, centered hero with one CTA, lorem ipsum, or emoji-only feature icons.
- Use real copy whenever the user provided it.
- For regulated industries, keep the design disciplined and include trust cues.
- Do not claim v0 will produce a perfect result. Give useful follow-up prompts.
1---2name: v0-prompt-crafter3description: Turn a PRD, product idea, app description, screenshot brief, or rough UI concept into a high-signal Vercel v0 prompt. Use this skill whenever the user wants a v0 prompt, landing page prompt, app UI generation prompt, visual direction, shadcn/Magic UI/Aceternity guidance, or a more distinctive interface than generic AI output.4---56# v0 Prompt Crafter78Produce a copy-paste-ready prompt for Vercel v0 that is specific enough to generate a memorable interface. The deliverable is the prompt, not application code.910## Parse The Product1112Extract these facts from the user input or PRD:13141. Product name and one-line pitch152. Core features, data fields, and user actions163. Target user and their technical comfort174. Context of use, such as device, environment, urgency, and attention span185. Decision or outcome the UI helps the user reach196. Industry or vertical207. Scope: component, landing page, marketing site, dashboard, full app, or multi-screen flow2122If facts are missing, propose two or three concrete options and ask the user to choose. Do not silently invent product facts.2324Missing facts matter most when they affect trust, privacy, conversion, or layout. For health, finance, legal, education, and AI products, explicitly resolve or label assumptions about privacy posture, regulated context, primary differentiator, and the most important user action before writing the final prompt.2526## Read The Industry2728Give a one-paragraph industry read before choosing a style. Mention the visual expectations of comparable products, such as density, trust cues, typography, color conventions, and layout patterns.2930Use current docs or web research when the task depends on up-to-date v0, shadcn, Magic UI, Aceternity, or Motion details.3132## Choose A Strong Direction3334Avoid generic "clean modern" prompts. Pick one coherent aesthetic and commit to it.3536Possible directions:3738- Brutalist editorial39- Retro terminal40- Soft luxury41- Neo-brutalist memphis42- Glassmorphic depth43- Organic biomorphic44- Industrial technical45- Playful toy-like46- Minimal Swiss grid47- Ink editorial print4849Write an aesthetic statement with:5051- Name of the direction52- Feeling in two or three adjectives53- One signature visual detail5455Then lock the design tokens:5657- Theme: light or dark58- Background, surface, foreground, and one or two accents as hex values59- Display, body, and mono fonts by exact name60- Radius, spacing unit, density, texture, and motion language6162Colors must be hex values. Fonts must be real fonts or known platform fonts.6364## Choose Libraries6566Use library choices that support the aesthetic rather than adding effects for novelty.6768- `shadcn/ui`: app chrome, forms, cards, dialogs, tables, tabs, command palettes69- `@magicui`: marquee, number ticker, animated grid, border beam, terminal, shimmer, orbiting circles70- `@aceternity`: spotlight, aurora, bento grid, infinite moving cards, tracing beam, meteors, sparkles71- `motion/react`: custom page-load, hover, scroll, and layout animations72- `lucide-react`: icons73- `recharts` or `tremor`: dashboards and charts74- `react-three-fiber` plus `@react-three/drei`: only when 3D is central to the concept7576Minimal Swiss should not use heavy animated backgrounds. Retro-terminal or playful community pages can justify stronger effects.7778## Build The Prompt7980The v0 prompt must include:81821. Product surface: every section, component, data field, and action832. Context of use: who, where, and what decision they need to make843. Aesthetic direction and signature detail854. Visual system with concrete tokens865. Component and library stack876. Layout from top to bottom or screen by screen887. Motion rules898. Responsive behavior909. Accessibility requirements9110. What to avoid9293If the user asked for speed and essential facts are missing, include an **Assumptions To Confirm** line before the prompt and make the assumptions visible inside the prompt. Do not bury them in the explanation.9495Length guidance:9697- Single component: 80-150 words98- Landing page: 250-450 words99- Full app: 500-900 words, or split into one prompt per screen100101## Output Format102103Return exactly:1041051. **Industry Read**: one paragraph1062. **Aesthetic Statement**: two or three sentences1073. **Design Tokens**: bullets with hex colors, fonts, radius, spacing, density, texture, motion1084. **Library Stack**: bullets with purpose for each library/component1095. **The v0 Prompt**: one fenced code block that is self-contained1106. **How To Use It**: three short bullets1117. **Follow-Up Prompts**: three to five one-line iteration prompts112113## Quality Bar114115- The prompt should be self-contained enough that a developer can paste it into v0 with no extra context.116- Never default to Inter, purple gradients, centered hero with one CTA, lorem ipsum, or emoji-only feature icons.117- Use real copy whenever the user provided it.118- For regulated industries, keep the design disciplined and include trust cues.119- Do not claim v0 will produce a perfect result. Give useful follow-up prompts.
IdkwhatImD0ing