Agent skill · vasilyu1983
software-ios-runtime-debugging
Proves iOS build/install/launch truth and triages hangs, crashes, jank, memory kills, and stale builds. Use when simulator, bundle, or runtime performance state is in doubt.
What it needs
About 12k tokens when loaded.
What this skill does
Native iOS Runtime Debugging Use this skill when the core problem is not app architecture or visual design, but runtime truth: did the current binary build, install, launch, and render on the intended simulator or device — and once that's proven, is the live complaint a hang, a crash, jank, a memory kill, or a launch-time regression? This skill owns stale-build suspicion, simulator drift, malformed .app bundles, missing executables, XcodeGen resource packaging mistakes, and the proof loop required before trusting screenshots, UI behavior, or downstream API/auth debugging. It also owns classifying and diagnosing live runtime performance and stability complaints once that proof exists: hangs and watchdog kills, crash symbolication, jank against frame budgets, Jetsam/memory pressure, and launch-time measurement traps. Quick Reference Symptom First Move Notes -------- ------------ ------- Screenshot does not match source Uninstall -> install -> launch Assume stale app first Tool cannot read a simulator screenshot temp path Re-capture from the current simulator Temp screenshot files expire or move. Do not treat a missing temp path as invalidating the user's visible report Install says app is missing executable Inspect built .app bundle Verify Info.plist and executable path before touching Swift Simulator behaves inconsistently Prove destination, boot, install, launch state Do not debate UI until runtime truth exists XcodeBuildMCP is unavailable Fall back to xcodebuild, simctl, xcresulttool Switch immediately Auth appears to succeed but next screen is unauthenticated Inspect token persistence and auth propagation after fresh launch Do not redesign UI first Push works on Xcode build but fails on TestFlight Inspect archived entitlements and newest backend device row Wrong APNs environment is more likely than feature-code regression APNs returns BadDeviceToken for older installs Check device-row environment and staleness first Often stale tokens or env mismatch, not a curren …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vasilyu1983/software-ios-runtime-debugging