菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when evaluating, designing, or pressure-testing the business model of an AI agent product. Triggers on "agent business model", "agent economics", "agent canvas", "evaluate agent product", "agent pricing", "agent unit economics", "agentic business", "AI agent company", "agent cost structure".
Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.
Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.
Use when a pipeline DOT file has passed structural validation but may still have flow inefficiencies, spec fidelity gaps, or information loss in prompts. Use after dotfile-audit or dotfile-from-spec when you want to deeply verify a pipeline captures everything from the original spec. Use when prompts might be missing critical domain rules, data models, or invariants.
| 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.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.