Mobile Responsiveness Audit Skill

How this skill behaves (read first)

This is an evaluative skill — it reviews existing work against mobile/touch standards, it doesn't generate. Flagging is safe, so it auto-runs and is built to be called as a validation step by generative skills whenever the target is mobile or responsive (the component family, screens, and flows all hand off here for their mobile context).

It owns the mobile/touch-adaptation concern in this repo. To avoid duplicating its sibling audits, it defers:

• WCAG ratios, screen-reader/assistive-tech, keyboard operability, alt text, captions → the accessibility audit. This skill judges physical touch ergonomics and layout adaptation, not AT compatibility or contrast math.
• Visual composition — hierarchy, spacing aesthetics, emphasis → the aesthetics audit.
• Usability, flow, and interaction logic → the heuristics audit.
• Content structure / navigation scheme → the information-architecture audit; type scale → ux-typography.

Applicability gate: this audit only applies when the target is meant to work on mobile or across breakpoints. If a design is explicitly desktop-only (e.g. a complex internal admin tool with no mobile support), say so and skip — don't manufacture mobile findings.

Scope discipline. When invoked directly (the user named this audit), review only this concern — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (ux-design-review) or a generative skill calls it under docs/orchestration-policy.md, where it sits in Tier B — offered (only when the platform is mobile). Explicit scope always wins.