A testimonial wall from real reviews

Paste into any coding agent: Claude Code, Cursor, Codex, Copilot, Windsurf or Cline.

# A testimonial wall from real reviews

Proof from real users helps launch visitors trust the production site, and fake or unattributed proof destroys that trust the moment someone checks. Build a testimonial section from real quotes I give you, with names, roles and sources, stored as data so it is easy to keep current.

Site: not given. Find the production URL in the project config, or ask me.

## Ground rules

1. Read before you write. Explore the parts of the codebase this job touches and tell me what is already in place.
2. Plan, then stop. Give me a numbered plan: what you will change, in which files, and why. Wait for my approval before editing anything.
3. Fix things at their source (the shared layout, the config, the generator), not with one-off patches page by page.
4. Keep the project's conventions: its framework APIs, file layout, naming and code style. Add no new dependency without asking.
5. Where something is already done well, say so and leave it alone.

## You will not

- Edit `.env` files, secrets or API keys, or print their values.
- Deploy, push, merge or publish anything.
- Delete data, or run migrations or scripts against a production database.
- Add tracking, third-party scripts or links to any site I did not ask for.
- Change copy, design or behaviour that this job does not need.
- Write or invent any testimonial.
- Show a person's name or photo without my confirmation of permission.

## Your stack

- Framework: Work out the framework, router and build output from the project files (package.json, lockfiles, framework config) before planning, and say which you found.
- Host: Work out where the site is hosted from the config files (vercel.json, netlify.toml, wrangler config, Dockerfile, fly.toml) and say which you found.

## Steps

### 1. Collect the quotes with me

Ask me for the quotes and their sources (launch comments, support emails, reviews, social posts), and confirm I have permission to show each with the person's name. Do not take quotes from anywhere I have not given you.

### 2. Store them as data

Put testimonials in one data file or table: quote, name, role or company, avatar (optional, with permission), source and its link, and date. Short quotes work best; trim only with "...", never change meaning.

### 3. Build the section

A responsive wall or carousel that shows each quote with its person and a link to the source where it is public. Place the strongest two or three near the main call to action on the landing page and the rest on their own section or page.

### 4. Structured data, honestly

Do not add `Review` or `AggregateRating` markup for testimonials you chose yourself; Google treats self-selected reviews on your own site as not eligible. Use plain HTML with `<blockquote>` and `<cite>`.

## Done means

- [ ] Every testimonial is real, permitted, and has a name and source.
- [ ] Testimonials live in one data file or table.
- [ ] The section works at phone width and links to public sources.
- [ ] No Review or AggregateRating markup is added for self-selected testimonials.

## Report back

When you finish, give me:

- what you changed, file by file;
- anything you skipped, and why;
- anything I must do by hand (DNS records, dashboards, accounts, deploys);
- how to check each change on the live site.