ios-debugger-agent

Build and run iOS app schemes on a booted Simulator with UI inspection and log capture.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Roy-wonji/claude-config --skill ios-debugger-agent-roy-wonji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-debugger-agent
Source: https://github.com/Roy-wonji/claude-config/tree/main/skills/ios-debugger-agent
Command: npx skills add https://github.com/Roy-wonji/claude-config --skill ios-debugger-agent-roy-wonji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork involved in running an iOS app and diagnosing runtime issues by guiding the build, launch, UI inspection, and log capture process on a booted Simulator.

Core Features & Use Cases

  • Simulator discovery & setup: Selects a Booted simulator and configures the session with the correct workspace/project, scheme, and simulator ID.
  • Build, run, and launch: Runs the current scheme via XcodeBuildMCP, with support for handling build failures and re-attempting with safer preferences.
  • UI interaction for diagnosis: Uses UI description, screenshots, taps, typing, gestures, and re-describes UI when elements change.
  • Logs & console visibility: Captures runtime logs for the app bundle ID and summarizes important output for faster debugging.
  • Troubleshooting guardrails: Verifies app launch via UI describe/screenshot and resolves unknown bundle IDs using MCP lookups.

Quick Start

Ask the agent to run your iOS app on the currently booted Simulator, then inspect the screen and capture the relevant logs for debugging the issue you see.

Frequently Asked Questions about ios-debugger-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug an iOS app on a booted Simulator using XcodeBuildMCP?

To debug an iOS app on a booted Simulator, this Skill uses XcodeBuildMCP to set session defaults, build and run the resolved scheme, and enable interactive UI inspection. It captures runtime logs and screenshots to diagnose failures directly within the active Simulator environment.

What's the best way to inspect SwiftUI elements and capture runtime logs during simulator debugging?

For simulator debugging, the Skill describes UI elements, captures screenshots, and simulates taps or gestures. It captures runtime logs for the specific app bundle ID, allowing you to inspect SwiftUI elements and summarize important console output for faster troubleshooting.

How do I troubleshoot an iOS app that fails to launch during Xcode build and run?

To troubleshoot an iOS app launch failure, the Skill verifies the launch via UI description and screenshots. If the build fails, it re-attempts with safer preferences, and if the bundle ID is unknown, it resolves it using MCP lookups before capturing simulator logs.

Do I need a specific simulator state to run XcodeBuildMCP for iOS app diagnosis?

Yes, you need a Booted simulator. The Skill discovers booted simulators and configures the session with the correct workspace, project, scheme, and simulator ID to successfully build, run, and diagnose your iOS app.

Can I re-describe the UI when elements change after interacting with an iOS app?

Yes, the Skill re-describes the UI when elements change. After performing taps, typing, or gestures during iOS app diagnosis, it captures updated screenshots and UI descriptions to ensure accurate runtime inspection and troubleshooting.