iOS Dev
Use this skill when the user wants you to create, modify, build, run, debug, screenshot, or inspect an iOS app in the macOS iOS Simulator.
ZCode Tool Names
This skill assumes the MCP server is configured in zcode as ios_simulator. In zcode, MCP tools are exposed to the model as mcp__ios_simulator__<tool>.
If the server is configured with a different name, use the corresponding visible mcp__<server>__... tool names from the active zcode tool list.
Default Workflow
- Call
mcp__ios_simulator__ios_preflight first.
- If full Xcode or
simctl is missing, stop the simulator workflow and explain the exact missing check.
- Command Line Tools alone are not enough for this plugin.
- Discover the project with
mcp__ios_simulator__ios_discover_project.
- If no Xcode project exists and the user wants a new app, call
mcp__ios_simulator__ios_create_app.
- Prefer editing the generated SwiftUI files directly after project creation.
mcp__ios_simulator__ios_create_app refuses to overwrite generated files by default; only pass overwrite: true after explicit user confirmation.
- Build and launch with
mcp__ios_simulator__ios_build_and_run.
- Pass
scheme when multiple schemes exist.
- Use
openSimulator: true when the user expects to see the macOS Simulator window.
- Read the returned
output first for compile errors; use the returned log path only when more detail is needed.
- Verify the app visually with
mcp__ios_simulator__ios_screenshot.
- For simple runtime checks, use
mcp__ios_simulator__ios_open_url, mcp__ios_simulator__ios_launch_app, mcp__ios_simulator__ios_terminate_app, and mcp__ios_simulator__ios_logs.
- For UI automation, call
mcp__ios_simulator__ios_ui_status first.
mcp__ios_simulator__ios_ui_tap, mcp__ios_simulator__ios_ui_swipe, mcp__ios_simulator__ios_ui_type_text, mcp__ios_simulator__ios_ui_button, and mcp__ios_simulator__ios_ui_describe require the optional idb backend.
- If
idb is unavailable, continue with build/run/screenshot checks and say UI automation is unavailable.
Tool Notes
- This MVP intentionally uses Apple's macOS Simulator app for rendering. Do not create or expect a custom simulator window.
- The MCP tools accept
udid, device, and runtime when a specific simulator is needed. Otherwise they choose the booted simulator, then the configured default iPhone device.
- Keep simulator interactions through MCP tools instead of raw
xcrun commands unless a tool does not cover the operation.
mcp__ios_simulator__ios_create_app generates a minimal SwiftUI app suitable for model-driven iteration.
mcp__ios_simulator__ios_build_app only builds. mcp__ios_simulator__ios_build_and_run builds, installs, launches, and opens Simulator.
Extension Point
The UI backend is deliberately isolated. P0 uses idb when installed; future backends can map the same public operations to XcodeBuildMCP, native Accessibility, or another automation bridge without changing the skill workflow.
1---2name: ios-dev3description: Build, run, inspect, and lightly automate iOS simulator apps with the ios-simulator MCP tools.4metadata:5 source: https://skillmd.com/skills/tomjiu/ios-dev6---78# iOS Dev910Use this skill when the user wants you to create, modify, build, run, debug, screenshot, or inspect an iOS app in the macOS iOS Simulator.1112## ZCode Tool Names1314This skill assumes the MCP server is configured in zcode as `ios_simulator`. In zcode, MCP tools are exposed to the model as `mcp__ios_simulator__<tool>`.1516If the server is configured with a different name, use the corresponding visible `mcp__<server>__...` tool names from the active zcode tool list.1718## Default Workflow19201. Call `mcp__ios_simulator__ios_preflight` first.21 - If full Xcode or `simctl` is missing, stop the simulator workflow and explain the exact missing check.22 - Command Line Tools alone are not enough for this plugin.232. Discover the project with `mcp__ios_simulator__ios_discover_project`.24 - If no Xcode project exists and the user wants a new app, call `mcp__ios_simulator__ios_create_app`.25 - Prefer editing the generated SwiftUI files directly after project creation.26 - `mcp__ios_simulator__ios_create_app` refuses to overwrite generated files by default; only pass `overwrite: true` after explicit user confirmation.273. Build and launch with `mcp__ios_simulator__ios_build_and_run`.28 - Pass `scheme` when multiple schemes exist.29 - Use `openSimulator: true` when the user expects to see the macOS Simulator window.30 - Read the returned `output` first for compile errors; use the returned log path only when more detail is needed.314. Verify the app visually with `mcp__ios_simulator__ios_screenshot`.325. For simple runtime checks, use `mcp__ios_simulator__ios_open_url`, `mcp__ios_simulator__ios_launch_app`, `mcp__ios_simulator__ios_terminate_app`, and `mcp__ios_simulator__ios_logs`.336. For UI automation, call `mcp__ios_simulator__ios_ui_status` first.34 - `mcp__ios_simulator__ios_ui_tap`, `mcp__ios_simulator__ios_ui_swipe`, `mcp__ios_simulator__ios_ui_type_text`, `mcp__ios_simulator__ios_ui_button`, and `mcp__ios_simulator__ios_ui_describe` require the optional `idb` backend.35 - If `idb` is unavailable, continue with build/run/screenshot checks and say UI automation is unavailable.3637## Tool Notes3839- This MVP intentionally uses Apple's macOS Simulator app for rendering. Do not create or expect a custom simulator window.40- The MCP tools accept `udid`, `device`, and `runtime` when a specific simulator is needed. Otherwise they choose the booted simulator, then the configured default iPhone device.41- Keep simulator interactions through MCP tools instead of raw `xcrun` commands unless a tool does not cover the operation.42- `mcp__ios_simulator__ios_create_app` generates a minimal SwiftUI app suitable for model-driven iteration.43- `mcp__ios_simulator__ios_build_app` only builds. `mcp__ios_simulator__ios_build_and_run` builds, installs, launches, and opens Simulator.4445## Extension Point4647The UI backend is deliberately isolated. P0 uses `idb` when installed; future backends can map the same public operations to XcodeBuildMCP, native Accessibility, or another automation bridge without changing the skill workflow.