interactive-simulator-ux-auditlisted

Use when auditing an iOS/iPadOS app's live behavior in the Simulator — navigation, modals, back-stack, completion flows, safe-area/Dynamic-Island clipping, offline or signed-out states — bugs a fixed-size snapshot render structurally cannot show. Covers installing `idb` without Homebrew (direct GitHub release + an exec wrapper that preserves rpath), the describe-all → tap → screenshot drive loop, device-point vs screenshot-pixel coordinate spaces, and the "stale build" / "worktree launch crash" false-negative traps. Use when asked to "test the UI", "find UX problems", "drive the simulator", or verify an interactive flow end-to-end.
wei18/apple-dev-skills · ★ 0 · Web & Frontend · score 70

Install: claude install-skill wei18/apple-dev-skills

# Interactive Simulator UX Audit (idb-driven) Snapshot tests render a view in a fixed-size `NSHostingView` — they model neither navigation, taps, the device safe area, nor the Dynamic Island. A whole class of bugs only shows when something actually drives the app: a screen that never appears after a selection, a flow that's unplayable when the user is signed out of a cloud account, completion content clipped by the Dynamic Island. This skill is the audit loop that catches those, using `idb` (Facebook's iOS Simulator automation tool) to tap, read the accessibility tree, and capture screenshots against a **booted** Simulator. ## When to invoke - Asked to "test the UI", "find UX problems", or "drive the simulator". - Verifying a navigation, modal, or completion flow actually renders end-to-end after a code change. - Auditing safe-area / Dynamic-Island layout, or an offline / signed-out flow, that snapshot tests can't model. - Debugging a report that only reproduces "in the app," not in any test. ## Scope Owns: live Simulator driving via `idb`, the audit loop, and the coordinate/build gotchas below. Does **not** own: scripted, CI-run UI tests that launch and assert without a human watching → `host-driven-xcuitest-e2e`; static pixel-diff regression gates → `swift-testing-baseline`. Use this skill first to *find* a bug interactively; write a host-driven XCUITest afterward to *pin* the fix. ## Prereq: install `idb` (one-time, not via Homebrew) If your project's policy forbids