trust-signals
Trust Signals
Build credibility through evidence, not claims.
How to use
/trust-signalsApply trust signal constraints to this conversation.
Constraints
Hierarchy of Trust (strongest to weakest)
- Specific metrics from named customers ("Saved 14 hours/week" - Sarah, VP at Acme)
- Named customer logos from recognizable companies
- Aggregate numbers ("Used by 2,400 teams")
- Star ratings with review count
- Security/compliance badges
- General testimonial quotes without specifics
Placement Rules
- MUST place first trust signal within 1 scroll of the hero
- MUST place trust signals near every major CTA
- SHOULD increase trust signal density as the page approaches the conversion point
- NEVER cluster all social proof in one section. Distribute it.
- NEVER show an empty testimonial section or "as seen in" with no logos
Quality Rules
- Testimonials MUST include: name, role, company, and a specific outcome
- NEVER use stock photos for testimonial avatars
- Logos MUST be real customers. Remove any that are aspirational.
- Case study structure: situation, problem, solution, measurable result
- Numbers MUST be current and verifiable. Round down, not up.
Anti-Patterns
- Fake urgency counters ("Only 3 spots left!")
- Testimonials that sound written by marketing
- Trust badges from organizations nobody recognizes
- "As featured in" with publications that feature everyone
- Social proof without specificity ("Great product!" - John)
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1