SkillScan: pass
Responsive Testing
Open the app in the harness's browser tool at multiple viewport sizes, screenshot each, and report layout breakage. Use after UI layout changes or when the user asks to verify responsive behavior.
Add a trust badge to your README
[](https://waxmark.app/items/responsive-testing/scan)
---
name: responsive-testing
description: >-
Open the app in the harness's browser tool at multiple viewport sizes,
screenshot each, and report layout breakage. Use after UI layout changes or
when the user asks to verify responsive behavior.
user-invocable: true
disable-model-invocation: true
---
# Responsive Testing
After a UI change, verify the page at the standard breakpoints.
## Runtime requirements
- A browser tool with viewport resizing and a running dev server. See the tool mapping in `visual-qa-testing`. Resizing is `browser_resize` (or `browser_cdp` with `Emulation.setDeviceMetricsOverride`) in Cursor, `resize_window` in Claude Code, and `browser_resize` in Playwright MCP.
- Works fully in local agents. Cloud Agents need the app runnable in the VM with browser access.
- If the environment cannot run the app or open a browser, say so and skip.
## Viewports
| Name | Width | Height | Tailwind |
|------|------:|-------:|----------|
| Mobile (small) | 375 | 812 | default |
| Mobile (large) | 428 | 926 | default |
| Tablet | 768 | 1024 | `md:` |
| Desktop | 1280 | 800 | `xl:` |
| Ultrawide | 1536 | 900 | `2xl:` |
Skip widths the project explicitly does not support if `AGENTS.md` says so.
## Workflow
1. Navigate to the changed route using the dev server URL from `AGENTS.md`.
2. For each viewport: resize, screenshot, and read the accessibility tree.
3. Check for:
- **Overflow:** elements wider than the viewport, horizontal scrollbars
- **Stacking:** flex or grid items that should stack on mobile but do not
- **Hidden content:** elements that vanish at a breakpoint with no menu toggle
- **Navigation:** menus that should collapse into a hamburger
- **Touch targets:** buttons or links too small or too close together
- **Font scaling:** text readable on desktop but tiny on mobile
- **Fixed positioning:** modals, toasts, sticky headers that break on small screens
- **Images:** oversized images that do not scale down
4. Reset the viewport to the harness default when finished.
5. Report:
```
Responsive: /dashboard
375px PASS
428px PASS
768px WARN — nav items overlap, needs hamburger
1280px PASS
1536px WARN — content not centered
```
Fix issues you introduced, then re-test only the affected widths.
## Related skills
- `visual-qa-testing` — single-viewport QA with console and network checks
- `dark-mode-testing` — theme verification at each breakpoint