ios-simulator_skill

Overview

This skill automates iOS Simulator workflows from the command line, designed for macOS and Xcode environments. It wraps xcrun simctl for simulator lifecycle and app management, and optionally uses idb for accessibility-driven UI inspection and interaction. The tool produces compact, machine-friendly output by default and supports human-readable modes when needed.

How this skill works

The skill exposes a Node CLI that issues simctl commands for listing, creating, booting, erasing, and deleting simulators, plus app install/launch/terminate and screenshots/video. When idb is available it queries the accessibility tree and can synthesize taps, typing, and semantic queries (find/tap/button). State (selected UDID) is stored in a local state file and commands accept explicit UDID overrides.

When to use it

• Run an app on an iOS Simulator from CI or a macOS node
• Take automated screenshots or record video of a simulator session
• Automate UI interactions using accessibility queries (requires idb)
• Install, uninstall, launch, or manage app containers on a simulator
• Grant/revoke privacy permissions or send simulated push notifications

Best practices

• Run commands on macOS with Xcode CLI tools installed and xcode-select configured
• Install idb for reliable accessibility inspection and semantic taps (brew + pip steps)
• Use the select command to write a default UDID state file for repeatable commands
• Prefer --udid for explicit targeting in CI or multi-simulator flows
• Treat erase/delete as dangerous and require --yes to avoid accidental data loss

Example use cases

• Set up a consistent simulator in CI: list -> select --boot -> app install -> app launch
• Automation test: boot simulator, install app, use ui find/tap/type to run a login flow, then screenshot
• Privacy testing: grant specific simulator permissions, run app behavior scenarios, then revoke or reset
• Push notification flow: send simulated push payloads to exercise notification handling in-app
• Diagnostics: capture logs, screenshots, or full UI tree for debugging flaky UI elements