Browser and device QA

Verifies responsive layouts and real interactions across specified browser sizes, input methods and navigation states.

browser-cross-device-qa

See how it helps

When is it useful?

Use when a web feature needs checking beyond a single desktop screenshot.

What does it help you do?

Checks action visibility, zoom, long content and table overflow.
Exercises touch, pointer and keyboard interactions without hover-only dependencies.
Tests reload, history and cross-tab state while recording actual environments.

Try asking this

Check our settings dialog at phone and desktop widths, enlarged text and touch, including logout in another tab. A logged-out second tab must not let the first tab silently save stale credentials. Verify that errors and recovery actions remain reachable at phone width.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Browser & Cross-Device QA

Use this skill when verifying web and responsive interfaces across desktop and mobile viewports, input modalities, and browser environments.

Workflow

Viewport and responsive layout verification:
- Check key breakpoints (mobile 320px–390px, tablet 768px, laptop 1280px, wide desktop 1920px+) and 200% browser zoom:
  - Verify that primary actions (Save, Submit, Cancel, Close, navigation controls) remain visible, clickable, and never clipped off-screen or hidden behind sticky headers/footers.
  - Check long unbroken strings (URLs, emails, file names, UUIDs) and large tables/lists for horizontal overflow or broken flex/grid layouts.
Input modality & interaction checks:
- Pointer vs. touch vs. keyboard:
  - Features relying on :hover must remain operable on touchscreens where hover does not exist.
  - Verify tab order, Escape/Enter handling in dialogs and forms, and visible focus indicators (handing deep WCAG audits to the accessibility specialist).
Browser navigation, storage, and lifecycle behavior:
- Test URL deep-linking, query-parameter persistence across page reloads, and browser Back/Forward history transitions.
- Check behavior across multiple open tabs (e.g., signing out or switching workspace in one tab while another tab is active).
- Inspect browser DevTools Console and Network panels during testing to catch uncaught promise rejections, failed asset loads, CORS errors, or hydration mismatches even when the UI appears visually intact.
Honest environment reporting:
- State explicitly which browsers, viewports, or emulated devices were actually tested, and never claim cross-browser or physical-device compatibility that was not verified.

Included files 1

SKILL.md