菜单
Build, run, and debug the current iOS project on a booted simulator via XcodeBuildMCP — UI interaction, screenshots, view inspection, and runtime log capture. USE WHEN you need to run an iOS app on a simulator, reproduce a bug, tap/type through a flow, or capture console logs.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Sheshiyer/skill-clusters --skill ios-debugger-agent命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | ios-debugger-agent |
| description | Build, run, and debug the current iOS project on a booted simulator via XcodeBuildMCP — UI interaction, screenshots, view inspection, and runtime log capture. USE WHEN you need to run an iOS app on a simulator, reproduce a bug, tap/type through a flow, or capture console logs. |
| cluster | native-ios |
| version | 1.0.0 |
| origin | antigravity-awesome-skills (MIT) |
| risk | safe |
| source | Dimillian/Skills (MIT) |
| date_added | 2026-03-25 |
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.Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.
Shared reference for the Selemene cluster: the two report surfaces (deterministic Rust reports vs. narrative witness-pipeline readings), the @selemene/bridge CLI contract, the output manifest format, and non-prescriptive witnessing tone. USE WHEN deciding which Selemene surface to invoke or when routing between birth/compatibility/transit reports and solo/dyadic readings.
Route Selemene Engine tasks to the right surface: deterministic reports (birth/compatibility/transit) via selemene-core and the @selemene/bridge CLI, or narrative witness readings via selemene-report. USE WHEN the user wants anything under the Selemene/Noesis umbrella but has not named the exact surface.