ios-ui-verification

Verify iOS simulator UI, debug accessibility interactions, and measure control contrast.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/patrickserrano/lacquer --skill ios-ui-verification-patrickserrano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ios-ui-verification
Source: https://github.com/patrickserrano/lacquer/tree/main/profiles/ios/skills/ios-ui-verification
Command: npx skills add https://github.com/patrickserrano/lacquer --skill ios-ui-verification-patrickserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reading and driving iOS simulator UI through screenshot loops is slow, token-expensive, and imprecise, and accessibility interaction errors like element_disabled are easy to misdiagnose. This Skill provides rules for verifying simulator UI via accessibility element trees, recovering from interaction failures, and auditing non-text contrast against WCAG 1.4.11. ## Core Features & Use Cases - Simulator UI Verification: Read screens with rocketsim elements --agent-mode and act on elements by id, using FlowDeck's tree output or screenshots only as fallbacks. - Accessibility Interaction Debugging: Recover from element_disabled tap errors using interact activate, and treat !perception and !ambiguous snapshot rows as real accessibility findings. - Contrast & Performance Auditing: Measure design-token border contrast against actual backgrounds (≥ 3:1 per WCAG 1.4.11) and apply Swift 6 concurrency, iOS 26 API, and battery/performance rules. - Use Case: While testing a settings screen, a tap on an iCloud sync toggle returns element_disabled; use rocketsim interact activate to present the sheet and confirm the toggle's value correctly stays unchanged. ## Quick Start Verify the current simulator screen by reading its accessibility element tree and tapping the login button by element id.

Frequently Asked Questions about ios-ui-verification

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

FAQPage Schema
How do I verify iOS simulator UI without screenshots?▼

Use `rocketsim elements --agent-mode nav` to read the screen as a compact accessibility element tree, then act on elements by id. Where RocketSim is unavailable, `flowdeck ui simulator screen --tree --json` returns similar text output; screenshots are only a fallback for genuinely visual questions.

Why does rocketsim tap return element_disabled on an enabled element?▼

The error code is a misnomer; the message means the element did not change state after tapping, which happens with controls that present sheets instead of toggling. Recover with `rocketsim interact activate`, which performs an accessibility press rather than a HID touch.

RocketSim vs FlowDeck for iOS simulator UI testing?▼

RocketSim's agent-mode element tree is the default for reading and driving UI, while FlowDeck remains mandatory for build, run, test, logs, and simulator management. FlowDeck's tree output is an alternative reader only where RocketSim is not installed.

How do I check SwiftUI control border contrast for WCAG compliance?▼

Measure the border token against the actual background it sits on and assert at least 3:1 per WCAG 1.4.11, since a fixed white opacity composites differently per ground. White at 40% opacity is the lowest round value clearing common dark backgrounds; assert the ratio in a test.

Can I reuse element ids across multiple simulator snapshots?▼

No, element ids are ephemeral and stable only within one snapshot. Re-snapshot before acting on any id you did not just read, or the interaction may target the wrong element.