xcode-app-project-workflow

Route broad legacy Xcode requests to narrower build, run, or test workflows.

6|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/gaelic-ghost/socket --skill xcode-app-project-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xcode-app-project-workflow
Source: https://github.com/gaelic-ghost/socket/tree/main/plugins/apple-dev-skills/skills/xcode-app-project-workflow
Command: npx skills add https://github.com/gaelic-ghost/socket --skill xcode-app-project-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Broad or legacy Xcode execution references can block progress during migration. This surface routes those requests to the appropriate narrower owners (xcode-build-run-workflow or xcode-testing-workflow) while preserving the direct .pbxproj warning boundary.

Core Features & Use Cases

  • Compatibility routing: forwards broad Xcode tasks to the correct specialized skill (build/run/diagnostics or tests).
  • Migration-safe: supports ongoing transitions from legacy names to narrower execution surfaces without breaking prompts or documentation.
  • Safety boundary: maintains the explicit .pbxproj mutation warning policy when routing mutation-related requests.

Quick Start

Provide a broad Xcode task name or request, and the skill will route it to the appropriate narrower workflow (xcode-build-run-workflow or xcode-testing-workflow) while preserving the direct .pbxproj warning boundary.

Frequently Asked Questions about xcode-app-project-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route legacy Xcode build requests during a workflow migration?

Legacy Xcode build requests are routed to the xcode-build-run-workflow skill, which handles build, run, and diagnostics execution while preserving the .pbxproj warning boundary.

What's the best way to migrate broad Xcode testing tasks to a narrower workflow?

Broad Xcode testing tasks are forwarded to the xcode-testing-workflow skill, ensuring test execution is handled by the appropriate specialized surface during migration.

Does this Xcode routing approach maintain .pbxproj mutation warnings?

Yes, the routing policy explicitly maintains the direct .pbxproj mutation warning boundary, ensuring safety checks are preserved when forwarding requests to build or testing workflows.

Can I use this routing workflow for ongoing migration from legacy Xcode names?

Yes, the routing workflow is migration-safe and supports ongoing transitions from legacy names to narrower execution surfaces without breaking existing prompts or documentation references.

How does Xcode compatibility routing work for broad execution references?

Compatibility routing uses a Python script to evaluate broad or legacy Xcode execution references and forwards them to either the build-run or testing workflow based on the request type.

When do I need to use a routing workflow for Xcode tasks?

You need this routing workflow when broad or legacy Xcode execution references block progress during migration and must be redirected to the correct specialized workflow owner.