playbooks

home / skills / fusengine / agents / ios

ios skill

/plugins/swift-apple-expert/skills/ios

This skill helps you accelerate iOS app development and testing by automating builds, UI actions, and device workflows with XcodeBuildMCP.

npx playbooks add skill fusengine/agents --skill ios

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
2.5 KB
---
name: ios
description: iOS platform-specific development with XcodeBuildMCP tools for simulator, device, UI automation, and debugging. Use when building iPhone apps, testing on simulator/device, or automating UI interactions.
versions:
  ios: 26
  xcode: 26
user-invocable: false
references: references/simulator-tools.md, references/device-tools.md, references/ui-automation.md, references/debugging.md, references/uikit-integration.md
related-skills: swift-core, swiftui-core, ipados, mcp-tools
---

# iOS Platform

iOS-specific development with XcodeBuildMCP automation tools.

## Agent Workflow (MANDATORY)

Before ANY implementation, use `TeamCreate` to spawn 3 agents:

1. **fuse-ai-pilot:explore-codebase** - Analyze existing iOS patterns
2. **fuse-ai-pilot:research-expert** - Verify latest iOS 26 docs via Context7/Exa
3. **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](references/simulator-tools.md) |
| Device deployment | [device-tools.md](references/device-tools.md) |
| Touch automation | [ui-automation.md](references/ui-automation.md) |
| LLDB debugging | [debugging.md](references/debugging.md) |
| UIKit in SwiftUI | [uikit-integration.md](references/uikit-integration.md) |

---

## Best Practices

1. **Build validation** - Always build before commit
2. **Simulator first** - Faster iteration
3. **Device testing** - Required before release
4. **Accessibility IDs** - Enable UI automation
5. **Screenshots** - Document UI states
6. **Test on oldest supported** - iOS version compatibility

Overview

This skill provides iOS platform-specific development automation using XcodeBuildMCP tools for simulator, device, UI automation, and debugging. It streamlines building, testing, deploying, and automating UI interactions for iPhone apps. Use it to speed iterative development cycles and enforce consistent device validation before release.

How this skill works

Before any implementation, create a team of three agents (explore-codebase, research-expert, and mcp__XcodeBuildMCP__discover_projs) to analyze the codebase, verify iOS docs, and locate Xcode projects. The skill exposes MCP commands for simulator workflows (build_sim, boot_sim, launch_app_sim, test_sim), device operations (build_device, install_app_device, list_devices), and UI automation (tap, swipe, screenshot, snapshot_ui). After changes, run a sniper validation agent to verify integration and tests.

When to use it

  • Building and compiling iPhone apps for simulator and device
  • Running automated test suites on simulator or physical hardware
  • Deploying and validating builds on connected iOS devices
  • Automating UI flows for regression testing or demos
  • Debugging app behavior and capturing view hierarchies or screenshots

Best practices

  • Run an initial TeamCreate workflow to spawn explore, research, and discovery agents before coding
  • Always validate a local build before committing changes
  • Use simulator for fast iteration, then test on real devices prior to release
  • Add stable accessibility IDs to support reliable UI automation
  • Capture screenshots and view hierarchies to document UI states and debug regressions

Example use cases

  • Build and run unit and UI tests on the iOS simulator as part of CI validation
  • Install a nightly build to a QA device farm and run automated tap/swipe scenarios
  • Capture screenshots of core flows to include in release notes or bug reports
  • Use snapshot_ui to extract the view hierarchy when debugging layout or accessibility issues
  • Run LLDB-assisted debugging on a device after reproducing a crash with automated steps

FAQ

Which agents must I spawn before implementing changes?

Spawn three agents: one to explore the codebase, one to verify iOS docs, and one to discover Xcode projects. This ensures correct context and project targeting.

Should I always test on device if simulator passes?

Yes. Simulator is fast for iteration, but hardware-specific behaviors and APIs require device testing before release.