Mobile Responsive QA
SkillWeb & browsingRun mobile responsive QA for websites and apps. Use after layout, media, navigation, form, pricing, dashboard, gallery, checkout, or motion changes to inspect phone and tablet viewports, prevent horizontal overflow, fix crop issues, verify touch targets, and make mobile feel intentionally composed.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Mobile Responsive QA skill
What this skill tells your AI
The instructions your AI receives, as published by thegoat395/codex-skills in skills/mobile-responsive-qa/SKILL.md and read by ahel’s review.
Use this skill to catch mobile problems that make otherwise premium sites feel rushed.
Workflow
- Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
- Read Mobile Responsive QA Guide before claiming the site is ready.
- Inspect affected phone/tablet navigation and input states: menu focus, touch affordances, virtual-keyboard occlusion, sticky controls, orientation and overflow where relevant. Distinguish emulation from real-device evidence.
- Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
- Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
Scoped execution
Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
Scope and evidence
Record width emulation separately from real touch/device/virtual-keyboard evidence. Use $responsive-visual-polish-qa for broad breakpoint composition; do not claim real-device certification from emulation.
Signals
- GitHub stars
- 124
- Forks
- 48
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
mobile-responsive-qa- Source
- github.com/thegoat395/codex-skills