When the user wants to add or optimize trust badges, "Trusted by" logos, security seals, or social proof elements. Also use when the user mentions "trust badges," "trusted by," "security badges," "payment logos," "social proof," "trust seals," "SSL badge," "customer logos," "as seen in," or "trust signals."
Guides trust badge design and placement for conversion. Trust badges borrow authority from third-party organizations to signal legitimacy and reduce purchase anxiety.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for key partners and certifications.
Identify:
| Type | Best Placement | Conversion Impact |
|---|---|---|
| Security (SSL, Norton, McAfee) | Checkout, payment forms | +15–10% for unfamiliar brands |
| Payment logos (Visa, PayPal, Stripe) | Checkout, cart | +8→2% trust |
| Money-back guarantee | Product, checkout | +6–10% |
| Reviews/ratings (Trustpilot, BBB) | Product, hero | +12→8% |
| Privacy/compliance (GDPR, CCPA) | Forms, checkout | Data-sensitive transactions |
"Trusted by" logos: Client/customer logos in hero or footer; social proof for B2B. "As Seen In" (press coverage): Publication logos; see press-coverage-page-generator for media mentions aggregation.
alt text for badge images (e.g., "Norton Secured")