ios-debugger-agent

Build, launch, and debug iOS apps on a booted simulator with XcodeBuildMCP.

3|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/heyAyushh/stacc --skill ios-debugger-agent-heyayushh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-debugger-agent
Source: https://github.com/heyAyushh/stacc/tree/main/configs/stacks/ios/ios-debugger-agent
Command: npx skills add https://github.com/heyAyushh/stacc --skill ios-debugger-agent-heyayushh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to automate building, launching, and debugging iOS apps on a booted simulator using XcodeBuildMCP. It streamlines handoff between building, running, interacting with the UI, and collecting logs, reducing manual setup.

Core Features & Use Cases

  • Automated Build & Run: Build the current project scheme and run it on a booted iOS simulator.
  • Launch & Inspect: Launch the app when already built and describe or interact with the UI to diagnose issues.
  • UI Interaction & Debugging: Describe UI, tap, type, and gesture to navigate the app and verify behavior.
  • Logs & Diagnostics: Start and stop simulators logs, capture console output, and identify runtime problems.
  • Use Case: A developer wants to quickly verify a new feature in a running simulator and capture logs for bug reporting.

Quick Start

Run the ios-debugger-agent to boot a simulator if needed, build and run the current scheme, then attach UI interaction and log capture to diagnose runtime behavior.

Frequently Asked Questions about ios-debugger-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate building and launching an iOS app on a simulator?

You can automate iOS builds and launches by targeting your current project scheme on a booted simulator, using XcodeBuildMCP to compile and run the app without manual Xcode interaction.

Can I capture simulator logs and diagnose runtime issues automatically?

Yes, you can start and stop simulator logs to capture console output, identifying runtime problems during UI interaction and navigation without manually filtering the Xcode console.

What do I need to run automated iOS UI testing on a simulator?

Automated iOS UI testing requires a booted simulator, the project workspace path, and XcodeBuildMCP tooling to identify the scheme, app bundle, and execute gestures like tapping and typing.

Does this approach work with my existing Xcode project scheme?

Yes, the process applies directly to your current Xcode project scheme, requiring only the workspace or project path and access to the booted simulator to build, launch, and debug.

What's the best way to interact with the UI for debugging on a booted simulator?

The best way to interact with the UI is by describing elements, tapping, typing, and using gestures to navigate the running app, verifying behavior while capturing diagnostic logs.

Why do I need XcodeBuildMCP for iOS simulator debugging?

XcodeBuildMCP is required because it provides the tooling to automate building, launching, and debugging iOS apps on a booted simulator, streamlining rapid iteration and log capture.