TheGoat395/Codex-Skills / skills/mobile-responsive-qa
mobile-responsive-qa
VerifiedVerify phone/tablet input and navigation flows.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
| agents/openai.yaml | config | 258 B |
| references/mobile-responsive-qa-guide.md | markdown | 2.2 KB |
SKILL.md
View on GitHub---
name: mobile-responsive-qa
description: "Verify phone/tablet input and navigation flows."
---
# Mobile Responsive QA
Use this skill to catch mobile problems that make otherwise premium sites feel rushed.
## Workflow
1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
2. Read [Mobile Responsive QA Guide](references/mobile-responsive-qa-guide.md) before claiming the site is ready.
3. 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.
4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
## Scoped execution
Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |