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.
Works with
--- name: ios-debugger-agent description: 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. license: MIT --- # 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.
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

