gesture-diagnostics

Diagnoses touch and gesture issues in Android Chrome PWAs via emulator-based workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/matthewfrazier/mobissh --skill gesture-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gesture-diagnostics
Source: https://github.com/matthewfrazier/mobissh/tree/main/.claude/skills/gesture-diagnostics
Command: npx skills add https://github.com/matthewfrazier/mobissh --skill gesture-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic methodology for diagnosing touch and gesture issues in PWAs running on Android Chrome via emulator. Gesture bugs are the hardest class of issues because they can pass synthetic tests but fail on real devices, and debugging is compounded by limited DevTools on mobile environments.

Core Features & Use Cases

  • Static Analysis: detect common misconfigurations and problematic event handling before emulator testing.
  • Emulator-to-Device Validation: guide from isolated unit tests to full device validation, including per-feature isolation and direction-aware assertions.
  • Debug Overlay & Structured Workflow: provide a repeatable process to diagnose, reproduce, and fix gesture interactions in PWAs.

Quick Start

Begin by running Phase 1 static analysis to identify common gesture bugs, then proceed through unit and emulator tests, and finally validate with real-device testing using the provided gating strategy.

Frequently Asked Questions about gesture-diagnostics

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

FAQPage Schema
Why do my Android PWA gesture tests pass on an emulator but fail on real devices?

Android PWA gesture issues often pass synthetic emulator tests but fail on real devices due to touch input differences. This Skill isolates these discrepancies using static analysis, unit tests, emulator isolation, and device validation with feature gating.

How do I debug touch event handling in a PWA running on Android Chrome?

Debugging touch events in Android Chrome PWAs requires a structured workflow. This Skill applies static analysis to detect misconfigurations, then proceeds through unit tests, emulator isolation, and direction-aware assertions to reproduce and fix gesture interactions.

What is the best way to isolate a new gesture feature for diagnostics in a PWA?

To isolate new PWA gesture features, apply per-feature isolation and direction-aware assertions during emulator testing. This Skill enforces a structured workflow that guides from isolated unit tests to full device validation using a specific gating strategy.

Do I need real Android device testing to diagnose PWA touch issues, or can I rely on the emulator?

Emulator testing is insufficient alone for PWA touch issues. This Skill uses an emulator-to-device validation workflow, applying feature gating and directional assertions to ensure gesture interactions work correctly when transitioning from emulator isolation to real device testing.

Can static analysis detect common gesture misconfigurations before emulator testing?

Static analysis can detect common gesture misconfigurations and problematic event handling before emulator testing begins. This Skill enforces static analysis as Phase 1, identifying potential touch bugs early before proceeding to unit tests and device validation.

What limitations exist when debugging gestures on mobile environments with limited DevTools?

Debugging PWA gestures on mobile environments is compounded by limited DevTools access. This Skill mitigates these limitations by providing a structured diagnostic workflow, debug overlay, and repeatable process to systematically reproduce and fix gesture interactions despite tooling constraints.