菜单
Build, run, launch, inspect, interact with, and debug iOS simulator apps using XcodeBuildMCP tools, UI descriptions, screenshots, and log capture. Prefer ios-simulator-browser for user-facing browser mirrors, visible simulator proof, or SwiftUI preview viewing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Search Apple Dev Search for Swift, SwiftUI, Xcode, iOS, macOS, and Apple-platform community articles, tutorials, blogs, and write-ups.
Apple firmware and binary reverse engineering with the `ipsw` CLI: IPSW/kernelcache download/extraction, dyld_shared_cache disassembly, private headers, entitlements, Mach-O analysis, Apple internals, KEXTs, and security research.
Use when App Store listing text must be translated or market-adapted across locales, including descriptions, keywords, What's New, subtitles, names, privacy text, and App Store Connect languages. Not for non-translation metadata edits, release-note drafting, or subscription/IAP display-name localization.
Use when App Store listing metadata in canonical `./metadata` JSON needs field edits, validation, push, keyword sync, or legacy fastlane migration. Not for translation-first localization, release-note drafting, or subscription/IAP display-name localizations.
Use for the concrete macOS Developer ID notarization command path with xcodebuild export plus `asc notarization` submit, status, log, and stapling. Not for broad packaging readiness review or signing-only diagnosis.
Set territory-specific subscription and IAP pricing with `asc` setup, pricing summary, CSV import, price-point, availability, and schedule commands. Use for PPP or localized pricing strategies.
| name | ios-simulator-debugger |
| description | Build, run, launch, inspect, interact with, and debug iOS simulator apps using XcodeBuildMCP tools, UI descriptions, screenshots, and log capture. Prefer ios-simulator-browser for user-facing browser mirrors, visible simulator proof, or SwiftUI preview viewing. |
Use XcodeBuildMCP for simulator control, build/run, UI inspection, screenshots, interaction, and logs.
If the user should see or interact with the running app, prefer ios-simulator-browser after this skill has selected or launched the Simulator. Keep this skill focused on build/run, logs, bundle IDs, UI tree inspection, and headless simulator automation.
mcp__XcodeBuildMCP__list_sims. If none is booted, ask the user to boot one unless they asked you to boot it.mcp__XcodeBuildMCP__session-set-defaults: projectPath or workspacePath, scheme, simulatorId, optional configuration: "Debug" and useLatestOS: true.mcp__XcodeBuildMCP__build_run_sim when requested. If the build fails, inspect output and retry only when justified, optionally with preferXcodebuild: true.mcp__XcodeBuildMCP__describe_ui or mcp__XcodeBuildMCP__screenshot before UI interaction.mcp__XcodeBuildMCP__launch_app_sim. If bundle id is unknown, call mcp__XcodeBuildMCP__get_sim_app_path then mcp__XcodeBuildMCP__get_app_bundle_id.mcp__XcodeBuildMCP__describe_ui.id or label first; coordinates only when needed.mcp__XcodeBuildMCP__type_text.mcp__XcodeBuildMCP__gesture for scrolls and edge swipes.mcp__XcodeBuildMCP__screenshot.Start capture with mcp__XcodeBuildMCP__start_sim_log_cap and the app bundle id. Stop with mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines. For console output, set captureConsole: true and relaunch if required.
Wrong app means verify scheme/bundle id. Non-hittable elements require fresh describe_ui after layout changes. Do not keep interacting after an unhandled build or launch failure.