device-test

Run structured visual UI tests on mobile devices to detect layout defects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thomasttvo/claude-skills --skill device-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: device-test
Source: https://github.com/thomasttvo/claude-skills/tree/main/skills/device-test
Command: npx skills add https://github.com/thomasttvo/claude-skills --skill device-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile UI regressions and layout defects are hard to detect across device states and physical hardware; this Skill provides a structured way to exercise screens, capture visuals, and produce deterministic layout assessments so teams can catch keyboard overlap, modal issues, and spacing defects before releases.

Core Features & Use Cases

  • Screen-driven testing: Use ask_screen to list visible elements and obtain coordinates for reliable tap and swipe actions.
  • Device control with UDID: Execute interactions (tap, swipe) targeted at specific devices to avoid conflicts and reproduce physical-device bugs.
  • Visual QA integration: Inject expected layout context into visual-qa analysis to detect hidden elements, spacing defects, and deviations from design artifacts like Figma.
  • Use Case: Verify that the submit button remains visible when the keyboard opens across multiple device orientations and OS versions.

Quick Start

Use the device-test skill to run a UI test case named login-keyboard on device UDID abc123 and verify that the submit button is not hidden by the keyboard.

Frequently Asked Questions about device-test

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

FAQPage Schema
How do I run visual UI tests on real mobile devices to detect layout defects?

To run visual UI tests on real mobile devices, use screen capture to list visible elements and execute targeted tap or swipe interactions to reproduce layout and spacing defects across physical hardware.

How do I test if a mobile keyboard overlaps UI elements across different device orientations?

You can test keyboard overlap by executing device control actions like tap and swipe targeted at specific device UDIDs, capturing the screen, and analyzing the layout to verify the submit button remains visible.

Can I compare mobile app screens against Figma designs for spacing and layout regressions?

Yes, you can compare mobile app screens against Figma designs by injecting expected layout context into visual QA analysis to detect hidden elements, spacing defects, and deviations for deterministic pass/fail results.

How do I target interactions to a specific physical mobile device to reproduce hardware bugs?

You can target interactions to a specific physical mobile device by using its unique UDID in your device control actions, ensuring tap and swipe commands execute on the correct hardware without conflicts.

What is the best way to automate modal layout testing on physical mobile hardware?

The best way to automate modal layout testing on physical hardware is using screen-driven tests that capture visible element coordinates and inject expected layout context to assess spacing and layout deterministically.

Why do I need to capture screen elements before performing tap and swipe actions in mobile UI testing?

You need to capture screen elements first to obtain accurate coordinates for reliable tap and swipe actions, ensuring your mobile UI testing interactions hit the correct targets and reproduce layout defects.