/ios
Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools.
$ npx -y skills add fusengine/agents --skill ios --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ios
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools.
SKILL.md
ios.SKILL.mdname: ios
description: Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools.
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
<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 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
Read more
name: ios description: Use when building iPhone apps — simulator/device testing, UI automation, or debugging — with XcodeBuildMCP tools. 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
<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 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
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill