mobile-readiness

Mobile CSS existing is not the same as the site working at mobile sizes. The question is: can a person on a phone complete the main task, read the content, and reach the actions?

Activate when

• Any public web UI before launch, after a redesign, or when users report phone problems.
• launch-all/quality-all route here (checks 33, 34).
• Not for native app testing or device-lab coverage.

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.

Inspect

1. Sweep (paths relative to this skill's folder; serve a build locally if needed):