Responsive QA Pass
$1.99OfficialSystematically test layouts across viewports, breakpoints, zoom, and orientation, then fix breakage. Use before shipping UI or when a layout breaks on a device.
frontendresponsivecssbreakpointsviewportqamobile· by SkillingMain
What you get
- ✓8-step procedure
- ✓Runnable JavaScript included
- ✓6-point quality checklist
- ✓7 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 4 min read
- Requires
- Works with any modern AI assistant
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes
Preview
When to use
Use after UI changes to verify layouts across screen sizes, when the user reports breakage on a specific device, before shipping landing or marketing pages, or when asked for a "responsive check", "mobile QA", or "does this work on phones". Also use when reviewing a PR that touches layout CSS, grids, or navigation.
Inputs to gather
- Pages or components in scope, plus a running dev URL.
- The project's defined breakpoints (design tokens, CSS custom properties, or framework config). If none are defined, use the default matrix below.
- Supported browser/device matrix and any devices with known issues.
- Whether browser automation is available (headless browser, screenshot
…
🔒 Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.