agentsclimarketplace

Ios simulator triage

Skill simiancraft/simiancraft-skills/skills/ios-simulator-triage

Public Claude Code skills and agents from simiancraft. Marketplace-installable.

Install
npx -y skills add simiancraft/simiancraft-skills --skill ios-simulator-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.7 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.