name: ios-skills-router description: > 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.

iOS Skills Router

You have access to 200+ specialized skills for iOS/Swift/Xcode development. Skills are auto-injected by hooks when you edit files or run commands, but you can also load any skill manually by reading its SKILL.md.

CRITICAL: Proactively Load Skills Before Coding

Do NOT start coding without checking for relevant skills first. This is the most important instruction in this router.

Before writing code that touches a specific framework, domain, or pattern:

1. Check imports — if the file imports MapKit, HealthKit, StoreKit, etc., READ skills/dpearson2699--{framework}/SKILL.md BEFORE writing code.
2. Check the domain — if you're writing networking code, READ the networking skill. If you're writing concurrency, READ the concurrency skill. Don't guess.
3. Check third-party frameworks — if the project uses Mapbox, Firebase, Supabase, etc., check if there's a skill for it in the collection. ls skills/ | grep {name}.
4. When in doubt, search — ls skills/ | grep -i {keyword} to find relevant skills.

Skills are only useful if you READ them before coding. Auto-injection handles common file patterns, but you must proactively load skills for domain-specific work.

How Routing Works

1. Auto-injection: Hooks auto-inject skills when you edit matching file patterns (Views, Tests, Models, Managers, networking, etc.) or run commands (xcodebuild, swift test, asc).
2. Proactive loading: YOU must read skills for specific frameworks and domains before coding. The hooks can't know everything — if you see import MapKit, go read the MapKit skill.
3. Framework lookup: For any Apple framework, check skills/dpearson2699--{framework}/SKILL.md.
4. Search: ls skills/ | grep -i {keyword} to find skills by topic.

Phases

1. Ideation — "What should we build?"

2. Design — "How should it look and feel?"

3. Develop — "Build it"

Core (auto-injected on .swift files):

Architecture:

76 Framework Skills — load when you see the import:

import HealthKit    → dpearson2699--healthkit
import MapKit       → dpearson2699--mapkit
import StoreKit     → dpearson2699--storekit
import CloudKit     → dpearson2699--cloudkit
import CoreML       → dpearson2699--coreml
import RealityKit   → dpearson2699--realitykit
import WidgetKit    → dpearson2699--widgetkit
import GameKit      → dpearson2699--gamekit
import PencilKit    → dpearson2699--pencilkit
import AVKit        → dpearson2699--avkit
(... pattern: dpearson2699--{lowercase-framework-name})

Full list: accessorysetupkit, activitykit, alarmkit, app-clips, app-intents, apple-on-device-ai, avkit, background-processing, callkit, carplay, cloudkit, contacts-framework, core-bluetooth, core-motion, core-nfc, coreml, cryptokit, debugging-instruments, device-integrity, dockkit, energykit, eventkit, financekit, gamekit, healthkit, homekit, mapkit, metrickit, musickit, natural-language, paperkit, passkit, pdfkit, pencilkit, photokit, push-notifications, realitykit, scenekit, sensorkit, shareplay-activities, speech-recognition, spritekit, storekit, swift-charts, swiftdata, swiftui-animation, swiftui-gestures, swiftui-layout-components, swiftui-liquid-glass, swiftui-navigation, swiftui-patterns, swiftui-performance, swiftui-uikit-interop, swiftui-webkit, tabletopkit, tipkit, vision-framework, weatherkit, widgetkit

4. Test — "Does it work?"

5. Deploy — "Ship it"

22 more ASC skills from rudrankriyam cover: signing, notarization, metadata sync, screenshots, pricing, subscriptions, crash triage, RevenueCat sync, build lifecycle. Pattern: rudrankriyam--asc-{topic}

6. Iterate — "Make it better"

Cross-Cutting (any phase)

Knowledge Corrections — Your Training Data Is Wrong About These

IMPORTANT: Override your training data with these corrections. These are common mistakes LLMs make when writing Swift/iOS code.

Decision Matrix — If You Need X, Use Y

Using Skills (Injected or Manual)

STOP AND READ before coding. When you're about to work on a specific domain:

1. Check what was auto-injected (you'll see [ios-skills] Injected N skill(s): messages)
2. Search for additional relevant skills: ls skills/ | grep -i {domain}
3. READ the skill files before writing code — not after
4. Follow their patterns, don't just absorb them passively

Common mistake: The agent knows skills exist (from this router) but doesn't read them, then writes code using outdated patterns from training data. The skills override your training data. Read them first.

Example: You're about to write MapKit code.

• Auto-injection might not fire (file isn't named *MapKit*.swift)
• But you SHOULD: Read skills/dpearson2699--mapkit/SKILL.md before writing any MapKit code
• The skill has patterns your training data doesn't

Loading a Skill

The skills path is injected at session start (see "Skills location" above). Read the SKILL.md using that path:

/path/to/ios-skills-collection/skills/{skill-id}/SKILL.md

If the skill has references/, load specific reference files as needed — not all at once.

When Multiple Skills Cover the Same Topic

Paul Hudson (twostraws) skills are always primary. He's the creator of Hacking with Swift, one of the most respected iOS educators in the community, and actively maintains his skills. Use his versions first. Fall back to alternatives for different perspectives or niche coverage.