ios-dev
Skill336 starsChanged 7 months agoMITView on GitHub
Start here for any iOS or SwiftUI task. Coordinates best-practice guides, correctness checks, and full Apple API references. Use before navigating to other Apple skills — for building, reviewing, refactoring, or debugging iOS apps.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- OpenMinis/MinisSkillstheir own version, first seen Oct 25, 2026
- Sean-Michael/skillstheir own version, first seen Mar 18, 2026
- AlphaSquadTech/ios-devtheir own version, first seen Feb 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- OpenMinis/MinisSkills★ 602same name
- AlphaSquadTech/ios-dev★ 2same name
- Sean-Michael/skills★ 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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apple-asoSkill
- apple-docs-indexSkill
- backgroundtasksSkill
- combineSkill
- core-animationSkill
- corehapticsSkill
- eventkitSkill
- guide-macos-spm-packagingSkill
- guide-swift-concurrencySkill
- guide-swiftdataSkill
- guide-swift-testingSkill
- guide-swiftui-chartsSkill
- guide-swiftui-performance-auditSkill
- healthkitSkill
- higSkill
- ios-liquid-glassSkill
- mapkitSkill
- photosuiSkill
- storekitSkill
- swift-concurrencySkill
- swiftdataSkill
- swift-testingSkill
- swiftuiSkill
- tipkitSkill
- uikitSkill
- usernotificationsSkill
- widgetkitSkill
- xcuitestSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Start here. This skill coordinates the Apple skills collection — it tells you *which* skill to use and *when*, so you get opinionated …
- Distinctive: line 14
Do not enforce specific architectures (MVVM, VIPER, MV, TCA, etc.) — encourage separating business logic from views without mandating how
- Distinctive: line 18
When you need exact API details, grep the framework reference skills — they contain full Apple documentation
- Distinctive: line 24
Read the code and identify which topics apply
- Distinctive: line 25
Run the Correctness Checklist below — violations are bugs
- Distinctive: line 26
Use the Topic Router to load the relevant guide for each topic
- Distinctive: line 31
Run the correctness checklist first
- Distinctive: line 42
Run the correctness checklist before finishing
“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 Development
Start here. This skill coordinates the Apple skills collection — it tells you which skill to use and when, so you get opinionated guidance and full API references together.
Operating Rules
- SwiftUI and UIKit are both first-class — pick whichever fits the task. UIKit is a valid choice whenever it gives more control or flexibility; when bridging the two, watch state sync, lifecycle, and animation/environment boundaries.
- Do not enforce specific architectures (MVVM, VIPER, MV, TCA, etc.) — encourage separating business logic from views without mandating how
- Hold a high bar for UI craft: apps should feel current-generation — fluid, design-forward, alive. Sweat the tiny details. Custom components, novel interactions, and custom Metal shaders are all in-bounds when they serve the experience; system defaults are a floor, not a ceiling.
- Do not prescribe how that craft is delivered — no house style, no "Apple-approved" gatekeeping, no aesthetic checklists. Design direction is your own judgment call, made per app. The
higandios-liquid-glassskills document what the system provides; they are references, not style mandates. When the task is designing a screen or making it look good, there is no doc to route to — design from your own taste; grep references only when you need API mechanics or a factual minimum (e.g. hit-target sizes). - Present performance optimizations as suggestions backed by reasoning, not blanket requirements
- When you need exact API details, grep the framework reference skills — they contain full Apple documentation
Task Workflows
Review existing code
- Read the code and identify which topics apply
- Run the Correctness Checklist below — violations are bugs
- Use the Topic Router to load the relevant guide for each topic
- For API correctness, grep the matching framework reference skill
Improve existing code
- Run the correctness checklist first
- For performance issues: use
guide-swiftui-performance-audit - For navigation, state, or pattern questions: use Apple's
swiftui-specialist(shipped with Xcode 27; exported to the user skills dir), then theswiftuiAPI reference - For API details: grep the matching framework reference skill
Build a new feature
- Design data flow first — identify owned vs. injected state
- For UI patterns and app wiring: use Apple's
swiftui-specialist, then theswiftuiAPI reference - For API details: grep the matching framework reference skill
- Structure views for optimal diffing — extract subviews early
- Run the correctness checklist before finishing
Topic Router
The Guide column has opinionated, short pattern guides. The API Reference column has full Apple documentation as grepable Markdown — use apple-docs-index to find which framework has what.
| Topic | Guide | API Reference |
| State management | swiftui-specialist (Apple, Xcode 27) | swiftui (state.md, binding.md, observation.md, environment.md) |
| View composition | — | swiftui (view-protocol.md) |
| Performance | guide-swiftui-performance-audit | — |
| Navigation | swiftui-specialist (Apple, Xcode 27) | swiftui (navigationstack.md, navigationsplitview.md, navigationlink.md) |
| Sheets & modals | swiftui-specialist (Apple, Xcode 27) | swiftui (sheet.md, inspector.md, alert.md, confirmationdialog.md) |
| Lists & ForEach | swiftui-specialist (Apple, Xcode 27) | swiftui (list.md) |
| ScrollView | swiftui-specialist (Apple, Xcode 27) | swiftui (scrollview.md) |
| Forms & input | — | swiftui (form.md, textfield.md, picker.md, toggle.md, slider.md) |
| Charts | guide-swiftui-charts | swiftui (chart.md, charts-overview.md) |
| Animations | swiftui-specialist (Apple, Xcode 27) | swiftui (swiftui-overview.md) |
| Layout | swiftui-specialist (Apple, Xcode 27) | swiftui (geometryreader.md, grid.md, hstack.md, vstack.md, zstack.md, spacer.md) |
| TabView | swiftui-specialist (Apple, Xcode 27) | swiftui (tabview.md) |
| Liquid Glass | — | ios-liquid-glass |
| Accessibility | swiftui-specialist (Apple, Xcode 27) | hig (a11y/ergonomic facts) |
| macOS apps | guide-macos-spm-packaging | swiftui, uikit |
| Data persistence | guide-swiftdata | swiftdata |
| Testing | guide-swift-testing | swift-testing, xcuitest |
| Concurrency | guide-swift-concurrency | swift-concurrency |
| In-app purchases | — | storekit |
| Maps | — | mapkit |
| Health data | — | healthkit |
| Notifications | — | usernotifications |
| App Intents / Siri | app-intents-specialist, app-intents-whats-new-27 (Apple, Xcode 27) | — |
| Widgets | — | widgetkit |
| App Store metadata | apple-aso | — |
| Finding docs | apple-docs-index | — |
Correctness Checklist
These are hard rules — violations are always bugs:
@Stateproperties areprivate@Bindingonly where a child needs to mutate parent state- Values passed in are never declared as
@State— they silently ignore updates - Use
@Statewith@Observableclasses — not@StateObjectorObservableObject - Use
@Bindablefor injected observables that need bindings ForEachuses stable identity — never.indiceson dynamic content- Each
ForEachelement produces a constant number of views .animation(_:value:)always includes thevalue:parameter@FocusStateproperties areprivate@Observableclasses are@MainActor— Swift 6 strict concurrency requires it- Property wrappers (
@AppStorage,@SceneStorage,@Query) inside@Observableclasses are marked@ObservationIgnored— they conflict with the macro and cause compiler errors - No business logic in
body— use.task,.onChange, or methods - No
AnyViewunless truly unavoidable — fix with better composition
Related Skills
System API reference:
/ios-liquid-glass— Liquid Glass API reference
Workflow guides:
/swiftui-specialist— Apple's SwiftUI best practices (Xcode 27): structure, data flow, environment, ForEach identity, localization, soft deprecations/swiftui-whats-new-27— iOS 27 SwiftUI changes (@State macro, @ContentBuilder, reorderable, toolbar overflow)/guide-swiftui-charts— Marks, axes, selection, styling, accessibility/guide-swiftui-performance-audit— Diagnose and fix performance issues/guide-swift-testing— Swift Testing patterns, async tests, common agent mistakes/guide-swift-concurrency— Concurrency patterns, actors, diagnostics, bug patterns/guide-swiftdata— SwiftData patterns, predicates, CloudKit constraints/guide-macos-spm-packaging— Build macOS apps with SwiftPM
Utilities:
/apple-docs-index— Find the right Apple documentation/apple-aso— App Store Optimization
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.

