Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

$pwd:

xcodebuildmcp

Name: Xcodebuildmcp
Author: JordanCoin

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

Exécuter dans Manus

$ git log --oneline --stat

stars:2

forks:0

updated:30 mars 2026 à 02:32

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

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

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://github.com/getsentry/XcodeBuildMCP/blob/main/docs/CONFIGURATION.md 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.

related-skills.json

même dépôt

ios-skills-router.md

from "JordanCoin/ios-skills-collection"

Always use when working on any iOS, macOS, Swift, SwiftUI, Xcode, or Apple platform project. Routes to the correct specialized skills based on development phase and task context. This collection contains 210 skills from 28 authors covering the full iOS lifecycle.

2026-03-312

aso-appstore-screenshots.md

from "JordanCoin/ios-skills-collection"

Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.

2026-03-302

xcode-preview-capture.md

from "JordanCoin/ios-skills-collection"

Build and capture Xcode/SwiftUI previews for visual analysis. Use when you need to see rendered UI output, verify layouts, or inspect visual components.

2026-03-302

motioneyes-animation-debug.md

from "JordanCoin/ios-skills-collection"

Diagnose, fix, or validate SwiftUI animation and scroll behavior by temporarily instrumenting views with MotionEyes, capturing console traces over time, and comparing motion data to user intent or test expectations. Use when users report bugs such as wrong direction, premature fade, timing or easing mismatch, unexpected movement, missing movement, incorrect relative movement between views, scroll jumps, scroll restoration drift, content-offset desynchronization, or when they want to turn MotionEyes traces into focused assertions. Prefer XcodeBuildMCP log capture first and fallback to CLI log streaming; remove only agent-added MotionEyes instrumentation after validation.

2026-03-302

motioneyes-visual-analysis.md

from "JordanCoin/ios-skills-collection"

Pixel-based motion and UI change analysis from frame sequences or screenshots using computer vision and visual comparison. Use when `.transition` or visual effects are not observable via MotionEyes logs, when you only have screenshots/video, when you need regression diffs across builds, or when you need to summarize on-screen changes without instrumentation. Do not use when MotionEyes traces are available and you need precise timing/values; use `motioneyes-animation-debug` instead.

2026-03-302

apple-docs-mcp.md

from "JordanCoin/ios-skills-collection"

MCP server for Apple Developer Documentation. Search iOS/macOS/SwiftUI/UIKit docs, WWDC videos with transcripts, sample code, and framework APIs. Use when you need to look up Apple APIs, check platform compatibility, find WWDC sessions, or browse framework symbols. Install the MCP server first, then use its tools.

2026-03-302

package.json

"author": "JordanCoin"

"repository": "JordanCoin/ios-skills-collection"

Ouvrir le dépôt GitHub Voir les dépôts du créateur

$ install --global

$ download --local

Exécuter dans Manus

$ useful --forSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

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

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.

xcodebuildmcp

XcodeBuildMCP

Step 1: Establish Session Context

Step 2: Understand Workflow-Scoped Tool Availability

Step 3: Report Context Clearly

Plus depuis ce dépôt

Plus depuis ce dépôt

XcodeBuildMCP

Step 1: Establish Session Context

Step 2: Understand Workflow-Scoped Tool Availability

Step 3: Report Context Clearly