How do I install the IOS Simulator Triage skill?

Run npx skillmds@latest add simiancraft/ios-simulator-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is IOS Simulator Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with IOS Simulator Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is IOS Simulator Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published IOS Simulator Triage?

simiancraft (@simiancraft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

IOS Simulator Triage by simiancraft

Name: IOS Simulator Triage
Author: simiancraft

IOS Simulator Triage

Diagnose and recover from failures when building, running, or driving an app on the iOS Simulator. A living catalog organized by layer: build failures (xcodebuild, CocoaPods, signing, codegen), runtime failures split into app-runtime vs Expo-runtime (the red error overlay), and automation failures that emit no error (element not found in the accessibility tree, stuck flow). Each layer names where its logs live. Used alongside ios-simulator and expo-ios-simulator when something breaks. Project-agnostic.

simiancraft f89f951 5 files · 16.3 KB Updated Sep 17, 2026

File contents

iOS Simulator Triage (living failure catalog)

Classify first (which layer failed), then recover. Most fixes live in the sibling skills; this skill routes you to them and supplies the logging tools that turn a symptom into a cause.

Route by symptom

It never installs or launches (xcodebuild, CocoaPods, or prebuild failed): a build failure -> references/build-failures.md.
It launches, then crashes or misbehaves: a runtime failure -> references/runtime-failures.md, split into app-native and Expo / React-Native because the logs and the fixes differ.
It runs, but AXe cannot find or tap the element: an automation failure -> references/automation-failures.md.

Read the logs first

Every layer has a log that names the cause; guessing without it wastes a cycle. references/logging.md is the cross-cutting tool, indexed by layer: the unified log (simctl spawn booted log stream), the app's stdout and stderr (simctl launch --console), crash reports, the diagnostic bundle (simctl diagnose), and the Metro terminal for the JS layer.

Rules

Identify the layer before changing anything; a build fix will not cure a runtime crash.
Pull the log before forming a hypothesis; the unified log or the crash report usually names the cause outright.
Every factual claim here and in the references cites a primary source (the tools' own help, Apple); a prior-art skill is never a source.

Out of scope

Happy-path driving -> ios-simulator and expo-ios-simulator. What makes an app addressable -> mobile-accessibility.

Where to go

references/build-failures.md: code signing, CocoaPods, prebuild, and architecture.
references/runtime-failures.md: native crashes and the Expo / RN failure modes.
references/automation-failures.md: empty describe-ui, missed taps, and blocking overlays.
references/logging.md: the unified log, console output, crash reports, and diagnose.

---name: ios-simulator-triagedescription: Diagnose and recover from failures when building, running, or driving an app on the iOS Simulator. A living catalog organized by layer: build failures (xcodebuild, CocoaPods, signing, codegen), runtime failures split into app-runtime vs Expo-runtime (the red error overlay), and automation failures that emit no error (element not found in the accessibility tree, stuck flow). Each layer names where its logs live. Used alongside ios-simulator and expo-ios-simulator when something breaks. Project-agnostic.---# iOS Simulator Triage (living failure catalog)Classify first (which layer failed), then recover. Most fixes live in the sibling skills;this skill routes you to them and supplies the logging tools that turn a symptom into a cause.## Route by symptom- **It never installs or launches** (xcodebuild, CocoaPods, or prebuild failed): a **build failure** -> `references/build-failures.md`.- **It launches, then crashes or misbehaves**: a **runtime failure** -> `references/runtime-failures.md`, split into app-native and Expo / React-Native because the logs and the fixes differ.- **It runs, but AXe cannot find or tap the element**: an **automation failure** -> `references/automation-failures.md`.## Read the logs firstEvery layer has a log that names the cause; guessing without it wastes a cycle.`references/logging.md` is the cross-cutting tool, indexed by layer: the unified log(`simctl spawn booted log stream`), the app's stdout and stderr (`simctl launch --console`),crash reports, the diagnostic bundle (`simctl diagnose`), and the Metro terminal for the JSlayer.## Rules- Identify the layer before changing anything; a build fix will not cure a runtime crash.- Pull the log before forming a hypothesis; the unified log or the crash report usually names the cause outright.- Every factual claim here and in the references cites a primary source (the tools' own help, Apple); a prior-art skill is never a source.## Out of scopeHappy-path driving -> **ios-simulator** and **expo-ios-simulator**. What makes an appaddressable -> **mobile-accessibility**.## Where to go- `references/build-failures.md`: code signing, CocoaPods, prebuild, and architecture.- `references/runtime-failures.md`: native crashes and the Expo / RN failure modes.- `references/automation-failures.md`: empty `describe-ui`, missed taps, and blocking overlays.- `references/logging.md`: the unified log, console output, crash reports, and diagnose.

Frequently asked questions