86 Self-Contained Agent Skills for iOS 26 and Swift 6.3

Ask a general-purpose agent for SwiftUI help and you get the average of its training data — including the deprecated patterns Apple retired years ago. dpearson2699/swift-ios-skills, a 1k-star collection, ships 86 agent skills that target iOS 26+ with Swift 6.3 and the frameworks that shipped alongside: Liquid Glass, approachable concurrency, Foundation Models, StoreKit 2, SwiftData, and async/await URLSession. The README's own standard: "No deprecated patterns."

Why This Skill Matters

Two design decisions separate this from a single mega-skill. First, every skill is self-contained — no skill references another, so you install exactly the frameworks your project touches and nothing else rides into your context window. Second, the set is complete enough to live in: the README's tables enumerate 10 SwiftUI skills, 10 Core Swift skills, 15 app-experience framework skills, 8 data and service skills, 5 AI/ML skills, 16 iOS-engineering skills, 8 hardware-integration skills, 10 platform-integration skills, and 4 gaming skills — 86 in total, each following the open Agent Skills standard (SKILL.md plus an optional references/ folder).

The coverage is current in ways that matter: swiftui-liquid-glass documents glassEffect and GlassEffectContainer, apple-on-device-ai covers the Foundation Models framework and MLX Swift, and swift-concurrency teaches Swift 6.2 concurrency with data-race safety.

Installation

The recommended path is the skills CLI, which opens an interactive picker:

npx skills add dpearson2699/swift-ios-skills

Install the full set non-interactively with --all, or named skills with repeatable --skill <skill-name> flags; npx skills check and npx skills update keep installed copies current.

Claude Code users can go through the plugin marketplace instead:

/plugin marketplace add dpearson2699/swift-ios-skills
/plugin install all-ios-skills@swift-ios-skills

Themed bundles exist too (swiftui-skills, ios-ai-ml-skills, apple-kit-skills and more) — but note the README's own guidance: bundles limit how many skills load into the context window, so if you want everything, install all-ios-skills rather than stacking multiple bundles.

Real Workflow: Add StoreKit 2 Purchases

Suppose your app is about to grow a subscription. Install just the storekit skill, then delegate:

1. Pull the single skill you need:

npx skills add dpearson2699/swift-ios-skills --skill storekit

2. Ask your agent for the feature. The skill's coverage spans StoreKit 2 purchases, subscriptions, SubscriptionStoreView, and transaction verification, so the implementation comes from current API documentation patterns instead of memorized Sample Code.

3. Because each skill is self-contained, removing it later leaves no dangling references in your project instructions.

Real Workflow: Debug With the Engineering Bundle

The 16 engineering skills read like a senior iOS engineer's toolkit: debugging-instruments (Xcode debugger, Instruments, os_signpost, MetricKit), ios-memgraph-analysis (simulator memgraph capture, leak ownership paths), ios-ettrace-performance (ETTrace launch capture with exact-build dSYM matching), plus swift-security, swiftlint, and ios-simulator. When a launch-time regression lands, these give the agent the profiling vocabulary and commands to investigate instead of guessing.

Tips

• Six framework skills are beta-bound: permissionkit, energykit, paperkit, relevancekit, appmigrationkit, and audioaccessorykit require the iOS/watchOS 26 beta and may change before GM.
• Upgrading from v2.x? v3.0 renamed 12 skills to Apple Kit framework names, and old skill paths no longer resolve — uninstall everything and reinstall rather than mixing generations.
• The README claims compatibility with Claude Code, Codex, Cursor, GitHub Copilot, and 40+ other agents through the Agent Skills standard.
• Codex installs one skill at a time via $skill-installer, pointing at the skill's directory URL.

When Not to Use This

The license is PolyForm Perimeter 1.0.0: building your app with these skills is allowed, but rebranding and reselling the collection as your own product is not. If your codebase is pinned to older deployment targets, iOS 26-first guidance may reference APIs you cannot ship yet. And the project is independent — the README states it is not affiliated with or endorsed by Apple, so treat its guidance as a community reference alongside official documentation, not a substitute for it.

See the leaderboard for more skills.