agentleFS
wrsilvawrsilva/reis-mobile/skills/mobile-ios/SKILL.md

mobile-ios

Skill8 starsChanged 58 days agoMITView on GitHub

Builds native iOS apps in Swift — SwiftUI and UIKit screens, state and data flow, NavigationStack, lists, forms and accessibility; networking with URLSession and Codable, persistence with SwiftData, Core Data, files and the Keychain; permissions, push notifications, universal links, background tasks, widgets, App Intents and StoreKit 2 purchases; performance with Instruments and MetricKit; and release with signing, TestFlight and App Store Connect. Use when writing or changing native iOS code, adding a platform feature, preparing a build for TestFlight or the App Store, or when the user asks how to do something on iOS, even if they do not name the framework.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the deployment target (IPHONEOS_DEPLOYMENT_TARGET), the Swift language version and the Xcode version: many APIs in these guides need …

    line 23
  2. Very specific:

    Follow the project: SwiftUI or UIKit, its architecture, and dependencies already in Package.resolved or Podfile.lock.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mobile iOS

Guides for building native iOS apps. Cross-platform topics live in their own skills and have iOS references there: architecture in mobile-architecture, tests in mobile-test, debugging (Xcode, CocoaPods, crashes) in mobile-debug, code review in mobile-code-review, security in mobile-security and Firebase in mobile-firebase.

Pick the topic

TopicRead
SwiftUI and UIKit screens, navigation, lists, forms, accessibility, localizationreferences/ui-navigation.md
Networking, JSON, persistence, caching, offlinereferences/data-networking.md
Permissions, push, universal links, background work, widgets, App Intents, in-app purchasesreferences/platform-features.md
Performance, app size, signing, TestFlight and App Store releasereferences/performance-release.md

Before writing code

  • Check the deployment target (IPHONEOS_DEPLOYMENT_TARGET), the Swift language version and the Xcode version: many APIs in these guides need iOS 16 or 17, and Swift 6 changes concurrency checking.
  • Follow the project: SwiftUI or UIKit, its architecture, and dependencies already in Package.resolved or Podfile.lock.
  • Apple's requirements change every year (minimum SDK for uploads, privacy manifests, review guidelines); check the current ones instead of relying on these guides for dates or version numbers.

Interface design

For UI/UX reviews, wireframes, design systems and screen redesigns, use mobile-ui-ux and its reference for this stack. For Apple targets, also consult its Apple design workflow; validate platform claims against current official guidance and the installed toolkit.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.