About this skill
A reusable General skill centered on xcode-mcp (for pi agent). It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Use this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable General skill centered on xcode-mcp (for pi agent). It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Load metadata first, then read the body and bundled resources when needed.
Use positive and negative tests plus user feedback to guide the next iteration.
Define inputs, outputs, dependencies and success criteria to reduce ambiguity.
Skill files
---
name: xcode-mcp-for-pi-agent
description: Guidelines for efficient Xcode MCP tool usage via mcporter CLI. This skill should be used to understand when to use Xcode MCP tools vs standard tools. Xcode MCP consumes many tokens - use only for build, test, simulator, preview, and SourceKit diagnostics. Never use for file read/write/grep operations. Use this skill whenever working with Xcode projects, iOS/macOS builds, SwiftUI previews, or Apple platform development.
---
# Xcode MCP Usage Guidelines
Xcode MCP tools are accessed via `mcporter` CLI, which bridges MCP servers to standard command-line tools. This skill defines when to use Xcode MCP and when to prefer standard tools.
## Setup
Xcode MCP must be configured in `~/.mcporter/mcporter.json`:
```json
{
"mcpServers": {
"xcode": {
"command": "xcrun",
"args": ["mcpbridge"],
"env": {}
}
}
}
```
Verify the connection:
```bash
mcporter list xcode
```
---
## Calling Tools
All Xcode MCP tools are callenamexcode-mcp (for pi agent)descriptionUse this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable General skill centered on xcode-mcp (for pi agent). It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.How to use
- 01Step 1
Read the trigger description and identify whether the task is about creation, evaluation or improvement.
- 02Step 2
Open SKILL.md and confirm the input, output and bundled resource requirements.
- 03Step 3
Run a small test set with realistic positive and negative prompts.
- 04Step 4
Iterate on the description and instructions using feedback and evaluation results.
Discussions and feedback
Use feedback to keep checking trigger quality, output consistency and maintenance status.