← Build iOS AppsCONTENT HISTORY

Update to Build iOS Apps

Snapshot Sep 30, 2026 · 23:18 UTC · version 0.1.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build, run, and debug iOS apps on Simulator with XcodeBuildMCP. Use when launching an app, inspecting simulator UI or logs, or diagnosing runtime behavior.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 218
    }
  ],
  "name": "ios-debugger-agent",
  "skill_md_contents": "---\nname: ios-debugger-agent\ndescription: Build, run, and debug iOS apps on Simulator with XcodeBuildMCP. Use when launching an app, inspecting simulator UI or logs, or diagnosing runtime behavior.\n---\n\n# iOS Debugger Agent\n\n## Overview\nUse 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.\n\n## Core Workflow\nFollow this sequence unless the user asks for a narrower action.\n\n### 1) Discover the booted simulator\n- Call `mcp__XcodeBuildMCP__list_sims` and select the simulator with state `Booted`.\n- If none are booted, ask the user to boot one (do not boot automatically unless asked).\n\n### 2) Set session defaults\n- Call `mcp__XcodeBuildMCP__session-set-defaults` with:\n  - `projectPath` or `workspacePath` (whichever the repo uses)\n  - `scheme` for the current app\n  - `simulatorId` from the booted device\n  - Optional: `configuration: \"Debug\"`, `useLatestOS: true`\n\n### 3) Build + run (when requested)\n- Call `mcp__XcodeBuildMCP__build_run_sim`.\n- **If the build fails**, check the error output and retry (optionally with `preferXcodebuild: true`) or escalate to the user before attempting any UI interaction.\n- **After a successful build**, verify the app launched by calling `mcp__XcodeBuildMCP__describe_ui` or `mcp__XcodeBuildMCP__screenshot` before proceeding to UI interaction.\n- If the app is already built and only launch is requested, use `mcp__XcodeBuildMCP__launch_app_sim`.\n- If bundle id is unknown:\n  1) `mcp__XcodeBuildMCP__get_sim_app_path`\n  2) `mcp__XcodeBuildMCP__get_app_bundle_id`\n\n## UI Interaction & Debugging\nUse these when asked to inspect or interact with the running app.\n\n- **Describe UI**: `mcp__XcodeBuildMCP__describe_ui` before tapping or swiping.\n- **Tap**: `mcp__XcodeBuildMCP__tap` (prefer `id` or `label`; use coordinates only if needed).\n- **Type**: `mcp__XcodeBuildMCP__type_text` after focusing a field.\n- **Gestures**: `mcp__XcodeBuildMCP__gesture` for common scrolls and edge swipes.\n- **Screenshot**: `mcp__XcodeBuildMCP__screenshot` for visual confirmation.\n\n## Logs & Console Output\n- Start logs: `mcp__XcodeBuildMCP__start_sim_log_cap` with the app bundle id.\n- Stop logs: `mcp__XcodeBuildMCP__stop_sim_log_cap` and summarize important lines.\n- For console output, set `captureConsole: true` and relaunch if required.\n\n## Troubleshooting\n- If build fails, ask whether to retry with `preferXcodebuild: true`.\n- If the wrong app launches, confirm the scheme and bundle id.\n- If UI elements are not hittable, re-run `describe_ui` after layout changes.\n"
}

SHA-256 of public snapshot: ee1145c5d09f919a5ddcc175deee796dd7fa40e7743e195838978f31f02b9ca8