public-support

Visitors need a way to say "this is broken", "delete my data", or "I was charged twice". A contact path that bounces or never gets read is worse than an honest "email us at…".

Activate when

• Any public product; especially commerce, accounts, forms, or a launch with press attention.
• Legal pages reference a contact route; footer says "Contact" but goes nowhere.
• Not to set up a helpdesk or staff support.

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. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: design-system-reconnaissance, forms-readiness.

Inspect