What problem does it solve?
It eliminates flaky, screenshot-driven coordinate guessing when tapping and verifying iOS Simulator UI by using accessibility-first interactions.
Core Features & Use Cases
- AXe label/id navigation: Tap, type, swipe, and screenshot using AXe CLI so interactions target real UI elements instead of screen pixels.
- SIMULATOR_MAP.md fallback: Maintain a living coordinate map for UI elements not present in the accessibility tree (e.g., SwiftUI tab items, custom-drawn controls).
- Session safety checks: Verify UDID and SIMULATOR_MAP freshness, then re-run UI inspection when taps fail to prevent drift and stale mappings.
Use case example: When a SwiftUI app changes layout and tabs stop being tappable by label, use AXe describe-ui to discover the element (or update SIMULATOR_MAP.md for elements that are not in the accessibility tree), then re-run the tap flow with mapped coordinates to restore determinism.
Quick Start
Use the ios-simulator-nav skill to tap a specific control in the iOS Simulator by accessibility label or id using axe, and update SIMULATOR_MAP.md immediately when a required element is not exposed in the accessibility tree.