agentleFS
mohammadchehabmohammadchehab/isnadibot/.agents/skills/ios-debugger-agent/SKILL.md

ios-debugger-agent

Skill2 starsChanged 14 days agoMITView on GitHub

Build, launch, inspect, and drive iOS apps with the repository-configured XcodeBuildMCP server. Use on macOS for iOS Simulator builds, focused native test runs, semantic UI automation, screenshots, logs, or debugging, including IsnadiBot mobile verification.

14 other projects use a version of this, 3 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

Show its rules and text

We split this skill into the rules it gives an agent

21 rules. 0 are common, 5 are distinctive, and 16 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 16

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the repository-configured xcodebuildmcp tools instead of requiring a globally installed Codex plugin.

    line 8
  2. Distinctive:

    If the tools are missing:

    line 14
  3. Very specific:

    Run npx --yes xcodebuildmcp@2.6.2 doctor when the server starts but simulator or UI-automation tools are unavailable.

    line 18
  4. Very specific:

    Do not ask contributors to install the OpenAI build-ios-apps plugin globally.

    line 21
  5. Very specific:

    Call session_show_defaults before discovery, build, launch, or UI work.

    line 25
  6. Very specific:

    Call list_sims and select one explicit simulator UDID.

    line 26
  7. Very specific:

    Call session_set_defaults with the project or workspace, scheme, Debug configuration, simulator ID, and bundle identifier when known.

    line 27
  8. Distinctive:

    Keep every subsequent build, launch, screenshot, log capture, and UI action pinned to that same UDID.

    line 28
  9. Distinctive:

    Avoid generic Mac window automation for switching among Simulator windows.

    line 30
  10. Very specific:

    Use build_run_sim when native source, native dependencies, entitlements, or project configuration changed.

    line 34
  11. Very specific:

    Use test_sim for the smallest relevant native test target or test cases.

    line 35
  12. Very specific:

    Use launch_app_sim when a compatible app is already installed and no native rebuild is needed.

    line 36
  13. Very specific:

    Do not run a build-only action immediately before build_run_sim unless the task requires both artifacts.

    line 38
  14. Very specific:

    After launch, call snapshot_ui or screenshot before interacting.

    line 40
  15. Very specific:

    Call snapshot_ui to obtain the current accessibility hierarchy and element references.

    line 44
  16. Very specific:

    Use only current elementRef values whose snapshot entries list the intended action.

    line 45
  17. Very specific:

    Use wait_for_ui for asynchronous transitions when available rather than fixed sleeps.

    line 47
  18. Very specific:

    Use gesture or scoped swipe actions when needed.

    line 50
  19. Very specific:

    Use start_sim_log_cap and stop_sim_log_cap with the exact bundle identifier for focused runtime logs.

    line 54
  20. Distinctive:

    Use debugger tools only when the task requires runtime diagnosis.

    line 55
  21. Distinctive:

    Stop only log captures, debugger sessions, apps, or simulators started for the current test.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 14 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

Use the repository-configured xcodebuildmcp tools instead of requiring a globally installed Codex plugin. Prefer MCP tools over raw xcodebuild, xcrun, or simctl when the client exposes them.

Confirm availability

This workflow requires macOS 14.5 or newer, Xcode 16 or newer, and Node.js 18 or newer. The repository pins XcodeBuildMCP in both .mcp.json for Claude Code and .codex/config.toml for Codex. Project MCP servers may require one-time trust or approval followed by a new session.

If the tools are missing:

  1. Confirm the repository is trusted and its project MCP server was approved.
  2. Restart or recreate the agent session after approving configuration.
  3. Run npx --yes xcodebuildmcp@2.6.2 doctor when the server starts but simulator or UI-automation tools are unavailable. Follow its actionable Xcode or AXe setup guidance.
  4. Fall back to the pinned XcodeBuildMCP CLI or native Apple CLIs only when the current agent client cannot expose project MCP tools.

Do not ask contributors to install the OpenAI build-ios-apps plugin globally.

Establish one simulator context

  1. Call session_show_defaults before discovery, build, launch, or UI work.
  2. Call list_sims and select one explicit simulator UDID. Prefer a simulator that is already booted; boot an installed simulator when verification requires it, but do not create or download runtimes without user authorization.
  3. Call session_set_defaults with the project or workspace, scheme, Debug configuration, simulator ID, and bundle identifier when known.
  4. Keep every subsequent build, launch, screenshot, log capture, and UI action pinned to that same UDID.

Avoid generic Mac window automation for switching among Simulator windows. Explicit device identity is more reliable.

Choose build or launch

  • Use build_run_sim when native source, native dependencies, entitlements, or project configuration changed.
  • Use test_sim for the smallest relevant native test target or test cases; do not run an entire workspace test matrix routinely.
  • Use launch_app_sim when a compatible app is already installed and no native rebuild is needed.
  • To reuse an existing build artifact, use get_sim_app_path or get_app_bundle_id, install it with install_app_sim when necessary, and then launch it.
  • Do not run a build-only action immediately before build_run_sim unless the task requires both artifacts.

After launch, call snapshot_ui or screenshot before interacting. An open Simulator window alone is not evidence that the intended app launched.

Drive the UI semantically

  1. Call snapshot_ui to obtain the current accessibility hierarchy and element references.
  2. Use only current elementRef values whose snapshot entries list the intended action. XcodeBuildMCP 2.6.2 does not accept coordinates for tap; when the app exposes no actionable reference, prefer a registered deep link or another app-supported route and otherwise report the accessibility blocker.
  3. Refresh with snapshot_ui after navigation or layout changes. Element references are snapshot-specific.
  4. Use wait_for_ui for asynchronous transitions when available rather than fixed sleeps.
  5. Capture a final screenshot for the state that proves the affected flow.

Use gesture or scoped swipe actions when needed. If a gesture is unreliable, return to a known route or relaunch rather than switching to generic desktop automation.

Capture logs and debug

  • Use start_sim_log_cap and stop_sim_log_cap with the exact bundle identifier for focused runtime logs.
  • Use debugger tools only when the task requires runtime diagnosis; attach to the selected simulator and app rather than an ambiguous process.
  • Summarize relevant errors instead of returning unbounded logs.

Clean up

Stop only log captures, debugger sessions, apps, or simulators started for the current test. Leave pre-existing simulators and unrelated sessions alone.

Upstream

Adapted from OpenAI's build-ios-apps plugin version 0.1.2 (ios-debugger-agent, MIT) and aligned with XcodeBuildMCP 2.6.2 tool names.

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.