iOS Visual Explore

When to use

Use this skill as a Tier-2 escalation after standard accessibility-based testing has already been attempted or is insufficient:

• Visual or layout regressions that accessibility assertions cannot detect
• Flows driven by visual landmarks (images, icons, colour cues) rather than labels
• Exploratory missions ("find any visual issues on the onboarding flow") where the goal is open-ended
• Debugging a user-reported visual issue that doesn't reproduce in unit tests

Do not use as a first resort — prefer deterministic XCUITest flows when the app's accessibility tree is well-formed.

Prerequisites

• A booted iOS simulator (or physical device via idb) with the target app installed
• idb_companion available on PATH (or installed via Homebrew)
• GEMINI_API_KEY / gemini-api-key-paid in macOS Keychain (for the Gemini vision backend)
• uv available on PATH (for the shim runner)