← ClaudeAtlas

ios-debugger-agentlisted

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.
patrickserrano/lacquer · ★ 1 · AI & Automation · score 67
Install: claude install-skill patrickserrano/lacquer
# iOS Debugger Agent 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`. ## Overview 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. ## Prerequisites - FlowDeck CLI installed (`flowdeck --version`) - Project with `.xcodeproj` or `.xcworkspace` - A saved FlowDeck config, or enough context to create one (`flowdeck context --json`) ## Core Workflow ### 1) Check for a saved config first ```bash 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: ```bash flowdeck context --json flowdeck config set -w <workspace> -s <scheme> -S "<simulator>" ``` ### 2) Discover the booted simulator (if you need a specific one) `