axe

Automate iOS Simulator interactions with AXe CLI commands.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill axe-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axe
Source: https://github.com/Detrous/dotfiles/tree/main/pi/skills/axe
Command: npx skills add https://github.com/Detrous/dotfiles --skill axe-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AXe provides agent-ready guidance and tooling to automate iOS Simulator interactions, turning repetitive manual tasks into repeatable scripts and batch flows.

Core Features & Use Cases

  • Comprehensive command set: includes tap, swipe, type, describe-ui, screenshot, record-video, batch, and more for simulator automation.
  • Resilient element targeting: prefer --id / --label selectors over coordinates to work across device sizes and states.
  • Batch-driven workflows: run multi-step flows in a single process invocation to minimize latency and improve consistency.
  • Verification & debugging: validate outcomes with describe-ui and screenshot after actions to ensure expected results.
  • Use Case: automate a UI walkthrough on an iOS simulator, capture states, and export a test report.

Quick Start

Create and run a first AXe batch to tap a UI element on the simulator and verify the result with describe-ui.

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 tasks like tapping and swiping for UI testing?

Automate iOS simulator tasks using the AXe CLI to convert manual testing into repeatable scripts. It supports tapping, swiping, typing, describing the UI, taking screenshots, recording video, and batch workflows across simulators.

What is the best way to run multi-step UI testing flows on an iOS simulator?

Use AXe batch workflows to run multi-step UI testing flows in a single process invocation. This minimizes latency, improves consistency, and allows you to automate a complete UI walkthrough on an iOS simulator.

Does iOS simulator automation require a specific device UDID to run scripts?

Yes, AXe enforces UDID usage for all commands to ensure your automation scripts target the correct simulator instance. Providing the specific device UDID is required for both batch and discrete command execution.

How do I verify UI state and debug after automating an action on an iOS simulator?

Validate outcomes after automating actions by running describe-ui and screenshot commands. These allow you to capture the interface state and ensure your automated actions produced the expected results on the iOS simulator.

Can I capture screenshots and record video during iOS simulator automation?

Yes, AXe includes screenshot and record-video commands to capture visual states during iOS simulator automation. These features support verification and debugging throughout your automated batch workflows.

Why should I use label selectors instead of coordinates when scripting iOS simulator interactions?

Using --id and --label selectors instead of coordinates provides resilient element targeting for iOS simulator automation. This ensures your scripts work reliably across different device sizes and interface states without breaking.