agentleFS
Sign inStart free
WescholmWescholm/ghostty-fleet/.agents/skills/xcodebuildmcp/SKILL.md

xcodebuildmcp

Skill1 starsChanged 8 months agoMITView on GitHub

Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use XcodeBuildMCP tools instead of raw xcodebuild, xcrun, or simctl.

    line 8
  2. Distinctive:

    Only simulator workflow tools are enabled by default.

    line 22
  3. Very specific:

    Call session_show_defaults before the first build/run/test action in a session.

    line 26
  4. Very specific:

    Use discover_projs only when defaults show missing or incorrect project/workspace context.

    line 27
  5. Very specific:

    Do not run discovery speculatively or in parallel with session_show_defaults.

    line 28
  6. Distinctive:

    Do not chain build-only then build-and-run unless the user explicitly requests both.

    line 30
  7. Distinctive:

    Not all tools are enabled by default.

    line 34
  8. Distinctive:

    If a tool is expected but missing, check enabled workflows first.

    line 35
  9. Very specific:

    Update enabled workflows in .xcodebuildmcp/config.yaml, then ask user to reload/restart the session to surface refreshes.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

XcodeBuildMCP

Use XcodeBuildMCP tools instead of raw xcodebuild, xcrun, or simctl.

Capabilities:

  • Session defaults: Configure project, scheme, simulator, and device defaults to avoid repetitive parameters
  • Project discovery: Find Xcode projects/workspaces, list schemes, inspect build settings
  • Simulator workflows: Build, run, test, install, and launch apps on iOS simulators; manage simulator state (boot, erase, location, appearance)
  • Device workflows: Build, test, install, and launch apps on physical devices with code signing
  • macOS workflows: Build, run, and test macOS applications
  • Log capture: Stream and capture logs from simulators and devices
  • LLDB debugging: Attach debugger, set breakpoints, inspect stack traces and variables, execute LLDB commands
  • UI automation: Capture screenshots, inspect view hierarchy with coordinates, perform taps/swipes/gestures, type text, press hardware buttons
  • SwiftPM: Build, run, test, and manage Swift Package Manager projects
  • Project scaffolding: Generate new iOS/macOS project templates

Only simulator workflow tools are enabled by default. If capabilities like device, macOS, debugging, or UI automation are not available, the user must configure XcodeBuildMCP to enable them. See https://xcodebuildmcp.com/docs/configuration for workflow configuration.

Step 1: Establish Session Context

  • Call session_show_defaults before the first build/run/test action in a session.
  • Use discover_projs only when defaults show missing or incorrect project/workspace context.
  • Do not run discovery speculatively or in parallel with session_show_defaults.
  • For simulator run intent, prefer the combined build-and-run tool instead of separate build then run calls.
  • Do not chain build-only then build-and-run unless the user explicitly requests both.

Step 2: Understand Workflow-Scoped Tool Availability

  • Not all tools are enabled by default; tool availability depends on enabled workflows.
  • If a tool is expected but missing, check enabled workflows first.
  • Update enabled workflows in .xcodebuildmcp/config.yaml, then ask user to reload/restart the session to surface refreshes.

Step 3: Report Context Clearly

  • Return the active defaults context used for execution (project/workspace, scheme, simulator/device).
  • For failures, include the exact failing step and the next actionable command/tool call.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free