ios-simulator-testing
Which tool to use and when
Two MCP servers are available for iOS testing. They have distinct roles and should not be interchanged:
XcodeBuildMCP — build, boot, and install
Use XcodeBuildMCP for everything before you start touching the UI:
| Task | Tool |
|---|---|
| Check session defaults (project, scheme, simulator) | session_show_defaults |
| Build and run on simulator | build_run_sim |
| Build only (no run) | build_sim |
| List available simulators | list_sims |
| List schemes in project | list_schemes |
| Boot a specific simulator | boot_sim |
| Install a pre-built .app | install_app_sim |
| Capture logs from simulator | start_sim_log_cap / stop_sim_log_cap |
| Run tests | test_sim |
More from arjitj2/arjit-skills
creating-skills
Use when creating a new skill, adding a skill to the user's setup, or the user says "make this a skill". All personal skills live in the arjit-skills monorepo and are symlinked into place.
2adding-a-project
Use when adding a new project to the user's personal site and resume, or when the user says to make something "live". Covers updating both arjit-me and arjit-resume, compiling the PDF, and pushing.
2frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
2address-copilot-review
Handle GitHub Copilot PR review comments end-to-end. Use when the user asks to read Copilot's review on a pull request, decide which comments to act on, implement appropriate fixes, push follow-up commits, reply on each review thread with either the fix or the rationale for not changing code, and resolve threads that are fully addressed.
2swiftui-design-principles
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
2resolve-merge-conflicts
Resolve PR merge conflicts end-to-end by identifying the base branch, merging it locally, fixing conflicted files carefully, validating the result, and pushing the updated branch. Use when the user asks to look at merge conflicts on a PR, resolve them, and push the branch.
1