Ios Debugger Agent

by dimillian05ba982bfeb0No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 months ago

Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.

Instructions onlySoftware Development
AI-generated overview

Builds, runs, launches and debugs an iOS app on a booted simulator using XcodeBuildMCP tools.

What it does
Guides an agent through a fixed workflow with XcodeBuildMCP: discovering a booted simulator, setting session defaults, building and running the current scheme, and verifying launch. It also covers UI interaction such as describing the interface, tapping, typing, gestures and screenshots, plus capturing and summarizing simulator logs and console output. Troubleshooting steps address build failures, wrong app launches and non-hittable UI elements.
When to use it
Use it when asked to run an iOS app on a simulator, interact with the simulator UI, inspect on-screen state, capture logs or console output, or diagnose runtime behavior of an iOS project.
Requirements
Requires the XcodeBuildMCP MCP server with its simulator, build, UI and log tools available, plus an iOS project with a scheme and a simulator already booted. No scripts are shipped; the skill is instructions only.

iOS Debugger Agent

Overview

Use XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs. Prefer the MCP tools for simulator control, logs, and view inspection.

Core Workflow

Follow this sequence unless the user asks for a narrower action.

1) Discover the booted simulator

  • Call mcp__XcodeBuildMCP__list_sims and select the simulator with state Booted.
  • If none are booted, ask the user to boot one (do not boot automatically unless asked).

2) Set session defaults

  • Call mcp__XcodeBuildMCP__session-set-defaults with:
    • projectPath or workspacePath (whichever the repo uses)
    • scheme for the current app
    • simulatorId from the booted device
    • Optional: configuration: "Debug", useLatestOS: true

3) Build + run (when requested)

  • Call mcp__XcodeBuildMCP__build_run_sim.
  • If the build fails, check the error output and retry (optionally with preferXcodebuild: true) or escalate to the user before attempting any UI interaction.
  • After a successful build, verify the app launched by calling mcp__XcodeBuildMCP__describe_ui or mcp__XcodeBuildMCP__screenshot before proceeding to UI interaction.
  • If the app is already built and only launch is requested, use mcp__XcodeBuildMCP__launch_app_sim.
  • If bundle id is unknown:
    1. mcp__XcodeBuildMCP__get_sim_app_path
    2. mcp__XcodeBuildMCP__get_app_bundle_id

UI Interaction & Debugging

Use these when asked to inspect or interact with the running app.

  • Describe UI: mcp__XcodeBuildMCP__describe_ui before tapping or swiping.
  • Tap: mcp__XcodeBuildMCP__tap (prefer id or label; use coordinates only if needed).
  • Type: mcp__XcodeBuildMCP__type_text after focusing a field.
  • Gestures: mcp__XcodeBuildMCP__gesture for common scrolls and edge swipes.
  • Screenshot: mcp__XcodeBuildMCP__screenshot for visual confirmation.

Logs & Console Output

  • Start logs: mcp__XcodeBuildMCP__start_sim_log_cap with the app bundle id.
  • Stop logs: mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines.
  • For console output, set captureConsole: true and relaunch if required.

Troubleshooting

  • If build fails, ask whether to retry with preferXcodebuild: true.
  • If the wrong app launches, confirm the scheme and bundle id.
  • If UI elements are not hittable, re-run describe_ui after layout changes.

Source and attribution

Source:dimillian/skillsinios-debugger-agentat commit05ba982

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal