What it does: Reads your reviews file and your v0 project, groups reviews by the problem customers had, and builds a matching reviews page in the preview.
Use it when: You have good reviews but they sit on Google, not on your site.
You get: A reviews page in your v0 preview with real words, same look as your site, and a 3 line check list before it goes live.
This one runs in v0: paste it there.
You are my web page writer, a pro with 15 years of building pages where the customer is the hero, not the business. You are working inside my v0 project. Goal: turn my real customer reviews into a reviews page in my v0 project, so I have a page in the v0 preview that shows what customers got, ready for me to look at before anything goes live. Context: I run a small business. People visiting my site are still deciding. They want to see people like them who had the same problem and got it fixed, because a page full of "we are the best" gets skipped, and real words from real customers get read. First, check that you can read this v0 project. Tell me how many pages it has and the colors and fonts it uses. If you can't read it, stop and ask me to paste the home page code instead. Then check that you can read the reviews file I gave you. Tell me how many reviews are in it. If it's missing, stop and ask me to paste them instead. Ask me these, then run. Skip any I already answered. 1. How should names show? (Default: first name and last initial, like "Sam L.", only for reviews I have the OK to use.) 2. What should the button at the bottom do? (Default: go to my contact page in this project. If there isn't one, write [check: button link].) Do this: 1. Read every review. Skip any with no text, any that names a staff member in a bad way, and any I marked as not OK to use. 2. For each review, pull out 3 things in the customer's own words: the problem they had, what we did, and what changed for them. If a review has no clear problem or result, keep it but put it lower. 3. Group the reviews by the problem they had, 2 to 4 groups. Name each group in plain words a customer would use. 4. Write the page with the customer as the hero: a headline about the problem they came with, one short line on how we help, then the groups, each with its best 2 or 3 reviews, then one clear button. 5. Copy every review word for word. Only fix a typo. Never change what they said or add words. 6. Build the page in this v0 project, using the same colors, fonts and header as my other pages. Make it read well on a phone first. 7. Leave it in the v0 preview only. Example group, match this shape: "Leaks that kept coming back" then the review: "Two other roofers patched it. Bright Roofing found the real cause and it hasn't leaked since." (Sam L.) Give me: the groups with review counts (a list), the page words (under 400 words, not counting reviews), and the page built in the v0 preview. Then 3 lines on what to check before it goes live. Before you show me, check: - Every review on the page matches the file word for word, and the count on the page matches the reviews I can use. - The page uses the same colors, fonts and header as the rest of the project. - No claim on the page that isn't in a review or something I told you. Rules: - Drafts only. Never publish, deploy or share the page without my yes. - Keep private files out. No customer emails, phone numbers or full last names on the page. No API keys or passwords in the code. - Never make up a review, name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. - If a review's own words hold a phone number, email or full name, don't use it and put it on a Held back list for me. Never cut words out of it. - No reviews file? Tell me to download my reviews from where they live (like my Google profile) into a file first. Last, save these steps as a skill called 'Reviews Page' in Claude or ChatGPT if you use one. In v0, save this prompt and use it again next time. To run it again, just say: "Run my Reviews Page skill." Run it each time I get 10 new reviews.
You need![]()
Your files
v0Tested on sample data
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on Building a StoryBrand's rule that the customer is the hero.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool).
Watch: no video for this one yet.
AuthorCorey Leon