ux-mobile-responsiveness-audit

Audits designs against mobile touch-target, reflow, orientation, and readability standards.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-mobile-responsiveness-audit-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-mobile-responsiveness-audit
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/ux/audits/mobile-responsiveness
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-mobile-responsiveness-audit-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviews of mobile-friendliness often produce vague feedback like "make the buttons bigger" with no thresholds, no severity, and no systematic coverage. This Skill turns a mobile review into a structured audit that checks seven concrete areas — viewport reflow, orientation, touch targets, thumb reach, input ergonomics, gesture safety, and readability — and rates every finding by whether it blocks the task on the actual device. ## Core Features & Use Cases - Seven-area systematic sweep: Checks viewport adaptation and reflow, orientation resilience, touch-target size and spacing (44pt/48dp, ≥8dp spacing), thumb reachability, mobile input ergonomics, gesture safety, and mobile readability (≥16px body, 30–40 character lines). - Severity-rated findings: Classifies issues as Critical, Major, or Minor based on task impact on the device, each with the violated principle, the concrete threshold, and a specific fix. - Validation handoff: Designed to run as a post-generation validation step for mobile or responsive UI produced by generative design skills, while deferring WCAG/contrast, aesthetics, and flow concerns to sibling audits. - Use Case: After generating a responsive checkout screen, run this audit to catch a 28px delete button adjacent to Save, a phone field opening a QWERTY keyboard, and a CTA stranded in the top corner — each rated and paired with a fix. ## Quick Start Ask the assistant to run a mobile responsiveness audit on your screen or component, describing the target device class and primary task.

Frequently Asked Questions about ux-mobile-responsiveness-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a design for mobile responsiveness?▼

Run a structured sweep across seven areas: viewport reflow, orientation resilience, touch-target size and spacing, thumb reachability, input ergonomics, gesture safety, and readability. Rate each finding Critical, Major, or Minor by whether it blocks the task on the device, and pair it with a concrete fix.

What is the minimum touch target size for mobile UI?▼

Use 44×44pt on iOS and 48×48dp on Android (Material) as the working minimums, with at least 8dp spacing between tappable elements. WCAG's 24px is a floor, but platform minimums are the practical target; enlarge corner targets further since they are harder to hit.

Does this audit cover WCAG accessibility and contrast?▼

No. It deliberately defers WCAG contrast ratios, screen-reader support, keyboard operability, and alt text to a separate accessibility audit. This audit judges physical touch ergonomics and layout adaptation, not assistive-technology compatibility.

When should I skip a mobile responsiveness audit?▼

Skip it when the design is explicitly desktop-only, such as an internal admin tool with no mobile support. The applicability gate prevents manufacturing mobile findings for interfaces never intended to run on phones or tablets.

Why are gesture-only interactions flagged in mobile audits?▼

Gestures are invisible and have discoverability and accessibility limits, so a critical action reachable only by a hidden swipe or long-press is flagged. Gestures should supplement a visible control, never be the sole path, and complex multi-finger gestures exclude users with motor limitations.