xcodebuildmcp-simulator-logslisted

# XcodeBuildMCP Simulator Logs Manage simulator runs and capture logs directly through the XcodeBuildMCP server. The user does not need to paste console output by hand. > Requires the `xcodebuildmcp` MCP server (configured in `.mcp.json`). It will prompt for approval on first use this session. ## When to Use This Skill - The user wants simulator logs captured or analyzed. - The user asks to run or verify the iOS app in Simulator. - The user wants ongoing debugging without copy/pasting log output. - The user is troubleshooting StoreKit, auth, crash, or runtime behavior in Simulator. ## Core Rules 1. Before the first simulator build, run, or test call in a session, call `session_show_defaults`. 2. If defaults are missing or wrong, discover projects and schemes first, then proceed with simulator workflows. 3. Do **not** call `boot_sim` or `open_sim` as prerequisites for `build_run_sim` — `build_run_sim` handles boot and opening automatically. 4. For ongoing logs, call `start_sim_log_cap` and keep the returned `logSessionId` for later retrieval. 5. To read captured output, call `stop_sim_log_cap` with the `logSessionId`, then immediately start a new capture if continuous monitoring is needed. ## Workflow: Connect to Simulator Log Stream 1. `session_show_defaults` — verify active project/workspace, scheme, simulator. 2. `start_sim_log_cap` with `subsystemFilter: app` unless broader logs are needed. 3. Ask the user to reproduce the issue. 4. `stop_sim_log_cap` to retrieve l