Route Apple platform development tasks
native-ios-orchestratorskillsetup L3★0
Sheshiyer/skill-clusters ↗What it does
Route native iOS/macOS tasks to specialist spokes
Best for
Single entry point for all native Apple-platform work, ensuring consistent baseline and isolating concerns across 7+ specialist skills.
Inputs
- · [object Object]
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · native-ios-core (baseline reference)
- · 7 architecture spokes (swift-concurrency-6-2, swiftui-patterns, swift-actor-persistence, swift-protocol-di-testing, foundation-models-on-device, liquid-glass-design, ios-icon-gen)
- · folded spokes (mobile-ios-design, watchos)
- · picked-up spokes (swift-concurrency-expert, swiftui-ui-patterns, swiftui-view-refactor, swiftui-performance-audit, swiftui-liquid-glass, ios-debugger-agent, app-store-changelog, macos-menubar-tuist-app, macos-spm-app-packaging)
Preconditions
- · User has native iOS/macOS app target
- · Task clearly maps to one concern (concurrency, state, persistence, testing, AI, design, or icons)
- · Xcode 26 / Swift 6.2 baseline understood
Failure modes
- · Confusing architecture spoke (how to design) with picked-up spoke (how to fix/audit/ship)
- · Routing to wrong spoke because task is too vague
- · Skipping native-ios-core baseline read before adopting new concurrency
Trust signals
- · Explicit layer × concern map
- · Clear spoke roles and routing rules
- · Distinction between architecture and picked-up spokes
- · Cross-cutting baseline (native-ios-core) ensures consistency