smithery/dimillian

ios-debugger-agent

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.

Installation

$ npx skills add smithery/dimillian --skill ios-debugger-agent

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/dimillian.

npx skills add smithery/dimillian

Browse all from smithery/dimillian

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,765 B
  • docs SUMMARY.md 303 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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 mcpXcodeBuildMCPlist_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 mcpXcodeBuildMCPsession-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 mcpXcodeBuildMCPbuildrunsim.
  • 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 mcpXcodeBuildMCPdescribe_ui or mcpXcodeBuildMCPscreenshot before proceeding to UI interaction.
  • If the app is already built and only launch is requested, use mcpXcodeBuildMCPlaunchappsim.
  • If bundle id is unknown:

1) mcpXcodeBuildMCPgetsimapppath 2) mcpXcodeBuildMCPgetappbundleid

UI Interaction & Debugging

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

  • Describe UI: mcpXcodeBuildMCPdescribe_ui before tapping or swiping.
  • Tap: mcpXcodeBuildMCPtap (prefer id or label; use coordinates only if needed).
  • Type: mcpXcodeBuildMCPtype_text after focusing a field.
  • Gestures: mcpXcodeBuildMCPgesture for common scrolls and edge swipes.
  • Screenshot: mcpXcodeBuildMCPscreenshot for visual confirmation.

Logs & Console Output

  • Start logs: mcpXcodeBuildMCPstartsimlog_cap with the app bundle id.
  • Stop logs: mcpXcodeBuildMCPstopsimlog_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.