Test on real mobile devices and viewports

SkillDev tools

mobile-testing is a skill that guides an AI agent to review whether websites are tested on real mobile devices and screen sizes. It is used when checking CI coverage, automated checks, or test strategy, with a focus on whether each rule is continuously verified rather than just documented.

Available today. Use it from your connected AI after setup.

Have an AI agent that can load skills.

Then ask your AI: use the Test on real mobile devices and viewports skill

What your AI can do with it

  • Review CI coverage for mobile device and viewport testing
  • Assess automated checks related to real mobile devices
  • Evaluate test strategy for different screen sizes
  • Check whether rules are continuously verified, not just documented

Getting started

  1. Have an AI agent that can load skills.
  2. Add the mobile-testing skill to the agent's available skills.
  3. Ask the agent to review CI coverage, automated checks, or test strategy for mobile device and viewport testing.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/mobile-testing/SKILL.md and read by ahel’s review.

More than 55% of global web traffic comes from mobile devices. Mobile browsers have different rendering engines, different font rendering, limited memory, real touch events that differ from mouse events, and system UI (notch, home indicator, keyboard) that intrudes on your layout. Issues like sticky hover states, touch target sizes, and keyboard layout shifts only appear on real devices.

Quick Reference

  • Desktop DevTools device emulation catches layout issues but not real touch behavior
  • Test on at least one Android (Chrome) and one iOS (Safari) real device
  • Test common viewport breakpoints: 375px (iPhone SE), 390px (iPhone 14), 768px (iPad)
  • Use BrowserStack or similar services for testing on devices you don't own

Check

Does this project have any mobile-specific test configurations? Check for Playwright device emulation, mobile viewport tests, or notes about mobile testing.

Fix

Add Playwright tests using mobile device presets to cover key user flows on mobile viewports.

Explain

Explain the difference between DevTools emulation and real device testing, common mobile-specific issues to test for, and how to use Playwright's device emulation.

Code Review

Review tests, CI workflows, and enforcement points related to Test on real mobile devices and viewports. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/testing/mobile-testing

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

When should this skill be used?
Use it when reviewing CI coverage, automated checks, or test strategy related to testing on real mobile devices and viewports.
What does the skill focus on?
It focuses on whether each rule is continuously verified, not just documented.
Does it run the mobile tests itself?
No. It guides the agent to review whether websites are tested on real mobile devices and screen sizes.
Advanced
Item type
skill
Key
mobile-testing-thedaviddias
Source
github.com/thedaviddias/front-end-checklist