mobile-parity

Validate desktop and mobile UI parity with Playwright E2E tests.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill mobile-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-parity
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/mobile-parity
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill mobile-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that UI features work consistently across desktop and mobile devices, with responsive behavior and comprehensive end-to-end testing.

Core Features & Use Cases

  • Responsive UI Verification: Checks for parity in UI features across desktop and mobile.
  • End-to-End Testing: Adds or updates Playwright tests for mobile-specific scenarios.
  • Use Case: When developing a new feature, use this Skill to verify that it works seamlessly on both desktop and mobile platforms.

Quick Start

Run the mobile parity check for the 'feature-x' task to ensure UI parity.

Frequently Asked Questions about mobile-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure UI parity between desktop and mobile when developing new frontend features?

To ensure UI parity between desktop and mobile, you can validate responsive design principles and execute Playwright end-to-end tests to verify that new features work consistently across both platforms.

Can I use Playwright to test mobile-specific functionality for responsive web applications?

Yes, you can use Playwright to add or update end-to-end tests specifically for mobile scenarios, validating that your responsive UI features function correctly on mobile devices.

What is the best way to verify cross-platform consistency for a new UI feature?

The best way to verify cross-platform consistency is to run responsive design checks and Playwright E2E tests together, confirming that desktop and mobile interfaces maintain visual and functional parity.

Do I need responsive design knowledge to automate mobile E2E testing?

Yes, responsive design knowledge is required to effectively automate mobile E2E testing, as it provides the necessary context to validate cross-platform UI behavior and ensure accurate mobile-specific test coverage.

Why does my UI feature work on desktop but break on mobile during E2E testing?

UI features break on mobile during E2E testing when responsive design rules are not properly implemented, requiring you to run mobile parity checks to identify and resolve cross-platform layout inconsistencies.