القائمة
Build, run, and debug iOS apps on a simulator. Use when asked to run an iOS app, interact with the simulator UI, capture logs, or diagnose runtime behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Consult a stronger model mid-task for a second opinion before committing to an approach, when stuck, or before declaring a non-trivial task done — the fast-executor + strong-advisor pattern, implemented with the Agent and Workflow tools (Claude Code does not expose Anthropic's raw API advisor tool). Use when running on a cheaper/faster model for mechanical work and a hard design/architecture/risk decision needs a stronger check, or when authoring a Workflow script that should get expert review partway through instead of only at the end.
Use when the user says "caveman mode", "talk like caveman", "use caveman", "less tokens", or "be brief", invokes /caveman, or when token efficiency is requested. Switches responses to an ultra-compressed terse style (multiple intensity levels available, ~75% token reduction) while preserving full technical accuracy.
Use right after being corrected on something a CLAUDE.md file should already have told you, when explicitly asked to review CLAUDE.md, or periodically after a session with a lot of back-and-forth — reviews THIS conversation for friction and proposes a bounded CLAUDE.md edit. A lightweight, single-session complement to skill-tuning-loop (which mines many sessions and validates a proposal against held-out cases before surfacing it — reach for that instead when the ask is "make this systematic," not "check right now"). Own version of the dx plugin's `/dx:review-claudemd`.
Generate a solution, evaluate it against explicit pass/fail criteria, refine using the feedback, repeat until it passes or a round cap is hit. Use for tasks with a clear, checkable bar and demonstrable value from iteration — a bug fix that must pass a test suite, code that must satisfy a lint/style rubric, a document that must meet stated requirements. Distinct from advisor-checkpoint (one strategic consult before committing) — this is a convergence loop against a concrete standard.
Use when PR checks fail, CI is red, or GitHub Actions workflows break - systematically inspects failing checks via gh CLI, pulls logs, checks for flakiness and scopes the breaking commit, scopes external checks, then creates fix plan using existing plan skill
Write a structured handoff document before a session ends, before a context-heavy interruption (SSH/tmux disconnect, context running low, a worktree being handed to another worker or agent), or when explicitly asked for a handoff — captures progress, what worked/failed, and the exact next step so a fresh session can resume without re-deriving context. Own version of the dx plugin's `/dx:handoff`.
| name | ios-debugger-agent |
| description | Build, run, and debug iOS apps on a simulator. Use when asked to run an iOS app, interact with the simulator UI, capture logs, or diagnose runtime behavior. |
Build and run iOS projects on a booted simulator, interact with the UI, and capture logs for debugging — via the flowdeck skill, which is this lacquer's canonical source of truth for exact FlowDeck syntax. This skill is a thin, scenario-specific wrapper around it, not a competing source of commands. If a command below errors or you're unsure of a flag, consult flowdeck's resources/ docs or run flowdeck <command> --help rather than guessing — never fall back to xcrun/simctl/xcodebuild.
FlowDeck ties build, install, and launch together (flowdeck run), and streams logs from the running app rather than querying the OS unified log. There is no need to discover DerivedData paths, hand-construct xcodebuild destinations, or spawn log stream predicates — FlowDeck's config-first workflow and app-tracking model replace all of that.
flowdeck --version).xcodeproj or .xcworkspaceflowdeck context --json)flowdeck config get --json
If a config exists, use bare commands (flowdeck build, flowdeck run, etc.) for the rest of this workflow. If not, discover and create one:
flowdeck context --json
flowdeck config set -w <workspace> -s <scheme> -S "<simulator>"
flowdeck simulator list --json
Check each entry's state field for "Booted". If none are booted and you need a specific device, boot one by UDID (boot takes a UDID, not a name):
flowdeck simulator boot <udid>
flowdeck build
Add -w <workspace> -s <scheme> -S "<simulator>" only if no config is saved and you're not overriding it.
flowdeck run
This builds, installs, and launches in one step, returning an App ID. To launch an existing build without rebuilding:
flowdeck run --no-build
There is no standalone "install only" verb for simulators — FlowDeck ties install to launch by design. (Physical devices are the exception: flowdeck device install <udid> <path-to-app> installs without launching — see resources/device.md in the flowdeck skill.)
Either launch with logs streaming immediately:
flowdeck run --log # run with run_in_background: true
Or attach to an already-running app:
flowdeck apps # find the App ID
flowdeck logs <app-id> # run with run_in_background: true — this is a continuous stream
Never use xcrun simctl spawn … log, log show, or log stream — FlowDeck captures all print() and OSLog output in this one stream.
Screenshots are primarily session-based, not one-off:
flowdeck ui simulator session start -S "<sim>" --json
# Read the `latest_screenshot` path from the JSON response with the Read tool
For a single one-off capture when no session is running:
flowdeck ui simulator screen -S "<sim>" --output /tmp/screenshot.png
flowdeck simulator record -S "<sim>" # record until Ctrl+C, or add --duration 10s
For frame-by-frame capture (e.g. validating an animation) instead of a video file, use flowdeck simulator frames -S "<sim>" (contact sheet by default, --images for full-res PNGs per frame).
flowdeck ui simulator open-url "myapp://deeplink" -S "<sim>"
flowdeck simulator push notification.apns -b com.example.MyApp -S "<sim>"
notification.apns must contain an aps key. -b/--bundle-id is optional if the payload includes a Simulator Target Bundle key.
flowdeck context --json or flowdeck project schemes to confirm the scheme name. On failure, flowdeck build prints the extracted reason and a Full log: <path> line — read that file rather than rerunning with -v/--verbose.flowdeck simulator app info <bundle-id> -S "<sim>" for bundle metadata, or flowdeck apps to see what FlowDeck currently has tracked.flowdeck simulator list --available-only; create one with flowdeck simulator create -n "<name>" --device-type "<type>" --runtime "<runtime>" if needed.flowdeck clean, or flowdeck clean --all to clear all caches.| Task | FlowDeck Command | Notes |
|---|---|---|
| List simulators | flowdeck simulator list --json | Check state field for "Booted"/"Shutdown" |
| Boot simulator | flowdeck simulator boot <udid> | Positional UDID only, not a name — resolve via simulator list --json first |
| Shutdown simulator | flowdeck simulator shutdown <udid> | |
| Erase simulator | flowdeck simulator erase <udid> | Simulator must be shut down first |
| Install app | flowdeck run (build+install+launch), or flowdeck run --no-build (install+launch an existing build) | No standalone simulator-only "install" verb exists in FlowDeck |
| Uninstall app | flowdeck uninstall <app-id-or-bundle-id> | Destructive — requires explicit user consent; not part of FlowDeck's automatic validation loop |
| Launch app | flowdeck run for apps FlowDeck built; flowdeck simulator launch <bundle-id> -S <udid> for apps FlowDeck did not build (system apps, pre-installed builds) | |
| Terminate app | flowdeck stop <app-id-or-bundle-id> | Targets an app FlowDeck is tracking (launched via run or simulator launch) — see flowdeck apps for identifiers. --force sends SIGKILL for a stuck app. |
| Get app container | flowdeck simulator app container <bundle-id> [-c app|data|groups|<group-id>] -S <udid> | -c/--container defaults to app |
For anything not covered above — hardware buttons, appearance, Dynamic Type, privacy grants, keychain, pasteboard, watch/phone pairing — see resources/simulator.md and resources/ui.md in the flowdeck skill.