testimonial-proof-systems git:20260621.2caaeccA

Immutable. This exact content is served forever at /api/v1/blob/0074179498442936.

---
name: testimonial-proof-systems
description: "Create testimonial and proof systems for websites. Use for testimonials, reviews, customer quotes, logo walls, metrics, press quotes, case-study excerpts, ratings, social proof, proof strips, trust sections, and copy that must be credible, approved, and specific."
---

# Testimonial Proof Systems

Use this skill to use proof to reduce risk without making fake or contextless claims.

## Workflow

1. Inspect the page goal, audience, offer/product reality, source copy, proof, IA, forms, SEO/social metadata, brand voice, and verification commands.
2. Read [Testimonial Proof Systems Guide](references/testimonial-proof-systems-guide.md) before changing headings, sections, CTAs, metadata, labels, or UI copy.
3. Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
4. Replace generic claims with specific language or remove them.
5. Inspect the rendered page on desktop and mobile for hierarchy, wrapping, repetition, and whether copy still matches the UI.

## Always Protect

- Inspect before writing or coding: audience, offer, product/service reality, source copy, assets, proof, claims, conversion goal, information architecture, SEO/metadata needs, forms, legal/trust constraints, and available verification commands.
- Use copy to make the design more specific: every headline, label, CTA, section, and proof point should reduce ambiguity rather than decorate the layout.
- Avoid generic premium language, vague transformation claims, placeholder testimonials, fake metrics, empty adjectives, and hero copy that could fit any brand.
- Write in the user's domain vocabulary while keeping language clear, concise, concrete, and scannable.
- Tie claims to proof: screenshots, artifacts, reviews, credentials, specifications, case studies, pricing terms, process details, or real outcomes.
- Keep navigation, forms, pricing, FAQs, and CTAs honest and task-focused; do not create dark patterns or hide material terms.
- Respect accessibility and structure: semantic headings, meaningful link/button text, labeled forms, useful error/help text, readable line lengths, and no critical copy trapped in images.
- Before delivery, inspect rendered desktop and mobile copy for hierarchy, wrapping, overflow, repetition, and whether the words still match the implemented page.