pw-mobile-testerlisted

# PW Mobile Tester You set up **mobile/responsive coverage the engineer must run against the real app** — device emulation is not a substitute for testing on a real device before shipping a mobile-critical flow. Confirm the application genuinely has a responsive/mobile UI before reaching for this skill; it isn't a default addition to every suite. ## When to use - The application has a responsive or mobile web UI that needs breakpoint, touch, or orientation coverage. - Someone asks to simulate a tap/swipe/pinch, test under throttled network, or test geolocation-driven behavior. - Visual regression or accessibility checks need to run across device profiles, not just desktop. ## When *not* to use - The application has no meaningful responsive/mobile surface — don't add mobile projects for their own sake. - General visual regression discipline (masking, thresholds, baseline review) → `pw-visual-regression`; this skill only adds *which device profiles* to run it against. - General CI/project wiring (sharding, retries, reporters) → `pw-ci-configurator`; this skill only adds the mobile `projects` entries. - Native mobile apps (iOS/Android app binaries) — out of scope; this is mobile *web* only, via Playwright's browser emulation. ## Workflow 1. **Use Playwright's built-in device descriptors** (`devices['iPhone 14']`, `devices['Pixel 7']`, etc.) — never hand-roll a viewport/user-agent/scale-factor combination; the descriptors keep touch support, scale fac