ChatGPT Claude Codex CLI Cohere Cursor DeepSeek Gemini GitHub Copilot GLM Grok Kimi Llama MiniMax Mistral OpenAI opencode Skill

ios-debugger-agent

Debug the current iOS project on a booted simulator with XcodeBuildMCP.

LLM Mart · 0 points · 16 1 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download sickn33-agentic-awesome-skills-skills_ios-debugger-agent-286166a.zip · 1 KB

sickn33/agentic-awesome-skills 46883 6831 forks MIT Updated 9h ago

Part of sickn33/agentic-awesome-skills — 427 skills

This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ios-debugger-agent

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart

Git git clone https://github.com/sickn33/agentic-awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

iOS Debugger Agent

Overview

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.

When to Use

When the user asks to run, debug, or inspect an iOS app on a simulator.
When you need simulator UI interaction, screenshots, or runtime logs via XcodeBuildMCP.

Core Workflow

Follow this sequence unless the user asks for a narrower action.

1) Discover the booted simulator

Call mcp__XcodeBuildMCP__list_sims and select the simulator with state Booted.
If none are booted, ask the user to boot one (do not boot automatically unless asked).

2) Set session defaults

Call mcp__XcodeBuildMCP__session-set-defaults with:
- projectPath or workspacePath (whichever the repo uses)
- scheme for the current app
- simulatorId from the booted device
- Optional: configuration: "Debug", useLatestOS: true

3) Build + run (when requested)

Call mcp__XcodeBuildMCP__build_run_sim.
If the build fails, check the error output and retry (optionally with preferXcodebuild: true) or escalate to the user before attempting any UI interaction.
After a successful build, verify the app launched by calling mcp__XcodeBuildMCP__describe_ui or mcp__XcodeBuildMCP__screenshot before proceeding to UI interaction.
If the app is already built and only launch is requested, use mcp__XcodeBuildMCP__launch_app_sim.
If bundle id is unknown:
1. mcp__XcodeBuildMCP__get_sim_app_path
2. mcp__XcodeBuildMCP__get_app_bundle_id

UI Interaction & Debugging

Use these when asked to inspect or interact with the running app.

Describe UI: mcp__XcodeBuildMCP__describe_ui before tapping or swiping.
Tap: mcp__XcodeBuildMCP__tap (prefer id or label; use coordinates only if needed).
Type: mcp__XcodeBuildMCP__type_text after focusing a field.
Gestures: mcp__XcodeBuildMCP__gesture for common scrolls and edge swipes.
Screenshot: mcp__XcodeBuildMCP__screenshot for visual confirmation.

Logs & Console Output

Start logs: mcp__XcodeBuildMCP__start_sim_log_cap with the app bundle id.
Stop logs: mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines.
For console output, set captureConsole: true and relaunch if required.

Troubleshooting

If build fails, ask whether to retry with preferXcodebuild: true.
If the wrong app launches, confirm the scheme and bundle id.
If UI elements are not hittable, re-run describe_ui after layout changes.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Files (agentic-awesome-skills)

agents

openai.yaml 218 B

interface:
  display_name: "iOS Debugger Agent"
  short_description: "Debug iOS apps on Simulator"
  default_prompt: "Use $ios-debugger-agent to build, launch, and inspect the current iOS app on the booted simulator."

SKILL.md 3.1 KB

---
name: ios-debugger-agent
description: Debug the current iOS project on a booted simulator with XcodeBuildMCP.
risk: safe
source: "Dimillian/Skills (MIT)"
date_added: "2026-03-25"
---

# iOS Debugger Agent

## Overview
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.

## When to Use
- When the user asks to run, debug, or inspect an iOS app on a simulator.
- When you need simulator UI interaction, screenshots, or runtime logs via XcodeBuildMCP.

## Core Workflow
Follow this sequence unless the user asks for a narrower action.

### 1) Discover the booted simulator
- Call `mcp__XcodeBuildMCP__list_sims` and select the simulator with state `Booted`.
- If none are booted, ask the user to boot one (do not boot automatically unless asked).

### 2) Set session defaults
- Call `mcp__XcodeBuildMCP__session-set-defaults` with:
  - `projectPath` or `workspacePath` (whichever the repo uses)
  - `scheme` for the current app
  - `simulatorId` from the booted device
  - Optional: `configuration: "Debug"`, `useLatestOS: true`

### 3) Build + run (when requested)
- Call `mcp__XcodeBuildMCP__build_run_sim`.
- **If the build fails**, check the error output and retry (optionally with `preferXcodebuild: true`) or escalate to the user before attempting any UI interaction.
- **After a successful build**, verify the app launched by calling `mcp__XcodeBuildMCP__describe_ui` or `mcp__XcodeBuildMCP__screenshot` before proceeding to UI interaction.
- If the app is already built and only launch is requested, use `mcp__XcodeBuildMCP__launch_app_sim`.
- If bundle id is unknown:
  1) `mcp__XcodeBuildMCP__get_sim_app_path`
  2) `mcp__XcodeBuildMCP__get_app_bundle_id`

## UI Interaction & Debugging
Use these when asked to inspect or interact with the running app.

- **Describe UI**: `mcp__XcodeBuildMCP__describe_ui` before tapping or swiping.
- **Tap**: `mcp__XcodeBuildMCP__tap` (prefer `id` or `label`; use coordinates only if needed).
- **Type**: `mcp__XcodeBuildMCP__type_text` after focusing a field.
- **Gestures**: `mcp__XcodeBuildMCP__gesture` for common scrolls and edge swipes.
- **Screenshot**: `mcp__XcodeBuildMCP__screenshot` for visual confirmation.

## Logs & Console Output
- Start logs: `mcp__XcodeBuildMCP__start_sim_log_cap` with the app bundle id.
- Stop logs: `mcp__XcodeBuildMCP__stop_sim_log_cap` and summarize important lines.
- For console output, set `captureConsole: true` and relaunch if required.

## Troubleshooting
- If build fails, ask whether to retry with `preferXcodebuild: true`.
- If the wrong app launches, confirm the scheme and bundle id.
- If UI elements are not hittable, re-run `describe_ui` after layout changes.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.