Agent Skills › Dimillian/Skills › ios-debugger-agent

ios-debugger-agent

GitHub

利用 XcodeBuildMCP 在 iOS 模拟器上构建、运行应用，并通过 UI 交互、截图和日志捕获进行运行时调试与状态检查。

ios-debugger-agent/SKILL.md Dimillian/Skills

Trigger Scenarios

用户请求运行或启动 iOS 应用需要检查模拟器 UI 状态或元素需要捕获或分析控制台日志诊断 iOS 应用的运行时行为

Install

npx skills add Dimillian/Skills --skill ios-debugger-agent -g -y

More Options

Non-standard path

npx skills add https://github.com/Dimillian/Skills/tree/main/ios-debugger-agent -g -y

Use without installing

npx skills use Dimillian/Skills@ios-debugger-agent

指定 Agent (Claude Code)

npx skills add Dimillian/Skills --skill ios-debugger-agent -a claude-code -g -y

安装 repo 全部 skill

npx skills add Dimillian/Skills --all -g -y

预览 repo 内 skill

npx skills add Dimillian/Skills --list

SKILL.md

Frontmatter

{
    "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."
}

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.