Ios Dev logo

Ios Dev

Organization
Prisma-Labs-Dev
ios-dev

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.

Overview

PublisherPrisma-Labs-Dev
Repositoryapple-skills
Skill nameios-dev
Stars
348
Forks
21
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Prisma-Labs-Dev on GitHub. Read the source before you install it.

Installation

Install the Ios Dev AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Prisma-Labs-Dev/apple-skills/tree/main/skills/ios-dev
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Prisma-Labs-Dev/apple-skills.git /tmp/apple-skills
mkdir -p .claude/skills
cp -r /tmp/apple-skills/skills/ios-dev .claude/skills/ios-dev
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ios Dev in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ios Dev on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ios Dev is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 hig and ios-liquid-glass skills 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

  1. Read the code and identify which topics apply
  2. Run the Correctness Checklist below — violations are bugs
  3. Use the Topic Router to load the relevant guide for each topic
  4. For API correctness, grep the matching framework reference skill

Improve existing code

  1. Run the correctness checklist first
  2. For performance issues: use guide-swiftui-performance-audit
  3. For navigation, state, or pattern questions: use Apple's swiftui-specialist (shipped with Xcode 27; exported to the user skills dir), then the swiftui API reference
  4. For API details: grep the matching framework reference skill

Build a new feature

  1. Design data flow first — identify owned vs. injected state
  2. For UI patterns and app wiring: use Apple's swiftui-specialist, then the swiftui API reference
  3. For API details: grep the matching framework reference skill
  4. Structure views for optimal diffing — extract subviews early
  5. 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.

TopicGuideAPI Reference
State managementswiftui-specialist (Apple, Xcode 27)swiftui (state.md, binding.md, observation.md, environment.md)
View composition—swiftui (view-protocol.md)
Performanceguide-swiftui-performance-audit—
Navigationswiftui-specialist (Apple, Xcode 27)swiftui (navigationstack.md, navigationsplitview.md, navigationlink.md)
Sheets & modalsswiftui-specialist (Apple, Xcode 27)swiftui (sheet.md, inspector.md, alert.md, confirmationdialog.md)
Lists & ForEachswiftui-specialist (Apple, Xcode 27)swiftui (list.md)
ScrollViewswiftui-specialist (Apple, Xcode 27)swiftui (scrollview.md)
Forms & input—swiftui (form.md, textfield.md, picker.md, toggle.md, slider.md)
Chartsguide-swiftui-chartsswiftui (chart.md, charts-overview.md)
Animationsswiftui-specialist (Apple, Xcode 27)swiftui (swiftui-overview.md)
Layoutswiftui-specialist (Apple, Xcode 27)swiftui (geometryreader.md, grid.md, hstack.md, vstack.md, zstack.md, spacer.md)
TabViewswiftui-specialist (Apple, Xcode 27)swiftui (tabview.md)
Liquid Glass—ios-liquid-glass
Accessibilityswiftui-specialist (Apple, Xcode 27)hig (a11y/ergonomic facts)
macOS appsguide-macos-spm-packagingswiftui, uikit
Data persistenceguide-swiftdataswiftdata
Testingguide-swift-testingswift-testing, xcuitest
Concurrencyguide-swift-concurrencyswift-concurrency
In-app purchases—storekit
Maps—mapkit
Health data—healthkit
Notifications—usernotifications
App Intents / Siriapp-intents-specialist, app-intents-whats-new-27 (Apple, Xcode 27)—
Widgets—widgetkit
App Store metadataapple-aso—
Finding docsapple-docs-index—

Correctness Checklist

These are hard rules — violations are always bugs:

  • @State properties are private
  • @Binding only where a child needs to mutate parent state
  • Values passed in are never declared as @State — they silently ignore updates
  • Use @State with @Observable classes — not @StateObject or ObservableObject
  • Use @Bindable for injected observables that need bindings
  • ForEach uses stable identity — never .indices on dynamic content
  • Each ForEach element produces a constant number of views
  • .animation(_:value:) always includes the value: parameter
  • @FocusState properties are private
  • @Observable classes are @MainActor — Swift 6 strict concurrency requires it
  • Property wrappers (@AppStorage, @SceneStorage, @Query) inside @Observable classes are marked @ObservationIgnored — they conflict with the macro and cause compiler errors
  • No business logic in body — use .task, .onChange, or methods
  • No AnyView unless 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

Frequently asked questions

What does the Ios Dev AI skill do?

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.

Why use Ios Dev on TypingMind?

Because you install it once and use it with any model. Ios Dev is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ios Dev in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Prisma-Labs-Dev/apple-skills/tree/main/skills/ios-dev. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ios Dev?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ios Dev?

As many as you like. As long as a model supports skills, you can use Ios Dev with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ios Dev AI skill free?

Yes. It is published on GitHub by Prisma-Labs-Dev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇