axe

Automate iOS Simulator UI interactions by dispatching AXe CLI commands.

Updated Aug 27, 2026

Search Tags:#ios #ui testing #batch workflows #accessibility tree #axe cli #simulator automation

Ready to run

npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill axe-elvinouyang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axe
Source: https://github.com/ElvinOuyang/claude-skill-collection/tree/main/plugins/ios-dev-toolkit/skills/axe
Command: npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill axe-elvinouyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork in iOS Simulator automation by showing how to reliably find UI elements and trigger the right interactions so you can validate outcomes.

Core Features & Use Cases

UI discovery for automation: Use axe list-simulators and axe describe-ui to target the correct Simulator UDID and inspect available identifiers like --id and --label.
Deterministic simulator actions: Perform taps, swipes, gestures, text entry, keyboard input, screenshots, video capture, and more using AXe CLI commands.
Robust multi-step flows: Use axe batch with --wait-timeout, polling, and delay controls to handle navigation and transitions safely.

Quick Start

Ask your agent to tap the login button in the current iOS Simulator screen by running: axe tap --label "Log In" --udid <UDID>.

Frequently Asked Questions about axe

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

FAQPage Schema

How do I automate iOS Simulator UI interactions for login and onboarding flows?▼

Automate iOS Simulator UI interactions by finding accessibility elements and dispatching AXe CLI commands for taps, gestures, and input. Use axe describe-ui to select --id or --label selectors, then execute actions like axe tap to drive login and onboarding flows.

What is the best way to find UI elements for iOS simulator automation?▼

Finding UI elements for iOS simulator automation uses the axe describe-ui command to inspect available accessibility identifiers. You target elements by selecting the correct Simulator UDID with axe list-simulators, then choosing the appropriate --id or --label selector.

How do I prevent timing failures during multi-step iOS simulator automation?▼

Prevent timing failures during multi-step iOS simulator automation by using axe batch with --wait-timeout and delay controls. These features handle navigation transitions safely by polling and waiting for UI elements to appear before executing the next action.

Can I capture screenshots and video during iOS simulator testing?▼

You can capture screenshots and video during iOS simulator testing using AXe CLI commands. The automation tool supports media capture alongside standard UI interactions like taps, swipes, and text entry to validate outcomes within your end-to-end mobile workflow.

Does iOS simulator automation require a specific Simulater UDID?▼

Yes, iOS simulator automation requires selecting the correct Simulator UDID before executing actions. You retrieve available UDIDs by running the axe list-simulators command, ensuring your taps, gestures, and text inputs target the intended simulator instance.