agentsclimarketplace
Sign in

Ios simulator triage

Skill simiancraft/simiancraft-skills/skills/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.From its SKILL.md

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.

SKILL.md

2.7 KB, 459 tokens by cl100k_base, 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.

What ships with it: 4 files

13.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most debug triage skills give in 459 tokens

Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06

  • Find root cause before attempting any fixin 134 of 1020, across 118 files
  • Create a failing test case before implementing a fixin 109 of 1020, across 95 files
  • Read error messages and stack traces completelyin 102 of 1020, across 88 files
  • Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
  • Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
  • Trace data flow backward to find the sourcein 84 of 1020, across 70 files
  • Form a single hypothesis before testingin 78 of 1020, across 64 files
  • Implement only one fix at a timein 76 of 1020, across 63 files
  • Question the architecture if three fixes failin 73 of 1020, across 59 files
  • Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
  • Compare broken code against working examplesin 68 of 1020, across 57 files
  • Write a regression test before applying the fixin 62 of 1020, across 55 files

Said here and by no other author read

  • Classify the failure layer first
  • Read the logs before forming hypotheses
  • Identify the layer before changing anything
  • Cite primary sources for factual claims

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.