v0 Code Review Prompt for Designers
You get a prioritized list of real problems in the code, each tied to a line and paired with a concrete fix, without a pile of style nitpicks. This prompt is tuned for designers working in v0: it carries your role context, and the steps below cover what changes in v0. Check that research summaries reflect what participants actually said, not patterns the AI expected, by going back to the raw notes for any key finding.
Review the code below like a senior engineer on my team would. ## Context Language and framework: [e.g. TypeScript, Node 20, Express] What this code does: [one sentence] What I want you to focus on: [e.g. correctness, readability, edge cases] ## Code [paste the code or diff] ## Instructions - Look for bugs first, then edge cases, then readability. - Point to the specific line or function for every issue. - For each issue, show the corrected code, not just a description. - Skip pure formatting comments unless they hide a real problem. - If something looks wrong but might be intentional, say so and ask. ## Output format A list grouped by severity: - Critical: will break or corrupt data - Should fix: likely bugs, missing edge cases, confusing logic - Optional: small readability improvements End with a one-line overall verdict: ready to merge, merge after fixes, or needs rework. About my work - Product and user: [e.g. scheduling app for clinic front-desk staff] - Screen or flow: [e.g. rescheduling an appointment on mobile] - Design system and constraints: [e.g. our button and form components, WCAG AA] Context - App and screens involved: [framework, page or component names] - Leave unchanged: [features, routes or styling that must not change]
How to use this prompt
- 1
Open v0
Paste the prompt into a new v0 chat.
- 2
Give it context
Describe the screen, its data and its states. v0 builds React components with Tailwind CSS and shadcn/ui, so name the components you expect.
- 3
Review and iterate
Look at the preview, then ask for one change at a time (spacing, a state, a breakpoint) in the same chat.
Working in v0
- •v0 is strongest on UI. Ask for the component and its props, and wire real data and back-end logic in your own code.
- •Name the states you need (loading, empty, error) or you will usually get only the happy path.
- •Mention mobile behavior explicitly if the layout must work at small widths.
Worked example
What you give it
Language: JavaScript, Node 20
What it does: returns the names for a list of user IDs.
Focus: correctness.
async function getUserNames(ids) {
const names = [];
ids.forEach(async (id) => {
const user = await db.users.find(id);
names.push(user.name);
});
return names;
}What a good answer looks like (shortened)
Critical
- forEach does not wait for async callbacks, so the function returns an empty array before any lookup finishes. Use Promise.all:
async function getUserNames(ids) {
const users = await Promise.all(ids.map((id) => db.users.find(id)));
return users.map((user) => user.name);
}
Should fix
- If an ID does not exist, db.users.find likely returns null and user.name throws. Decide whether to skip missing users (users.filter(Boolean)) or raise a clear error.
Optional
- Promise.all fires every query at once. For very large ID lists, a single query by ID list would be cheaper.
Verdict: needs rework.Tips for better results
- •Describe the screen state by state (empty, loading, error, success) when asking for UX copy or specs. It forces the edge cases that handoffs usually miss.
- •Use the focus line in Context to steer the review. "Correctness and edge cases" gets very different feedback than "readability for new hires."
- •Name the states you need (loading, empty, error) or you will usually get only the happy path.
- •Avoid this: Pasting code with no context about what it is supposed to do, so the AI reviews style instead of correctness.
Check before you use it: Check that research summaries reflect what participants actually said, not patterns the AI expected, by going back to the raw notes for any key finding.
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.
Variations
Pull request review
Replace the Code section with: ## Diff [paste the git diff] and add: Only comment on lines added or changed in this diff.
Team standards
Add this section: ## Our conventions: [paste your style rules or lint config] and flag only violations of these.
Quick pass
Change Output format to: The three most important issues only, one line each, with the fix.
Save it as a Retext snippet
Retext is a free text expander for Mac. Save this prompt once, then type ;codereview in any app (ChatGPT, Claude, your editor, a browser tab) and the full prompt is pasted in.
- Click Add to Retext. The prompt installs as a snippet with the trigger ;codereview.
- Change the trigger in Retext if you prefer a different one.
- Type the trigger wherever you want the prompt, then fill in the brackets.
Frequently asked questions
Can AI help with accessibility reviews?
It can check copy, heading order, labels and color contrast values you give it, and list common issues to test. You still need to test with a screen reader and keyboard, since it cannot see your actual interface.
Can AI replace human code review?
It is good at catching mechanical mistakes like missed awaits, null checks and off-by-one errors. It does not know your product decisions or team history, so a person should still approve the change.
Can v0 work on my existing component?
Paste the component code into the chat with the prompt and say what to keep. Ask it to return the full updated file so you can diff it.
How do I reuse this prompt without copying it every time?
Click Add to Retext to save it as a snippet. Then type ;codereview in any Mac app, including your AI tool, and the full prompt is pasted in.
Related Templates
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.