ios-simulator-skill

Automate iOS app build, testing, and simulator UI via accessibility-driven navigation.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Roy-wonji/claude-config --skill ios-simulator-skill-roy-wonji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-simulator-skill
Source: https://github.com/Roy-wonji/claude-config/tree/main/skills/ios-simulator
Command: npx skills add https://github.com/Roy-wonji/claude-config --skill ios-simulator-skill-roy-wonji

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates fragile, screenshot-based iOS simulator automation by using accessibility tree navigation for reliable building, testing, interaction, and CI-friendly reporting.

Core Features & Use Cases

  • Accessibility-first navigation: Find and interact with UI elements by text, type, or accessibility ID instead of pixel coordinates.
  • Production-grade automation scripts: Build/test with xcresult parsing, semantic tapping/typing, accessibility audits, and state snapshots for debugging.
  • Simulator lifecycle management: Boot, shutdown, create/delete/erase simulators, plus environment health checks and token-efficient outputs for AI agents.
  • Verification tooling: Visual diffing, screenshot/a11y snapshots per step, and structured summaries for rapid diagnosis.

Quick Start

Run accessibility audit on the currently booted simulator by executing the command: python scripts/accessibility_audit.py --verbose.

Frequently Asked Questions about ios-simulator-skill

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

FAQPage Schema
How do I automate iOS simulator UI testing without relying on fragile screenshot comparisons?

Automate iOS simulator UI testing by using accessibility tree navigation to find and interact with elements by text, type, or accessibility ID instead of pixel coordinates. This semantic approach provides reliable end-to-end test flows and eliminates brittle screenshot-based automation.

What's the best way to run an accessibility audit on a booted iOS simulator?

Run an accessibility audit on the currently booted iOS simulator by executing the provided scripts with the verbose flag. This generates semantic element mapping and accessibility compliance checks for rapid diagnosis.

Can I manage the iOS simulator lifecycle and parse xcresult files in a CI/CD workflow?

Yes, you can manage the iOS simulator lifecycle by booting, shutting down, creating, deleting, and erasing simulators. The scripts parse xcresult files and provide token-efficient outputs, making them suitable for CI/CD workflows and regression verification.

Does iOS simulator automation support machine-readable output for AI agents?

Yes, iOS simulator automation supports optional JSON and verbose modes for machine parsing and detailed debugging. This provides structured summaries and state snapshots that are token-efficient for AI agents.

How do I debug failing end-to-end test flows in the iOS simulator?

Debug failing end-to-end test flows by using state snapshots, visual diffing, and screenshot or accessibility snapshots captured per step. These verification tools provide structured summaries for rapid diagnosis of simulator UI automation issues.