trust-all

Owns launch family C (checks 19–26). Trust is broader than badges: it is whether the product does what it visibly promises and looks like a real business. Visitors decide in seconds, and dead controls, lorem ipsum, invented metrics, and 404s in the footer are what they notice.

Activate when

The site is public and about to be shown to real users, investors, press, or customers.
launch-all routes here, or the user says "it feels unfinished / fake / sketchy".
Not for legal-page authoring (compliance-all) or visual redesign (this repairs broken trust surfaces in the existing design).

Working alone

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. The lanes this bundle can activate are companions because it promises to run them when they apply: consider them all, activate only the ones that fit. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: content-trust, faq-readiness, error-pages, link-integrity, failure-resilience, public-support, launch-identity, legal-navigation.

Route

Sweep once (paths relative to this skill's folder; --render for client-rendered apps):