What problem does it solve? Verifying iOS app changes normally requires juggling raw xcodebuild, xcrun, and simctl commands, guessing simulator states, and tapping blind coordinates. This Skill standardizes the whole loop through the repository-configured XcodeBuildMCP server so builds, launches, UI interaction, and log capture stay pinned to one explicit simulator. ## Core Features & Use Cases - Pinned Simulator Sessions: Establish one simulator UDID via session defaults so every build, launch, screenshot, and UI action targets the same device. - Semantic UI Automation: Drive the app through accessibility snapshots and element references instead of coordinates, with wait_for_ui for asynchronous transitions. - Focused Builds, Tests, and Logs: Run build_run_sim, targeted test_sim cases, and bundle-scoped log capture for runtime diagnosis. - Use Case: After changing native code in a T3 Code Mobile feature, build and launch on a booted simulator, snapshot the UI, tap through the affected flow using element references, and capture a final screenshot proving the fix. ## Quick Start Use the ios-debugger-agent skill to build and launch the current iOS app on a booted simulator, then snapshot the UI and verify the login flow with a screenshot.
