Lists the concrete MCP tools available for each phase — simulator tools (build_sim, boot_sim, launch_app_sim, test_sim), device tools (build_device, install_app_device, list_devices), and UI automation primitives.
Best practices: build before every commit, iterate on the simulator first, always test on a real device before release, enable accessibility identifiers for UI automation, and validate against the oldest supported iOS version.
iOS Platform
iOS-specific development with XcodeBuildMCP automation tools.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing iOS patterns
- fuse-ai-pilot:research-expert - Verify latest iOS 26 docs via Context7/Exa
- mcp__XcodeBuildMCP__discover_projs - Find Xcode projects
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Building iPhone applications
- Testing on iOS Simulator
- Deploying to physical devices
- Automating UI interactions
- Debugging app behavior
- UIKit integration in SwiftUI
Why iOS Skill
| Feature |
Benefit |
| XcodeBuildMCP |
Automated build and test |
| UI Automation |
Scripted user interactions |
| Simulator tools |
Fast iteration cycle |
| Device tools |
Real hardware testing |
MCP Tools Available
Simulator Tools
build_sim - Build for simulator
boot_sim - Start simulator
launch_app_sim - Run app
test_sim - Execute tests
Device Tools
build_device - Build for device
install_app_device - Deploy to device
list_devices - Show connected devices
UI Automation
tap, swipe - Touch interactions
screenshot - Capture screen
snapshot_ui - Get view hierarchy
Reference Guide
| Need |
Reference |
| Simulator build/test |
simulator-tools.md |
| Device deployment |
device-tools.md |
| Touch automation |
ui-automation.md |
| LLDB debugging |
debugging.md |
| UIKit in SwiftUI |
uikit-integration.md |
Best Practices
- Build validation - Always build before commit
- Simulator first - Faster iteration
- Device testing - Required before release
- Accessibility IDs - Enable UI automation
- Screenshots - Document UI states
- Test on oldest supported - iOS version compatibility
1---2name: ios3description: Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools.4versions:5 ios: 266 xcode: 267user-invocable: false8references: references/simulator-tools.md, references/device-tools.md, references/ui-automation.md, references/debugging.md, references/uikit-integration.md9related-skills: swift-core, swiftui-core, ipados, mcp-tools10metadata:11 source: https://skillmd.com/skills/fusengine/ios12---1314<objective>15Covers iOS-specific development using XcodeBuildMCP automation tools: building and testing on the iOS Simulator, deploying to physical devices, scripted UI interactions (tap, swipe, screenshot, view-hierarchy snapshot), LLDB debugging, and integrating UIKit views inside SwiftUI.1617Lists the concrete MCP tools available for each phase — simulator tools (build_sim, boot_sim, launch_app_sim, test_sim), device tools (build_device, install_app_device, list_devices), and UI automation primitives.1819Best practices: build before every commit, iterate on the simulator first, always test on a real device before release, enable accessibility identifiers for UI automation, and validate against the oldest supported iOS version.20</objective>2122# iOS Platform2324iOS-specific development with XcodeBuildMCP automation tools.2526## Agent Workflow (MANDATORY)2728Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:29301. **fuse-ai-pilot:explore-codebase** - Analyze existing iOS patterns312. **fuse-ai-pilot:research-expert** - Verify latest iOS 26 docs via Context7/Exa323. **mcp__XcodeBuildMCP__discover_projs** - Find Xcode projects3334After implementation, run **fuse-ai-pilot:sniper** for validation.3536---3738## Overview3940### When to Use4142- Building iPhone applications43- Testing on iOS Simulator44- Deploying to physical devices45- Automating UI interactions46- Debugging app behavior47- UIKit integration in SwiftUI4849### Why iOS Skill5051| Feature | Benefit |52|---------|---------|53| XcodeBuildMCP | Automated build and test |54| UI Automation | Scripted user interactions |55| Simulator tools | Fast iteration cycle |56| Device tools | Real hardware testing |5758---5960## MCP Tools Available6162### Simulator Tools63- `build_sim` - Build for simulator64- `boot_sim` - Start simulator65- `launch_app_sim` - Run app66- `test_sim` - Execute tests6768### Device Tools69- `build_device` - Build for device70- `install_app_device` - Deploy to device71- `list_devices` - Show connected devices7273### UI Automation74- `tap`, `swipe` - Touch interactions75- `screenshot` - Capture screen76- `snapshot_ui` - Get view hierarchy7778---7980## Reference Guide8182| Need | Reference |83|------|-----------|84| Simulator build/test | [simulator-tools.md](references/simulator-tools.md) |85| Device deployment | [device-tools.md](references/device-tools.md) |86| Touch automation | [ui-automation.md](references/ui-automation.md) |87| LLDB debugging | [debugging.md](references/debugging.md) |88| UIKit in SwiftUI | [uikit-integration.md](references/uikit-integration.md) |8990---9192## Best Practices93941. **Build validation** - Always build before commit952. **Simulator first** - Faster iteration963. **Device testing** - Required before release974. **Accessibility IDs** - Enable UI automation985. **Screenshots** - Document UI states996. **Test on oldest supported** - iOS version compatibility