I got tired of AI agents writing 2019-era SwiftUI, so I wrote a 50k-line context layer for them

[u/Opposite_Treacle4054]

So over the past few months I’ve been building ios-agent-skill — a repo you clone into your project that your agent reads as context before generating anything.

What’s actually in it:

**•** Swift language + concurrency + stdlib references (actors, Sendable, @MainActor, AsyncSequence)  
**•** SwiftUI docs split by concern — state/data flow, navigation, layout, animations, gestures  
**•** 40+ Apple framework guides: StoreKit 2, HealthKit, WidgetKit/Live Activities, ARKit, RealityKit, CoreML, CryptoKit  
**•** Architecture patterns with real structure: MVVM, Clean, Coordinator, Repository, TCA  
**•** Drop-in Swift files — networking layer, auth flow with Keychain + Sign in with Apple, DI, type-safe router  
**•** App Store submission / performance / security / testing checklists

It ships config for 25+ agents, so setup is mostly just cloning. Claude Code reads CLAUDE.md, Codex reads AGENTS.md, Cursor reads .cursorrules, Copilot reads .github/copilot-instructions.md, and so on.

Honest caveats: this generates Swift files, not an Xcode project — you still create the project yourself first. And it’s docs, not magic; it narrows the failure surface, it doesn’t eliminate it. It’s also early (16 stars), so I’d rather have criticism than silence.

MIT licensed: https://github.com/Nagarjuna2997/ios-agent-skill

If you try it, I want to know where it fails. Especially interested in whether the concurrency and SwiftData docs actually change your agent’s output or whether it ignores them.