Apple development skills — iOS 26+ APIs, SwiftUI, UIKit, Liquid Glass, SwiftData, and more.

version
1.0.20
GitHub stars
361

Install

/plugin install apple-skills@apple-skills

Run it inside Claude Code after adding the marketplace with /plugin marketplace add Prisma-Labs-Dev/apple-skills.

Contents

Discovered from source

Skills 29

Apple ASO (App Store Optimization)

Optimize App Store metadata following Apple's guidelines and ASO best practices to maximize visibility and downloads.

When to Use

  • Creating or editing store.config.json
  • Optimizing App Store keywords
  • Localizing app metadata for new markets
  • Reviewing existing metadata for ASO issues
  • Adding new language localizations

Character Limits

FieldLimitRanking WeightIndexed
Title30 charsHighestYes
Subtitle30 chars2nd highestYes
Keywords100 chars3rd (same as subtitle)Yes
Description4,000 charsNoneNo
Promo Text170 charsNoneNo
Release Notes4,000 charsNoneNo

Keyword Field Rules

Format

keyword1,keyword2,multi word phrase,keyword3

Critical formatting:

  • Comma-separated with NO spaces after commas (saves characters)
  • Spaces allowed within multi-word phrases
  • 100 characters total

Must Follow

  1. Never duplicate words from title/subtitle - Apple indexes them automatically
  2. Use single words when possible - Apple creates combinations automatically
  3. No plurals if you have the singular form
  4. No special characters - @, #, - are replaced with spaces
  5. No generic terms - avoid "app", "game", "free", "best", "new"
  6. No competitor names or trademarks
  7. No category names - already indexed from category selection

Should Include

  • Synonyms not in title/subtitle
  • Alternate spellings (with/without accents)
  • Related concepts and features
  • Long-tail niche terms
  • Regional variations
  • Action verbs users search for

Localization Best Practices

Apple App Store Language Codes

LanguageCodeLanguageCode
English (US)en-USGermande-DE
English (UK)en-GBFrench (France)fr-FR
English (AU)en-AUFrench (Canada)fr-CA
Spanish (Spain)es-ESPortuguese (Brazil)pt-BR
Spanish (Mexico)es-MXPortuguese (Portugal)pt-PT
ItalianitDutchnl-NL
JapanesejaRussianru
KoreankoChinese Simplifiedzh-Hans
Arabicar-SAChinese Traditionalzh-Hant

Localization Rules

  1. Don't just translate - Research native search terms
  2. Include English keywords in non-English locales (users often search in English)
  3. Remove diacritics for keywords (users skip accents when typing)
  4. Add regional terms - Different countries use different words
  5. Consider cross-localization - Apple indexes multiple locales per territory

Cross-Localization (Free Extra Keywords)

Apple indexes keywords from multiple locales per territory:

  • US: English (US) + Spanish (Mexico)
  • UK: English (UK) + English (US)
  • Canada: English (Canada) + French (Canada)
  • Australia: English (AU) + English (UK)

This effectively gives you 200 characters in some markets.

Optimization Workflow

Step 1: Analyze Current Metadata

Check for these issues:

  • Keywords duplicating title/subtitle words
  • Redundant synonyms (e.g., "kids" and "children")
  • Generic terms that waste space
  • Missing regional variants
  • Unused character space

Step 2: Research Keywords

Consider:

  • Relevance: Does it describe your app?
  • Volume: Are people searching for it?
  • Competition: Can you realistically rank?

Step 3: Optimize Keywords

  1. Remove all duplicates from title/subtitle
  2. Remove plurals if singular exists
  3. Add action verbs users search for
  4. Add regional/cultural variants
  5. Fill remaining space with related terms
  6. Remove diacritics for better matching

Step 4: Validate

  • Title ≤ 30 characters
  • Subtitle ≤ 30 characters
  • Keywords ≤ 100 characters (count with no spaces after commas)
  • No duplicates across fields
  • No prohibited terms

Example: Before & After

Before (Poor ASO)

{
  "title": "Call Santa Claus Now",
  "subtitle": "Magical Santa Voice Calls",
  "keywords": ["santa", "call santa", "santa claus", "voice call", "kids", "children"]
}

Issues:

  • "santa", "call santa", "santa claus" duplicate title
  • "voice call" duplicates subtitle
  • "kids" and "children" are synonyms

After (Optimized)

{
  "title": "Call Santa Claus Now",
  "subtitle": "Magical Santa Voice Calls",
  "keywords": "christmas,xmas,holiday,north pole,father christmas,talk,phone,festive,rudolph,elves,family"
}

Improvements:

  • No duplicates from title/subtitle
  • Regional variant (father christmas for UK)
  • Related terms (rudolph, elves, north pole)
  • Alternate spellings (xmas)
  • Action verb (talk)

store.config.json Schema

{
  "configVersion": 0,
  "apple": {
    "info": {
      "en-US": {
        "title": "App Name (max 30 chars)",
        "subtitle": "Value proposition (max 30 chars)",
        "description": "Full description (max 4000 chars)",
        "keywords": "comma,separated,no spaces,after commas",
        "releaseNotes": "What's new in this version",
        "promoText": "Short promotional text (max 170 chars)",
        "privacyPolicyUrl": "https://example.com/privacy",
        "supportUrl": "https://example.com/support",
        "marketingUrl": "https://example.com"
      }
    },
    "categories": ["PRIMARY_CATEGORY", "SECONDARY_CATEGORY"]
  }
}

Common Mistakes to Avoid

  1. Duplicating keywords across fields - Wastes precious character space
  2. Direct translation - Doesn't account for local search behavior
  3. Keyword stuffing in title - Hurts readability and conversion
  4. Ignoring subtitle - Second most important ranking factor
  5. Using spaces after commas - Wastes ~10% of keyword space
  6. Frequent changes - Wait 3-4 weeks between keyword updates
  7. Including app/game - Already indexed from category

Resources

Commands

# Push metadata to App Store
eas metadata:push

# Pull current metadata from App Store
eas metadata:pull

# Validate metadata locally
# (Check JSON syntax and character limits)

Apple Documentation Index

This skill provides indexes of Apple framework documentation. Use these to:

  • Browse available APIs in a framework
  • Find the path to specific documentation
  • Decide what detailed docs to download

Available Indexes

FrameworkFileSizeTopics
SwiftUI../swiftui/swiftui-overview.md907KBViews, modifiers, navigation, state
XCTestxctest-index.md55KBTesting, assertions, expectations
XCUIAutomationxcuiautomation-index.md58KBUI testing, elements, queries
UIKit../uikit/uikit-overview.md1.8MBViews, controllers, controls, scenes
Core Animation../core-animation/core-animation-index.md80KBCALayer, CAAnimation, CATransaction, layer subclasses
HealthKithealthkit-index.md312KBHealth data, workouts, records
Combinecombine-index.md153KBPublishers, subscribers, operators
SwiftDataswiftdata-index.md86KBModels, containers, queries
Observationobservation-index.md3KB@Observable macro

How to Use

1. Browse an Index

# See what's in HealthKit
cat healthkit-index.md | head -100

# Search for specific topic
grep -i "workout" healthkit-index.md
grep -i "navigation" ../swiftui/swiftui-overview.md

2. Find Documentation Paths

Index files list all available documentation pages. Each entry shows the path:

- [HKWorkout](/documentation/healthkit/hkworkout)
- [NavigationStack](/documentation/swiftui/navigationstack)

3. Fetch More Detailed Docs

  1. Check whether the detailed page is already available in one of your installed Apple skills.
  2. Use skill names, descriptions, or SKILL.md frontmatter to find likely skill directories, then grep their local .md files before fetching. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the same path with the sosumi.ai Markdown mirror.

For example, /documentation/healthkit/hkworkout maps to https://sosumi.ai/documentation/healthkit/hkworkout.

4. Browse Missing Framework Indexes

If the local indexes don't include the framework you need, use the framework's sosumi.ai index:

https://sosumi.ai/documentation/{framework}

For example, https://sosumi.ai/documentation/foundation provides a Markdown index you can search for Foundation paths.

If the Markdown mirror is unavailable and your environment can parse JSON, Apple's public DocC index endpoint is:

https://developer.apple.com/tutorials/data/index/{framework}

The useful path tree is under interfaceLanguages.swift[0].children.

BackgroundTasks Documentation

Search these docs to answer questions about background task APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details

Files

  • backgroundtasks-index.md - Framework overview, task types
  • bgtaskscheduler.md - Task scheduling and registration

Combine Documentation

Search these docs to answer questions about Combine APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details, e.g.:
    • combine-index.md for framework overview

Files

  • combine-index.md - Framework overview, publishers, subscribers, and operators

Core Animation Reference

Search these docs to answer questions about Core Animation (the QuartzCore framework). Use this skill when working directly with CALayer, layer-backed UIKit/AppKit views, explicit keyframe or spring animations on layer properties, particle systems, or per-frame callbacks via CADisplayLink.

For SwiftUI's declarative animation API (withAnimation, Animation, .animation(_:value:), transitions), use Apple's swiftui-specialist skill (its animations reference) instead. For SwiftUI immediate-mode drawing, use swiftui/canvas.md and swiftui/graphicscontext.md.

Return Format

Always include:

  1. Summary — answer the question concisely.
  2. File paths — list relevant files for full details, e.g.:
    • calayer.md for layer geometry, contents, hierarchy
    • cabasicanimation.md for animating a single property between two values
    • catransaction.md for batching, disabling implicit animations, or changing default duration

Files

FileContent
core-animation-index.mdFull QuartzCore framework index — layer basics, animation classes, transactions, layer subclasses
calayer.mdCALayer — the root layer class: geometry, contents, hierarchy, layout, animations
caanimation.mdCAAnimation — abstract base class for all Core Animation animation types
capropertyanimation.mdCAPropertyAnimation — abstract subclass animating a single layer property
cabasicanimation.mdCABasicAnimation — interpolate a layer property between two values
cakeyframeanimation.mdCAKeyframeAnimation — animate a property through a sequence of keyframes
caspringanimation.mdCASpringAnimation — spring-based interpolation with mass, stiffness, damping
caanimationgroup.mdCAAnimationGroup — run multiple animations together with a shared duration
catransition.mdCATransition — fade, push, reveal, and move-in transitions between layer states
camediatiming.mdCAMediaTiming — protocol shared by layers and animations (beginTime, duration, repeat, speed)
catransaction.mdCATransaction — batch property changes, disable implicit animations, set default duration/timing
catransform3d.mdCATransform3D — 4×4 matrix used by CALayer.transform for 3D transforms
cashapelayer.mdCAShapeLayer — vector-shape layer driven by a CGPath (stroke, fill, line dash)
cagradientlayer.mdCAGradientLayer — axial, radial, and conic gradient layers
caemitterlayer.mdCAEmitterLayer — particle emitter layer (fire, smoke, confetti, sparkles)
caemittercell.mdCAEmitterCell — individual particle definition used by CAEmitterLayer
careplicatorlayer.mdCAReplicatorLayer — replicate a sublayer with offsets and transforms
cametallayer.mdCAMetalLayer — layer backed by a Metal drawable for GPU-rendered content
catextlayer.mdCATextLayer — layer that renders plain or attributed text
catiledlayer.mdCATiledLayer — tile-based asynchronous content rendering for large or zoomable layers
cadisplaylink.mdCADisplayLink — timer synchronized to the display's refresh rate

When to Reach for Core Animation

  • You need to animate a layer property SwiftUI/UIKit doesn't expose declaratively (e.g., CAGradientLayer.colors, CAShapeLayer.strokeEnd, CAEmitterLayer.birthRate).
  • You need explicit keyframe or spring control with timing functions (CAMediaTimingFunction) per segment.
  • You want to batch implicit animations off (CATransaction.setDisableActions(true)).
  • You need a CADisplayLink per-frame callback (custom drawing loops, scrubbing, physics).
  • You're rendering thousands of particles with CAEmitterLayer or replicating sublayers with CAReplicatorLayer.

If your problem fits inside withAnimation { ... } in SwiftUI or UIView.animate { ... } in UIKit, prefer those — Core Animation sits underneath both and is rarely the right starting point in 2026-era code.

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills, then grep their local files.
  3. If no installed skill has the page, the QuartzCore path on Apple's site is /documentation/quartzcore/<symbol> — fetch via the sosumi.ai Markdown mirror (e.g. https://sosumi.ai/documentation/quartzcore/camediatimingfunction) or by running pnpm fetch-doc against the apple-skills tooling.

Core Haptics Documentation

Search these docs to answer questions about haptic feedback APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details

Files

  • corehaptics-index.md - Framework overview, patterns, events
  • chhapticengine.md - Haptic engine setup and playback

EventKit Documentation

Search these docs to answer questions about calendar and reminder APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details

Files

  • eventkit-index.md - Framework overview, events, reminders
  • ekeventstore.md - Event store access and permissions
  • ekreminder.md - Creating and managing reminders

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from Dimillian/Skills by Thomas Ricouard. MIT License.

macOS SwiftPM App Packaging (No Xcode)

Overview

Bootstrap a complete SwiftPM macOS app folder, then build, package, and run it without Xcode. Use assets/templates/bootstrap/ for the starter layout and references/packaging.md + references/release.md for packaging and release details.

Two-Step Workflow

  1. Bootstrap the project folder

    • Copy assets/templates/bootstrap/ into a new repo.
    • Rename MyApp in Package.swift, Sources/MyApp/, and version.env.
    • Customize APP_NAME, BUNDLE_ID, and versions.
  2. Build, package, and run the bootstrapped app

    • Copy scripts from assets/templates/ into your repo (for example, Scripts/).
    • Build/tests: swift build and swift test.
    • Package: Scripts/package_app.sh.
    • Run: Scripts/compile_and_run.sh (preferred) or Scripts/launch.sh.
    • Release (optional): Scripts/sign-and-notarize.sh and Scripts/make_appcast.sh.
    • Tag + GitHub release (optional): create a git tag, upload the zip/appcast to the GitHub release, and publish.

Minimum End-to-End Example

Shortest path from bootstrap to a running app:

# 1. Copy and rename the skeleton
cp -R assets/templates/bootstrap/ ~/Projects/MyApp
cd ~/Projects/MyApp
sed -i '' 's/MyApp/HelloApp/g' Package.swift version.env

# 2. Copy scripts
cp assets/templates/package_app.sh Scripts/
cp assets/templates/compile_and_run.sh Scripts/
chmod +x Scripts/*.sh

# 3. Build and launch
swift build
Scripts/compile_and_run.sh

Validation Checkpoints

Run these after key steps to catch failures early before proceeding to the next stage.

After packaging (Scripts/package_app.sh):

# Confirm .app bundle structure is intact
ls -R build/HelloApp.app/Contents

# Check that the binary is present and executable
file build/HelloApp.app/Contents/MacOS/HelloApp

After signing (Scripts/sign-and-notarize.sh or ad-hoc dev signing):

# Inspect signature and entitlements
codesign -dv --verbose=4 build/HelloApp.app

# Verify the bundle passes Gatekeeper checks locally
spctl --assess --type execute --verbose build/HelloApp.app

After notarization and stapling:

# Confirm the staple ticket is attached
stapler validate build/HelloApp.app

# Re-run Gatekeeper to confirm notarization is recognised
spctl --assess --type execute --verbose build/HelloApp.app

Common Notarization Failures

SymptomLikely CauseRecovery
The software asset has already been uploadedDuplicate submission for same versionBump BUILD_NUMBER in version.env and repackage.
Package Invalid: Invalid Code Signing EntitlementsEntitlements in .entitlements file don't match provisioningAudit entitlements against Apple's allowed set; remove unsupported keys.
The executable does not have the hardened runtime enabledMissing --options runtime flag in codesign invocationEdit sign-and-notarize.sh to add --options runtime to all codesign calls.
Notarization hangs / no status emailxcrun notarytool network or credential issueRun xcrun notarytool history to check status; re-export App Store Connect API key if expired.
stapler validate fails after successful notarizationTicket not yet propagatedWait ~60 s, then re-run xcrun stapler staple.

Templates

  • assets/templates/package_app.sh: Build binaries, create the .app bundle, copy resources, sign.
  • assets/templates/compile_and_run.sh: Dev loop to kill running app, package, launch.
  • assets/templates/build_icon.sh: Generate .icns from an Icon Composer file (requires Xcode install).
  • assets/templates/sign-and-notarize.sh: Notarize, staple, and zip a release build.
  • assets/templates/make_appcast.sh: Generate Sparkle appcast entries for updates.
  • assets/templates/setup_dev_signing.sh: Create a stable dev code-signing identity.
  • assets/templates/launch.sh: Simple launcher for a packaged .app.
  • assets/templates/version.env: Example version file consumed by packaging scripts.
  • assets/templates/bootstrap/: Minimal SwiftPM macOS app skeleton (Package.swift, Sources/, version.env).

Notes

  • Keep entitlements and signing configuration explicit; edit the template scripts instead of reimplementing.
  • Remove Sparkle steps if you do not use Sparkle for updates.
  • Sparkle relies on the bundle build number (CFBundleVersion), so BUILD_NUMBER in version.env must increase for each update.
  • For menu bar apps, set MENU_BAR_APP=1 when packaging to emit LSUIElement in Info.plist.

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/Swift-Concurrency-Agent-Skill by Paul Hudson. MIT License.

Swift Concurrency Patterns

Review and write Swift concurrency code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems — do not nitpick or invent issues.

Core Instructions

  • Target Swift 6.2 or later with strict concurrency checking.
  • Prefer structured concurrency (task groups) over unstructured (Task {}).
  • Prefer Swift concurrency over GCD for new code. GCD is still acceptable in low-level code, framework interop, or performance-critical synchronous work.
  • Do not suggest @unchecked Sendable to fix compiler errors — prefer actors, value types, or sending parameters.

Review Process

  1. Scan for known-dangerous patterns using references/hotspots.md.
  2. Check for Swift 6.2 concurrency behavior using references/new-features.md.
  3. Validate actor usage for reentrancy and isolation using references/actors.md.
  4. Ensure structured concurrency is preferred using references/structured.md.
  5. Check unstructured task usage using references/unstructured.md.
  6. Verify cancellation handling using references/cancellation.md.
  7. Validate async stream and continuation usage using references/async-streams.md.
  8. Check bridging code between sync and async using references/bridging.md.
  9. Review legacy concurrency migrations using references/interop.md.
  10. Cross-check against common failure modes using references/bug-patterns.md.
  11. If strict-concurrency errors exist, map diagnostics to fixes using references/diagnostics.md.
  12. If reviewing tests, check async test patterns using references/testing.md.

If doing partial work, load only the relevant reference files.

References

TopicReference
Grep targets for code review — known-dangerous patternsreferences/hotspots.md
Swift 6.2: default isolation, @concurrent, Task.immediate, isolated deinitreferences/new-features.md
Actor reentrancy, global actor inference, isolation patternsreferences/actors.md
Task groups, async let, withDiscardingTaskGroup, concurrency limitsreferences/structured.md
Task vs Task.detached, when Task {} is a code smellreferences/unstructured.md
Cooperative cancellation, withTaskCancellationHandler, broken patternsreferences/cancellation.md
AsyncStream.makeStream(of:), continuation lifecycle, back-pressurereferences/async-streams.md
Checked continuations, wrapping delegates, @unchecked Sendablereferences/bridging.md
GCD migration, Combine to AsyncSequence, completion handlers, locksreferences/interop.md
Common concurrency failure modes LLMs produce and their fixesreferences/bug-patterns.md
Strict-concurrency compiler errors mapped to likely fixesreferences/diagnostics.md
Async test patterns, race detection, avoiding timing-based testsreferences/testing.md

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/Swift-Testing-Agent-Skill by Paul Hudson. MIT License.

Swift Testing Patterns

Write and review Swift Testing code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems — do not nitpick or invent issues.

Core Instructions

  • Target Swift 6.2 or later, using modern Swift concurrency.
  • Swift Testing does not support UI tests — XCTest must be used there.
  • Do not rewrite existing XCTest to Swift Testing unless requested.

Review Process

  1. Ensure tests follow core conventions using references/core-rules.md.
  2. Validate structure, assertions, dependency injection, and best practices using references/writing-better-tests.md.
  3. Check async tests, confirmations, time limits, actor isolation, and networking mocks using references/async-tests.md.
  4. Ensure new features like raw identifiers, exit tests, and attachments are used correctly using references/new-features.md.
  5. If migrating from XCTest, follow references/migrating-from-xctest.md.

If doing partial work, load only the relevant reference files.

References

TopicReference
Structs over classes, @Suite, parallel execution, withKnownIssue, tagsreferences/core-rules.md
Test hygiene, structure, DI, #expect vs #require, Issue.record(), verification methodsreferences/writing-better-tests.md
Serialized tests, confirmation(), time limits, actor isolation, mocking networkingreferences/async-tests.md
Raw identifiers, exit tests, attachments, test scoping traits, range-based confirmationsreferences/new-features.md
XCTest-to-Swift Testing conversion, assertion mappings, floating-point tolerancereferences/migrating-from-xctest.md

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/SwiftData-Agent-Skill by Paul Hudson. MIT License.

SwiftData Patterns

Write and review SwiftData code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems — do not nitpick or invent issues.

Core Instructions

  • Target Swift 6.2 or later, using modern Swift concurrency.
  • Prefer SwiftData across the board. Do not suggest Core Data unless the feature cannot be solved with SwiftData.
  • Do not introduce third-party frameworks without asking first.

Review Process

  1. Check for core SwiftData issues using references/core-rules.md.
  2. Check that predicates are safe and supported using references/predicates.md.
  3. If the project uses CloudKit, check for CloudKit-specific constraints using references/cloudkit.md.
  4. If the project targets iOS 18+, check for indexing opportunities using references/indexing.md.
  5. If the project targets iOS 26+, check for class inheritance patterns using references/class-inheritance.md.

If doing partial work, load only the relevant reference files.

References

TopicReference
Autosave, relationships, delete rules, @Query restrictions, #Unique, @Transientreferences/core-rules.md
Supported predicates, dangerous patterns that crash at runtime, unsupported methodsreferences/predicates.md
CloudKit constraints: no #Unique, optional requirements, eventual consistencyreferences/cloudkit.md
Database indexing (iOS 18+), single and compound property indexesreferences/indexing.md
Model subclassing (iOS 26+), @available requirements, predicate filteringreferences/class-inheritance.md

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from AvdLee/SwiftUI-Agent-Skill by Antoine van der Lee and Omar Elsayed. MIT License.

Swift Charts

References

TopicReference
Marks, axes, selection, styling, composition, Chart3Dreferences/charts.md
Accessibility, VoiceOver, Audio Graph, custom descriptorsreferences/charts-accessibility.md

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from Dimillian/Skills by Thomas Ricouard. MIT License.

SwiftUI Performance Audit

Quick start

Use this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.

Workflow

  1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.
  2. If code is available, start with a code-first review using references/code-smells.md.
  3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.
  4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with references/profiling-intake.md.
  5. Summarize likely causes, evidence, remediation, and validation steps using references/report-template.md.

1. Intake

Collect:

  • Target view or feature code.
  • Symptoms and exact reproduction steps.
  • Data flow: @State, @Binding, environment dependencies, and observable models.
  • Whether the issue shows up on device or simulator, and whether it was observed in Debug or Release.

Ask the user to classify the issue if possible:

  • CPU spike or battery drain
  • Janky scrolling or dropped frames
  • High memory or image pressure
  • Hangs or unresponsive interactions
  • Excessive or unexpectedly broad view updates

For the full profiling intake checklist, read references/profiling-intake.md.

2. Code-First Review

Focus on:

  • Invalidation storms from broad observation or environment reads.
  • Unstable identity in lists and ForEach.
  • Heavy derived work in body or view builders.
  • Layout thrash from complex hierarchies, GeometryReader, or preference chains.
  • Large image decode or resize work on the main thread.
  • Animation or transition work applied too broadly.

Use references/code-smells.md for the detailed smell catalog and fix guidance.

Provide:

  • Likely root causes with code references.
  • Suggested fixes and refactors.
  • If needed, a minimal repro or instrumentation suggestion.

3. Guide the User to Profile

If code review does not explain the issue, ask for runtime evidence:

  • A trace export or screenshots of the SwiftUI timeline and Time Profiler call tree.
  • Device/OS/build configuration.
  • The exact interaction being profiled.
  • Before/after metrics if the user is comparing a change.

Use references/profiling-intake.md for the exact checklist and collection steps.

4. Analyze and Diagnose

  • Map the evidence to the most likely category: invalidation, identity churn, layout thrash, main-thread work, image cost, or animation cost.
  • Prioritize problems by impact, not by how easy they are to explain.
  • Distinguish code-level suspicion from trace-backed evidence.
  • Call out when profiling is still insufficient and what additional evidence would reduce uncertainty.

5. Remediate

Apply targeted fixes:

  • Narrow state scope and reduce broad observation fan-out.
  • Stabilize identities for ForEach and lists.
  • Move heavy work out of body into derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use @State only for view-owned state, not as an ad hoc cache for arbitrary computation.
  • Use equatable() only when equality is cheaper than recomputing the subtree and the inputs are truly value-semantic.
  • Downsample images before rendering.
  • Reduce layout complexity or use fixed sizing where possible.

Use references/code-smells.md for examples, Observation-specific fan-out guidance, and remediation patterns.

6. Verify

Ask the user to re-run the same capture and compare with baseline metrics. Summarize the delta (CPU, frame drops, memory peak) if provided.

Outputs

Provide:

  • A short metrics table (before/after if available).
  • Top issues (ordered by impact).
  • Proposed fixes with estimated effort.

Use references/report-template.md when formatting the final audit.

References

  • Profiling intake and collection checklist: references/profiling-intake.md
  • Common code smells and remediation patterns: references/code-smells.md
  • Audit output template: references/report-template.md
  • Add Apple documentation and WWDC resources under references/ as they are supplied by the user.
  • Optimizing SwiftUI performance with Instruments: references/optimizing-swiftui-performance-instruments.md
  • Understanding and improving SwiftUI performance: references/understanding-improving-swiftui-performance.md
  • Understanding hangs in your app: references/understanding-hangs-in-your-app.md
  • Demystify SwiftUI performance (WWDC23): references/demystify-swiftui-performance-wwdc23.md

HealthKit Documentation

Search these docs to answer questions about HealthKit APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details, e.g.:
    • hkhealthstore.md for HKHealthStore API
    • hkunit.md for unit conversions

Files

  • healthkit-index.md - Framework overview and all available APIs
  • hkhealthstore.md - Health data store operations
  • hkquantitysample.md - Quantity samples (weight, heart rate, etc.)
  • hkquantitytypeidentifier.md - All quantity type identifiers
  • hksamplequery.md - Querying health data
  • hkunit.md - Units and conversions

Human Interface Guidelines Reference

Local greppable copy of Apple's Human Interface Guidelines — an on-demand fact lookup, not design direction.

Use it to answer factual questions: what a system component can do, what Apple calls something, accessibility and ergonomic minimums (44pt hit targets, Dynamic Type behavior, contrast), and conventions App Review actually checks.

Visual design in our repos is the designing model's own taste. Consult the HIG for facts, never for aesthetics — it describes what the system provides and requires, not what your screen should look like.

Downloaded Reference Files

All key HIG documentation is available locally (grep-friendly):

Getting Started

FileContentSize
hig-index.mdFull HIG table of contents11KB
designing-for-ios.mdiOS design principles5KB

Foundations

FileContentSize
app-icons.mdApp icon design guidelines14KB
color.mdColor usage and system colors17KB
typography.mdFonts, text styles, Dynamic Type17KB
layout.mdLayout principles, safe areas21KB
materials.mdMaterials, blur effects, vibrancy14KB
motion.mdAnimation principles9KB
accessibility.mdAccessibility best practices19KB
sf-symbols.mdSF Symbols usage21KB

Patterns

FileContentSize
onboarding.mdOnboarding flows6KB
modality.mdModal presentations7KB
launching.mdApp launch experience6KB
feedback.mdUser feedback patterns5KB
playing-haptics.mdHaptic feedback10KB
searching.mdSearch patterns7KB
settings.mdSettings patterns7KB

Components - Navigation

FileContentSize
tab-bars.mdTab bar design11KB
navigation-bars.mdNavigation bar patterns17KB
toolbars.mdToolbar design17KB
sidebars.mdSidebar patterns8KB

Components - Presentation

FileContentSize
sheets.mdSheet presentations11KB
alerts.mdAlert dialogs10KB
action-sheets.mdAction sheets4KB
menus.mdMenu design14KB

Components - Controls

FileContentSize
buttons.mdButton styles and usage17KB
lists-and-tables.mdList and table patterns9KB
toggles.mdToggle/switch design9KB
pickers.mdPicker controls6KB
sliders.mdSlider controls6KB
steppers.mdStepper controls2KB
text-fields.mdText input fields6KB

Searching the Docs

# Find color guidance
grep -i "semantic" color.md

# Find button styles
grep -i "bordered" buttons.md

# Find haptic patterns
grep -i "notification" playing-haptics.md

# Browse the full HIG index
grep -i "navigation" hig-index.md

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant Human Interface Guidelines path with the sosumi.ai Markdown mirror. For example, /design/human-interface-guidelines/buttons maps to https://sosumi.ai/design/human-interface-guidelines/buttons.

Common HIG Doc Paths

TopicURL Path
Full Indexhuman-interface-guidelines
iOS Designhuman-interface-guidelines/designing-for-ios
iPadOS Designhuman-interface-guidelines/designing-for-ipados
macOS Designhuman-interface-guidelines/designing-for-macos
App Iconshuman-interface-guidelines/app-icons
Colorhuman-interface-guidelines/color
Typographyhuman-interface-guidelines/typography
Layouthuman-interface-guidelines/layout
Accessibilityhuman-interface-guidelines/accessibility
SF Symbolshuman-interface-guidelines/sf-symbols
Buttonshuman-interface-guidelines/buttons
Tab Barshuman-interface-guidelines/tab-bars
Navigation Barshuman-interface-guidelines/navigation-bars
Sheetshuman-interface-guidelines/sheets
Alertshuman-interface-guidelines/alerts

Quick Facts

System Button Styles (iOS)

What the system provides out of the box:

  • Plain - Text only, minimal visual weight
  • Gray - Gray background
  • Tinted - Tinted background with accent color
  • Filled - Solid background
  • Bordered - Outlined with border
  • Bordered Prominent - Filled background, high prominence

Haptic Feedback Types

  • Selection - Light tap for selection changes
  • Impact - Light/medium/heavy/rigid/soft for collisions
  • Notification - Success/warning/error for outcomes

Safe Areas (ergonomic facts)

  • Content outside safe areas can be clipped by the notch/Dynamic Island, home indicator, or rounded corners
  • Interactive elements outside safe areas may be unreachable or intercepted by system gestures
  • Backgrounds can extend edge-to-edge without those risks

Sources

Apple Documentation

WWDC Sessions

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

iOS Liquid Glass Reference

API reference for the Liquid Glass design system (iOS 26+): glass effects, containers, morphing transitions, and related system behaviors. This documents what the system provides — design direction is yours.

When to Use

  • Implementing glass materials, glassEffect modifiers, or GlassEffectContainer
  • Navigation surfaces that use system glass (tabs, toolbars, sheets)
  • Checking how glass adapts to accessibility settings
  • Creating app icons with Icon Composer

Apple's Stated Design Principles

Apple describes Liquid Glass with three principles (reference, not a mandate):

PrincipleDescription
HierarchyControls float above content. Glass frames content rather than obscuring it.
HarmonySoftware design aligns with hardware — concentric corners, fluid gestures.
ConsistencyAdapts across iPhone, iPad, Mac — same identity, contextual expression.

One functional constraint worth knowing: glass is designed for the navigation/control layer. Applying it to content surfaces defeats its sampling model (see containers below).

Liquid Glass Core API

Basic Glass Effect

import SwiftUI

// Simple glass application
Text("Action")
    .padding()
    .glassEffect() // .regular variant, .capsule shape

// With explicit parameters
Button("Confirm") { }
    .padding()
    .glassEffect(.regular, in: RoundedRectangle(cornerRadius: 12), isEnabled: true)

Glass Variants

VariantUse Case
.regularToolbars, nav bars, tab bars, standard controls
.clearFloating controls over media (photos, maps, video)
.identityConditional disable: glassEffect(isActive ? .regular : .identity)

Glass Modifiers

// Semantic tinting
.glassEffect(.regular.tint(.accentColor))

// Interactive behaviors (scaling, shimmer, touch illumination)
.glassEffect(.regular.interactive())

// Combined
.glassEffect(.regular.tint(.blue).interactive())

Custom Shapes

// Standard shapes
.glassEffect(.regular, in: .capsule)
.glassEffect(.regular, in: .circle)
.glassEffect(.regular, in: RoundedRectangle(cornerRadius: 16))

// Container-concentric (matches device/container corners)
.glassEffect(.regular, in: .rect(cornerRadius: .containerConcentric))

GlassEffectContainer & Morphing

Container Setup

Glass cannot sample other glass. Use containers for multiple glass elements:

GlassEffectContainer(spacing: 30) {
    HStack(spacing: 20) {
        ForEach(actions) { action in
            Button(action.title, systemImage: action.icon) { }
                .frame(width: 44, height: 44)
                .glassEffect(.regular.interactive())
        }
    }
}

Morphing Transitions

struct ExpandableActions: View {
    @State private var isExpanded = false
    @Namespace private var namespace

    var body: some View {
        GlassEffectContainer(spacing: 30) {
            VStack(spacing: 30) {
                if isExpanded {
                    ActionButton(icon: "rotate.right")
                        .glassEffectID("rotate", in: namespace)
                }

                HStack(spacing: 30) {
                    if isExpanded {
                        ActionButton(icon: "slider.horizontal.3")
                            .glassEffectID("adjust", in: namespace)
                    }

                    Button {
                        withAnimation(.bouncy) { isExpanded.toggle() }
                    } label: {
                        Image(systemName: isExpanded ? "xmark" : "plus")
                            .frame(width: 56, height: 56)
                    }
                    .glassEffect(.regular.tint(.accentColor).interactive())
                    .glassEffectID("toggle", in: namespace)

                    if isExpanded {
                        ActionButton(icon: "crop")
                            .glassEffectID("crop", in: namespace)
                    }
                }

                if isExpanded {
                    ActionButton(icon: "wand.and.stars")
                        .glassEffectID("enhance", in: namespace)
                }
            }
        }
    }
}

Navigation Patterns

Tab Bar (Floating)

TabView {
    Tab("Home", systemImage: "house") {
        HomeView()
    }

    Tab("Search", systemImage: "magnifyingglass") {
        SearchView()
    }

    Tab("Profile", systemImage: "person") {
        ProfileView()
    }
}
// Tab bar now floats, reacts to background, collapses on scroll

Toolbar with Grouping

.toolbar {
    ToolbarItemGroup(placement: .topBarTrailing) {
        Button("Edit", systemImage: "pencil") { }
        Button("Share", systemImage: "square.and.arrow.up") { }
    }

    ToolbarSpacer(.flexible, placement: .topBarTrailing)

    ToolbarItem(placement: .topBarTrailing) {
        Button("Done", systemImage: "checkmark") { }
            .tint(.accentColor)
    }
}

Sheets with Morphing

struct ContentView: View {
    @State private var showSettings = false
    @Namespace private var namespace

    var body: some View {
        NavigationStack {
            ContentView()
                .toolbar {
                    ToolbarItem(placement: .topBarTrailing) {
                        Button("Settings", systemImage: "gear") {
                            showSettings = true
                        }
                        .matchedTransitionSource(id: "settings", in: namespace)
                    }
                }
                .sheet(isPresented: $showSettings) {
                    SettingsView()
                        .navigationTransition(.zoom(sourceID: "settings", in: namespace))
                        .presentationDetents([.medium, .large])
                }
        }
    }
}

SF Symbols Effects

Image(systemName: "checkmark.circle")
    .symbolEffect(.drawOn, value: isComplete)

Image(systemName: "heart.fill")
    .symbolEffect(.bounce, value: isFavorite)

Haptics API

import UIKit

// Impact feedback
let generator = UIImpactFeedbackGenerator(style: .medium)
generator.impactOccurred()

// Selection feedback
let selection = UISelectionFeedbackGenerator()
selection.selectionChanged()

// Success/error
let notification = UINotificationFeedbackGenerator()
notification.notificationOccurred(.success)

Accessibility Behaviors

Automatic Glass Adaptations

Glass automatically adapts to:

  • Reduce Transparency: More frosting
  • Increase Contrast: Stark borders
  • Reduce Motion: Tones down animation

Manual Checks

@Environment(\.accessibilityReduceTransparency) var reduceTransparency
@Environment(\.accessibilityReduceMotion) var reduceMotion

var animation: Animation? {
    reduceMotion ? nil : .bouncy
}

System expectations: minimum 44x44pt touch targets, accessibility labels, Dynamic Type support.

Reference

For official Apple documentation links, WWDC session IDs, and API quick reference tables, see reference.md.

MapKit Reference

MapKit for SwiftUI — maps, annotations, and location features (iOS 26+).

Downloaded Reference Files

FileContent
mapkit-overview.mdFull MapKit framework index
map.mdMap view
marker.mdMarker (pin-style annotations)
annotation.mdCustom annotations
mapcameraposition.mdMapCameraPosition
mapkit-for-swiftui.mdMapKit SwiftUI integration
mapfeature.mdMapFeature

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from mapkit-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/mapkit/mkmapview maps to https://sosumi.ai/documentation/mapkit/mkmapview.

PhotosUI Documentation

Search these docs to answer questions about photo picker APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details

Files

  • photosui-index.md - Framework overview, Live Photo views
  • photospicker.md - SwiftUI PhotosPicker for selecting photos

StoreKit Reference

StoreKit 2 for in-app purchases and subscriptions (iOS 26+).

Downloaded Reference Files

FileContent
storekit-overview.mdFull StoreKit framework index
product.mdProduct struct
transaction.mdTransaction verification & history
subscriptioninfo.mdSubscription info & status
storeview.mdStoreView (product display)
subscriptionstoreview.mdSubscriptionStoreView

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from storekit-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/storekit/product maps to https://sosumi.ai/documentation/storekit/product.

Swift Concurrency Reference

Structured concurrency, actors, and async sequences in Swift.

Downloaded Reference Files

FileContent
concurrency-overview.mdSwift concurrency index
task.mdTask struct
taskgroup.mdTaskGroup for parallel work
actor.mdActor protocol
asyncsequence.mdAsyncSequence protocol
asyncstream.mdAsyncStream
checkedcontinuation.mdCheckedContinuation for bridging

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from concurrency-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/swift/task maps to https://sosumi.ai/documentation/swift/task.

Swift Testing Reference

Apple's modern testing framework (import Testing) for iOS 26+.

Downloaded Reference Files

FileContent
testing-overview.mdFull Testing framework index
defining-tests.mdDefining test functions with @Test
organizing-tests.mdOrganizing tests with @Suite
expectations.md#expect, #require, confirmations
parameterized-testing.mdParameterized test patterns
traits.mdTest traits (tags, conditions, time limits)
migrating-from-xctest.mdMigration guide from XCTest

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from testing-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/testing/test maps to https://sosumi.ai/documentation/testing/test.

SwiftData Documentation

Search these docs to answer questions about SwiftData APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details, e.g.:
    • swiftdata-model.md for @Model macro
    • swiftdata-query.md for @Query usage

Files

  • swiftdata-index.md - Framework overview and all available APIs
  • swiftdata-model.md - @Model macro and model definition
  • swiftdata-modelcontext.md - ModelContext for CRUD operations
  • swiftdata-query.md - @Query property wrapper for fetching data

SwiftUI Reference

This skill provides access to SwiftUI documentation via downloaded reference files.

Downloaded Reference Files

The following Apple documentation pages are available locally (grep-friendly):

FileContent
swiftui-overview.mdFull SwiftUI framework index (907KB)
view-protocol.mdView protocol and all modifiers (59KB)
state.md@State property wrapper
binding.md@Binding property wrapper
environment.md@Environment property wrapper
observation.md@Observable macro (iOS 17+)
navigationstack.mdNavigationStack (iOS 16+)
navigationsplitview.mdNavigationSplitView
tabview.mdTabView
list.mdList view
canvas.mdCanvas — immediate-mode drawing (iOS 15+)
graphicscontext.mdGraphicsContext — drawing API used inside Canvas

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from swiftui-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/swiftui/button maps to https://sosumi.ai/documentation/swiftui/button.

Common SwiftUI Doc Paths

TopicURL Path
Textswiftui/text
Buttonswiftui/button
Imageswiftui/image
VStackswiftui/vstack
HStackswiftui/hstack
ZStackswiftui/zstack
Formswiftui/form
Sheetswiftui/sheet
Alertswiftui/alert
Pickerswiftui/picker
Toggleswiftui/toggle
Sliderswiftui/slider
ProgressViewswiftui/progressview
AsyncImageswiftui/asyncimage
GeometryReaderswiftui/geometryreader
ScrollViewswiftui/scrollview
LazyVStackswiftui/lazyvstack
LazyHStackswiftui/lazyhstack
NavigationLinkswiftui/navigationlink
ToolbarItemswiftui/toolbaritem
Canvasswiftui/canvas
GraphicsContextswiftui/graphicscontext

Usage Instructions

  1. Check downloaded files first - Grep the local .md files for your topic
  2. Use the overview as an index - Search swiftui-overview.md for documentation paths
  3. Fetch only when needed - If no installed skill has the page, use sosumi.ai with documentation paths from the overview

Example workflow:

# Looking for info on modifiers?
grep -i "padding" view-protocol.md

# Need full Text documentation? Check the local file first.
grep -i "font" text.md

Sources

TipKit Reference

TipKit for displaying contextual tips and feature discovery (iOS 26+).

Downloaded Reference Files

FileContent
tipkit-overview.mdFull TipKit framework index
tip.mdTip protocol
tipview.mdTipView (inline tips)
popuptipview.mdTipUIPopoverViewController
tips.mdTips namespace
configure.mdTips.configure() setup

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from tipkit-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/tipkit/tip maps to https://sosumi.ai/documentation/tipkit/tip.

UIKit Reference

UIKit framework documentation for iOS and iPadOS apps.

Downloaded Reference Files

Search the local files first. uikit-overview.md is the full framework index and is large, so prefer rg over opening it directly.

FileContent
uikit-overview.mdFull UIKit framework index
uikit-updates.mdUIKit updates
uiapplication.mdUIApplication
uiapplicationdelegate.mdUIApplicationDelegate
uiwindowscene.mdUIWindowScene
uiview.mdUIView
uiviewcontroller.mdUIViewController
uicontrol.mdUIControl
uibutton.mdUIButton
uilabel.mdUILabel
uiimage.mdUIImage
uiimageview.mdUIImageView
uicolor.mdUIColor
uifont.mdUIFont
uiscrollview.mdUIScrollView
uitableview.mdUITableView
uicollectionview.mdUICollectionView
uistackview.mdUIStackView
nslayoutconstraint.mdNSLayoutConstraint
uinavigationcontroller.mdUINavigationController
uitabbarcontroller.mdUITabBarController
uisplitviewcontroller.mdUISplitViewController
uigesturerecognizer.mdUIGestureRecognizer
uialertcontroller.mdUIAlertController
uiactivityviewcontroller.mdUIActivityViewController
uivisualeffectview.mdUIVisualEffectView
uiblureffect.mdUIBlurEffect
uihostingcontroller.mdUIHostingController bridge from SwiftUI
using-swiftui-with-uikit.mdUsing SwiftUI with UIKit

Fetching More Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from uikit-overview.md with the sosumi.ai Markdown mirror. For example, /documentation/uikit/uiview maps to https://sosumi.ai/documentation/uikit/uiview.

Some UIKit-adjacent APIs live in other frameworks. For example, UIHostingController is documented under SwiftUI.

UserNotifications Documentation

Search these docs to answer questions about notification APIs.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details, e.g.:
    • notifications-overview.md for notification center and triggers

Files

  • notifications-overview.md - Framework overview and notification types
  • unusernotificationcenter.md - Central notification management
  • unnotificationrequest.md - Creating notification requests
  • unmutablenotificationcontent.md - Notification content (title, body, etc.)
  • uncalendarnotificationtrigger.md - Date/time-based triggers
  • untimeintervalnotificationtrigger.md - Interval-based triggers

WidgetKit Documentation

Search these docs to answer questions about widget development.

Return Format

Always include:

  1. Summary - Answer the question concisely
  2. File paths - List relevant files for full details, e.g.:
    • widgetkit-overview.md for widget basics
    • widgetkit-timelineprovider.md for timeline providers

Files

  • widgetkit-overview.md - Framework overview and widget families
  • widgetkit-timelineentry.md - Timeline entry protocol
  • widgetkit-timelineprovider.md - Providing widget timeline data

XCUITest Reference

Comprehensive reference for writing reliable XCUITest UI tests in Swift 6.

Quick Reference

// Basic test structure
@MainActor
final class MyUITests: XCTestCase {
    var app: XCUIApplication!

    override func setUp() {
        super.setUp()
        continueAfterFailure = false
        app = XCUIApplication()
        app.launch()
    }

    func testExample() {
        let button = app.buttons["Submit"]
        XCTAssertTrue(button.waitForExistence(timeout: 5))
        button.tap()
    }
}

Topic Guides

Curated guidance with code examples (grep-friendly):

FileContent
element-queries.mdCore API classes: XCUIApplication, XCUIElement, XCUIElementQuery, XCUICoordinate
interactions.mdTaps, presses, text input, swipes, coordinate-based and other gestures
waiting.mdwaitForExistence, XCTWaiter, non-existence, property waits, Xcode 26 KeyPath waits
swift6-concurrency.mdSwift 6 strict concurrency: @MainActor test classes, async setUp/tearDown, nonisolated
assertions.mdXCTAssert patterns, custom messages, existence checks
screenshots.mdScreenshots, XCTAttachment, screenshot-on-failure, extracting from .xcresult
launch-arguments.mdLaunch arguments/environment, UserDefaults override, localization and accessibility testing
permissions.mdresetAuthorizationStatus, XCUIProtectedResource, interruption monitors, springboard/system alerts
test-helpers.mdPage Object Model, reusable helpers, timeout constants
troubleshooting.mdCommon failures (element not found, flaky tests) and what's new in Xcode 26 / iOS 26
patterns.mdAdvanced patterns: base test class, system dialogs, scroll/wait, debugging, test organization

Downloaded Reference Files

Apple documentation pages available locally:

FileContent
xctest-index.mdFull XCTest framework index
xcuiautomation-index.mdFull XCUIAutomation framework index
xcuiapplication.mdXCUIApplication class
xcuielement.mdXCUIElement class
xcuielementquery.mdXCUIElementQuery class
xcuicoordinate.mdXCUICoordinate class
xcuiprotectedresource.mdXCUIProtectedResource enum
xcuiscreenshot.mdXCUIScreenshot class

Sources

Apple Documentation

WWDC Sessions

Community Resources

Fetching More Apple Docs

  1. Search this skill's local .md files first.
  2. If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or SKILL.md frontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet.
  3. If no installed skill has the page, use the relevant documentation path from the local XCTest or XCUIAutomation indexes with the sosumi.ai Markdown mirror. For example, /documentation/xcuiautomation/xcuielement maps to https://sosumi.ai/documentation/xcuiautomation/xcuielement.

Sponsors

Details

Marketplace
Prisma-Labs-Dev/apple-skills
Category
Development