How do I install the IOS skill?

Run npx skillmds@latest add fusengine/ios in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with IOS?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

fusengine (@fusengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

IOS by fusengine — Agent Skill

Name: IOS
Rating: 4.666666666666667 (3 reviews)
Author: fusengine

File contents

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

---name: iosdescription: Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools.---<objective>Covers 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.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.</objective># iOS PlatformiOS-specific development with XcodeBuildMCP automation tools.## Agent Workflow (MANDATORY)Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:1. **fuse-ai-pilot:explore-codebase** - Analyze existing iOS patterns2. **fuse-ai-pilot:research-expert** - Verify latest iOS 26 docs via Context7/Exa3. **mcp__XcodeBuildMCP__discover_projs** - Find Xcode projectsAfter 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 Practices1. **Build validation** - Always build before commit2. **Simulator first** - Faster iteration3. **Device testing** - Required before release4. **Accessibility IDs** - Enable UI automation5. **Screenshots** - Document UI states6. **Test on oldest supported** - iOS version compatibility

Frequently asked questions

IOS