# Debug iOS Apps on Simulator

iOS simulator debugging often requires many separate build, launch, UI, and log steps. This skill gives Claude a clear XcodeBuildMCP workflow for inspecting app behavior in one guided session.

## Install

```bash
npx skillstore add dimillian/ios-debugger-agent
```

## Metadata

- Status: approved
- Slug: dimillian-ios-debugger-agent
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6ee4fad65d314f5bce72338a28542aba7dcbe1bbae1b622f5b6446ed9f507df4
- Author: Dimillian
- GitHub username: Dimillian
- License: MIT
- Repository: https://github.com/Dimillian/Skills/tree/main/ios-debugger-agent
- Ref: 1ffa7643651792ccb4bd3b15d924d2c97edff755
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dimillian-ios-debugger-agent
- Manifest: https://skillstore.pages.dev/api/skills/dimillian-ios-debugger-agent/manifest

## Capabilities

- Finds a booted iOS simulator before running simulator actions.
- Sets XcodeBuildMCP session defaults for project, scheme, and simulator.
- Builds and runs an iOS app on the selected simulator when requested.
- Launches an already built simulator app when a full build is not needed.
- Describes, taps, types, gestures, and screenshots simulator UI through MCP tools.
- Starts and stops simulator log capture and summarizes important console output.

## Use Cases

- Validate a New iOS Screen: Build and run the app, inspect the visible UI, and confirm that key elements appear on the simulator.
- Investigate Runtime Behavior: Launch the app, capture console logs, interact with the UI, and summarize errors or warnings.
- Reproduce a Simulator Bug: Follow a reported interaction path, use screenshots for confirmation, and collect simulator logs for diagnosis.

## Prompt Templates

### Run the iOS App

```
Run this iOS app on the booted simulator and tell me whether it launches successfully.
```

### Inspect the Current Screen

```
Use the simulator tools to describe the current UI and point out anything that looks broken.
```

### Reproduce a Navigation Issue

```
Build and run the app, open the settings screen, tap the account option, and capture logs if the app fails.
```

### Diagnose a Launch Regression

```
Set the XcodeBuildMCP session defaults, run the Debug configuration, capture console output, and summarize likely causes of the launch failure.
```

## Limitations

- Requires XcodeBuildMCP tools to be installed and available in the session.
- Requires a booted simulator, unless the user explicitly asks to boot one.
- Does not choose the correct scheme automatically when the project has ambiguous targets.
- Does not replace unit tests, UI tests, or device testing on physical hardware.

## Best Practices

- Start with the booted simulator and confirm the target scheme before building.
- Use UI description before tapping so interactions target visible elements.
- Capture logs only for the app and summarize relevant lines instead of pasting noisy output.

## Anti Patterns

- Do not run simulator actions without confirming a booted device exists.
- Do not rely on coordinates when labels or element identifiers are available.
- Do not treat simulator success as proof that behavior works on every physical device.

## Security Audit

- Audited at: 2026-07-09T04:37:40.412\+00:00
- Summary: Static findings are false positives caused by markdown inline code references to XcodeBuildMCP tools and iOS simulator parameters. The skill guides authorized local simulator debugging, UI inspection, screenshots, and log capture without arbitrary command execution, network upload, or prompt injection content.

## Stats

- Views: 196
- Downloads: 10
- Favorites: 0
- Popularity score: 0