ios-simulator-nav

Navigate iOS Simulator UI via accessibility labels and axe CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill ios-simulator-nav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-simulator-nav
Source: https://github.com/ElvinOuyang/claude-skill-collection/tree/main/plugins/ios-dev-toolkit/skills/ios-simulator-nav
Command: npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill ios-simulator-nav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about ios-simulator-nav

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

FAQPage Schema
How do I tap buttons in iOS Simulator reliably without coordinate guessing?

To tap buttons in iOS Simulator reliably, use AXe CLI to perform accessibility-based UI actions that target elements by AXUniqueId or labels instead of brittle screen coordinates. This approach eliminates flaky interactions by hitting real UI elements directly.

What is the best way to automate SwiftUI tab navigation in iOS Simulator?

The best way to automate SwiftUI tab navigation is using AXe CLI for accessibility-first interactions. When SwiftUI tab items lack accessibility labels, you fall back to a living coordinate map in SIMULATOR_MAP.md to maintain deterministic taps.

Why does my iOS Simulator UI automation fail after a layout change?

iOS Simulator UI automation fails after layout changes due to stale mappings or missing accessibility labels. You can fix this by verifying the environment state via UDID, re-running UI inspection with AXe describe-ui, and updating SIMULATOR_MAP.md for unmapped elements.

Can I use AXe CLI to fill forms and type text in iOS Simulator apps?

Yes, you can use AXe CLI to fill forms and type text in iOS Simulator apps by targeting real UI elements through accessibility labels or ids. This applies to simulator workflows including swiping, taking screenshots, and verifying post-action UI states.

How do I handle iOS Simulator elements missing from the accessibility tree?

For iOS Simulator elements missing from the accessibility tree like custom-drawn controls, you maintain a living coordinate map in SIMULATOR_MAP.md. This fallback ensures deterministic interactions when accessibility-based navigation is unavailable.