agentleFS
Sign inStart free
tarunyadav1tarunyadav1/ios-app-lifecycle/skills/ios-debugger-agent/SKILL.md

ios-debugger-agent

Skill1 starsChanged 36 days agoMITView on GitHub

Build, run, and debug iOS apps on Simulator with XcodeBuildMCP. Use when launching an app, inspecting simulator UI or logs, or diagnosing runtime behavior.

13 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use test-t3-app, test-t3-mobile and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • btsouthSkill

    test-t3-app

    Launch, retain, and test the T3 Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, cross-turn dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, iteratively test UI behavior with a human, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.

    Also in 3 projects that use this

  • btsouthSkill

    test-t3-mobile

    Launch and test T3 Code Mobile on an iOS Simulator or Android Emulator against disposable local T3 environments, including Metro and dev-client reuse, native rebuild decisions, per-client pairing, seeded projects, semantic UI control, screenshots, and iOS serve-sim streaming. Use after mobile UI or native changes, when reproducing phone or tablet behavior, pairing an emulator to isolated state, or verifying mobile behavior on macOS, Linux, or Windows.

    Also in 3 projects that use this

  • eugenepyvovarovSkill

    swift-concurrency-expert

    Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

    Also in 3 projects that use this

  • patrickserranoSkill

    app-store-changelog

    Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 6 are common, 0 are distinctive, and 6 are very specific to this project.

  • 6

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs.

    line 9
  2. Common:

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

    line 12
  3. Very specific:

    Call mcp__XcodeBuildMCP__list_sims and select the simulator with state Booted.

    line 15
  4. Common:

    If none are booted, ask the user to boot one (do not boot automatically unless asked).

    line 16
  5. Very specific:

    If the app is already built and only launch is requested, use mcp__XcodeBuildMCP__launch_app_sim.

    line 29
  6. Common:

    If bundle id is unknown:

    line 30
  7. Common:

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

    line 35
  8. Very specific:

    Start logs: mcp__XcodeBuildMCP__start_sim_log_cap with the app bundle id.

    line 44
  9. Very specific:

    Stop logs: mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines.

    line 45
  10. Very specific:

    If build fails, ask whether to retry with preferXcodebuild: true.

    line 49
  11. Common:

    If the wrong app launches, confirm the scheme and bundle id.

    line 50
  12. Very specific:

    If UI elements are not hittable, re-run describe_ui after layout changes.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free