// 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.
Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.
Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.
Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
| 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. |
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.
Follow this sequence unless the user asks for a narrower action.
mcp__XcodeBuildMCP__list_sims and select the simulator with state Booted.mcp__XcodeBuildMCP__session-set-defaults with:
projectPath or workspacePath (whichever the repo uses)scheme for the current appsimulatorId from the booted deviceconfiguration: "Debug", useLatestOS: truemcp__XcodeBuildMCP__build_run_sim.preferXcodebuild: true) or escalate to the user before attempting any UI interaction.mcp__XcodeBuildMCP__describe_ui or mcp__XcodeBuildMCP__screenshot before proceeding to UI interaction.mcp__XcodeBuildMCP__launch_app_sim.mcp__XcodeBuildMCP__get_sim_app_pathmcp__XcodeBuildMCP__get_app_bundle_idUse these when asked to inspect or interact with the running app.
mcp__XcodeBuildMCP__describe_ui before tapping or swiping.mcp__XcodeBuildMCP__tap (prefer id or label; use coordinates only if needed).mcp__XcodeBuildMCP__type_text after focusing a field.mcp__XcodeBuildMCP__gesture for common scrolls and edge swipes.mcp__XcodeBuildMCP__screenshot for visual confirmation.mcp__XcodeBuildMCP__start_sim_log_cap with the app bundle id.mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines.captureConsole: true and relaunch if required.preferXcodebuild: true.describe_ui after layout changes.