ios
Skill37 starsChanged 36 days agoMITView on GitHub
Use when building native iOS applications. Covers SwiftUI architecture, state management, navigation, networking, persistence, background behavior, and App Store submission requirements. Trigger on "structure my swiftui app", "deep links open the wrong screen", "background fetch isn't running". Do not use for Swift language issues like concurrency or optionals — see the swift skill; for signing and rollout, see the mobile-release skill.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- glowingkitty/OpenMatestheir own version, first seen Oct 8, 2026
- hebertzhu/agent-foundrytheir own version, first seen Mar 27, 2026
- kingsidharth/skillstheir own version, first seen Mar 16, 2026
- ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- glowingkitty/OpenMates★ 53same name
- kingsidharth/skills★ 17same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- hebertzhu/agent-foundry★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository137 other files it gives its agents.
- agent-instructionsSkill
- agent-memorySkill
- hooksSkill
- plugin-developmentSkill
- skill-authoringSkill
- skill-reviewSkill
- slash-commandsSkill
- subagentsSkill
- agent-designSkill
- context-engineeringSkill
- fine-tuningSkill
- llm-cost-optimizationSkill
- llm-evaluationSkill
- llm-integrationSkill
- mcp-serverSkill
- ml-pipelineSkill
- model-selectionSkill
- prompt-engineeringSkill
- ragSkill
- structured-outputSkill
- api-designSkill
- background-jobsSkill
- cachingSkill
- djangoSkill
- event-driven-architectureSkill
- fastapiSkill
- graphqlSkill
- microservicesSkill
- nestjsSkill
- realtime-websocketsSkill
- spring-bootSkill
- competitive-analysisSkill
- lead-researchSkill
- product-analysisSkill
- resumeSkill
- user-researchSkill
- database-performanceSkill
- data-modelingSkill
- data-qualitySkill
- pandasSkill
- postgresSkill
- sparkSkill
- brand-guidelinesSkill
- generative-artSkill
- themingSkill
- ui-reviewSkill
- visual-designSkill
- architecture-decisionsSkill
- bug-fix-protocolSkill
- cli-developmentSkill
- code-reviewSkill
- debuggingSkill
- design-patternsSkill
- domain-modelingSkill
- git-workflowSkill
- legacy-modernizationSkill
- refactoringSkill
- repository-explorationSkill
- simple-designSkill
- system-designSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
Never do work in a view's body.
- Distinctive: line 58
Test on the oldest supported device you claim to support, not the newest simulator.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
iOS
Purpose
Build iOS applications with a single source of truth for state, correct lifecycle handling, and an architecture that survives the App Review process without surprises.
When to Use
- Building or reviewing a SwiftUI application.
- Structuring navigation, state, and dependencies.
- Handling background execution, notifications, or deep links.
- Preparing an App Store submission.
Capabilities
- SwiftUI architecture with
@Observableand unidirectional data flow. - Navigation with
NavigationStackand type-safe routes. - Networking with async/await, retries, and offline behavior.
- Persistence: SwiftData, Core Data, Keychain.
- Background tasks, push notifications, and app lifecycle.
- App Store requirements: privacy manifest, permissions, review guidelines.
Inputs
- The feature set and the minimum supported iOS version.
- Data requirements: offline, sync, sensitive.
- Distribution target: App Store, TestFlight, enterprise.
Outputs
- Views that read state and emit intent; models that own the state.
- A navigation model that supports deep links by construction.
- A submission checklist covering permissions, privacy, and metadata.
Workflow
- Model the state — One
@Observablemodel per screen or feature. The view derives everything it displays from it; it holds no duplicate copies. - Make navigation data-driven —
NavigationStack(path:)with an enumerated route type. Deep linking then becomes "append to the path", not a second navigation system. - Handle the lifecycle — Work started in the foreground is suspended when the app is backgrounded. Anything that must complete needs a background task assertion or a background URL session.
- Design for offline — Assume the network fails. Cache, queue writes, and reconcile. On mobile this is the normal case, not the edge case.
- Prepare for review — Every permission needs a purpose string that says what the app does with it. A privacy manifest is mandatory. Rejections are almost always about permissions, purchases, or metadata.
Best Practices
- Never do work in a view's
body. It runs whenever SwiftUI decides it should, which is more often than you expect. @Statefor view-local state,@Observablemodels for anything shared. Passing a model down through six views is a sign it should be in the environment.- Long-running work never blocks the main actor. Mark it
nonisolatedor run it in a detached task and hop back to update state. - Store tokens in the Keychain, never in
UserDefaults.UserDefaultsis a plist, readable from a backup. - Test on the oldest supported device you claim to support, not the newest simulator. Performance is a feature on a four-year-old phone.
- A permission prompt with no context is a permission denial. Explain why before the system dialog appears.
Examples
Type-safe, deep-linkable navigation:
enum Route: Hashable {
case orderList
case order(id: String)
case refund(orderID: String)
}
@Observable
final class Router {
var path: [Route] = []
func handle(_ url: URL) {
// myapp://orders/ord_123/refund
guard url.host == "orders" else { return }
let parts = url.pathComponents.filter { $0 != "/" }
guard let orderID = parts.first else { return path = [.orderList] }
path = parts.contains("refund")
? [.orderList, .order(id: orderID), .refund(orderID: orderID)]
: [.orderList, .order(id: orderID)]
}
}
struct AppView: View {
@State private var router = Router()
var body: some View {
NavigationStack(path: $router.path) {
OrderListView()
.navigationDestination(for: Route.self) { route in
switch route {
case .orderList: OrderListView()
case .order(let id): OrderDetailView(orderID: id)
case .refund(let orderID): RefundView(orderID: orderID)
}
}
}
.environment(router)
.onOpenURL { router.handle($0) }
}
}Deep links reconstruct the full back stack, so the user can navigate up naturally — a detail most hand-rolled routers get wrong.
Notes
- A privacy manifest (
PrivacyInfo.xcprivacy) is required for apps and for many third-party SDKs. A missing one is an automatic rejection at submission. @Observable(iOS 17+) invalidates only the views that read the changed property, unlikeObservableObject, which invalidates every observer. It is a material performance difference on complex screens.- Background URL sessions continue after the app is suspended and even after it is terminated. They are the only reliable way to complete a large upload.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

