ワンクリックで
xcode
Intelligent Xcode development operations
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Intelligent Xcode development operations
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | xcode |
| description | Intelligent Xcode development operations |
This skill provides guidance for using xc-mcp tools efficiently based on the task at hand. It routes operations to the appropriate MCP server or native CLI to minimize token overhead.
The xc-mcp toolset is split into focused servers for token efficiency:
| Server | Tools | Token Overhead | Use Case |
|---|---|---|---|
| xc-project | 23 | ~5K | .xcodeproj file manipulation |
| xc-simulator | 29 | ~6K | iOS Simulator, UI automation, sim logs |
| xc-device | 12 | ~2K | Physical iOS devices |
| xc-debug | 8 | ~2K | LLDB debugging |
| xc-swift | 6 | ~1.5K | Swift Package Manager |
| xc-build | 18 | ~3K | macOS builds, discovery, utilities |
| xc-mcp | 89 | ~50K | All tools (monolithic) |
Use mcp__xc-project__* tools for operations that modify .xcodeproj files:
These operations require the XcodeProj library - no CLI equivalent exists.
Use mcp__xc-simulator__* tools for:
build_run_sim)Use mcp__xc-device__* tools for:
Use mcp__xc-debug__* tools for:
Debug sessions maintain persistent state - use this server for multi-step debugging workflows.
Use mcp__xc-swift__* tools for:
Use mcp__xc-build__* tools for:
For read-only queries, use Bash directly to avoid MCP overhead:
# List schemes
xcodebuild -list -json
# List simulators
xcrun simctl list devices --json
# Simple SPM build
swift build
Users can configure which servers to enable in their .mcp.json:
{
"mcpServers": {
"xc-project": { "command": "xc-project" }
}
}
{
"mcpServers": {
"xc-project": { "command": "xc-project" },
"xc-build": { "command": "xc-build" },
"xc-simulator": { "command": "xc-simulator" }
}
}
{
"mcpServers": {
"xc-project": { "command": "xc-project" },
"xc-build": { "command": "xc-build" },
"xc-simulator": { "command": "xc-simulator" },
"xc-device": { "command": "xc-device" },
"xc-debug": { "command": "xc-debug" },
"xc-swift": { "command": "xc-swift" }
}
}
{
"mcpServers": {
"xc-mcp": { "command": "xc-mcp" }
}
}
| Task | Recommended Approach |
|---|---|
| Edit .xcodeproj file | MCP xc-project |
| Build and run iOS app | MCP xc-simulator build_run_sim |
| Take screenshot | MCP xc-simulator screenshot |
| Debug crash | MCP xc-debug |
| Build Swift package | MCP xc-swift or Bash swift build |
| List schemes | Bash xcodebuild -list |
| Query build settings | Bash xcodebuild -showBuildSettings |
| Install on device | MCP xc-device |
If no MCP server is configured for a capability:
Diagnose and resolve Xcode build system issues when programmatically creating or modifying Xcode project files via XcodeProj. Use when: (1) working on PreviewCaptureTool.swift or any code that injects targets into .xcodeproj files, (2) debugging xcodebuild failures for injected/preview host targets, (3) encountering linker errors like undefined symbols, missing dylibs, or empty framework bundles, (4) investigating .debug.dylib crashes or _relinkableLibraryClasses errors, (5) dealing with mergeable library issues or SPM transitive dependency linking failures, (6) user mentions "preview capture build", "inject target", or "xcodebuild linker error".
Write and maintain DocC documentation for Swift modules. Use when: (1) Creating new Documentation.docc catalogs (2) Writing or editing Main.md landing pages (3) Adding articles or guides to documentation (4) Documenting symbols with triple-slash comments (5) Organizing Topics sections (6) Adding images, diagrams, or code examples to docs (7) Fixing DocC build warnings or broken links (8) User mentions "documentation", "docc", "docs", or asks to document code