
apple-skills
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-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add Prisma-Labs-Dev/apple-skills.
Contents
Discovered from sourceSkills 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
| Field | Limit | Ranking Weight | Indexed |
|---|---|---|---|
| Title | 30 chars | Highest | Yes |
| Subtitle | 30 chars | 2nd highest | Yes |
| Keywords | 100 chars | 3rd (same as subtitle) | Yes |
| Description | 4,000 chars | None | No |
| Promo Text | 170 chars | None | No |
| Release Notes | 4,000 chars | None | No |
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
- Never duplicate words from title/subtitle - Apple indexes them automatically
- Use single words when possible - Apple creates combinations automatically
- No plurals if you have the singular form
- No special characters -
@,#,-are replaced with spaces - No generic terms - avoid "app", "game", "free", "best", "new"
- No competitor names or trademarks
- 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
| Language | Code | Language | Code | |
|---|---|---|---|---|
| English (US) | en-US | German | de-DE | |
| English (UK) | en-GB | French (France) | fr-FR | |
| English (AU) | en-AU | French (Canada) | fr-CA | |
| Spanish (Spain) | es-ES | Portuguese (Brazil) | pt-BR | |
| Spanish (Mexico) | es-MX | Portuguese (Portugal) | pt-PT | |
| Italian | it | Dutch | nl-NL | |
| Japanese | ja | Russian | ru | |
| Korean | ko | Chinese Simplified | zh-Hans | |
| Arabic | ar-SA | Chinese Traditional | zh-Hant |
Localization Rules
- Don't just translate - Research native search terms
- Include English keywords in non-English locales (users often search in English)
- Remove diacritics for keywords (users skip accents when typing)
- Add regional terms - Different countries use different words
- 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
- Remove all duplicates from title/subtitle
- Remove plurals if singular exists
- Add action verbs users search for
- Add regional/cultural variants
- Fill remaining space with related terms
- 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
- Duplicating keywords across fields - Wastes precious character space
- Direct translation - Doesn't account for local search behavior
- Keyword stuffing in title - Hurts readability and conversion
- Ignoring subtitle - Second most important ranking factor
- Using spaces after commas - Wastes ~10% of keyword space
- Frequent changes - Wait 3-4 weeks between keyword updates
- Including app/game - Already indexed from category
Resources
- Apple Developer: App Store Search
- EAS Metadata Schema
- Project guidelines:
docs/aso-guidelines.md
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
| Framework | File | Size | Topics |
|---|---|---|---|
| SwiftUI | ../swiftui/swiftui-overview.md | 907KB | Views, modifiers, navigation, state |
| XCTest | xctest-index.md | 55KB | Testing, assertions, expectations |
| XCUIAutomation | xcuiautomation-index.md | 58KB | UI testing, elements, queries |
| UIKit | ../uikit/uikit-overview.md | 1.8MB | Views, controllers, controls, scenes |
| Core Animation | ../core-animation/core-animation-index.md | 80KB | CALayer, CAAnimation, CATransaction, layer subclasses |
| HealthKit | healthkit-index.md | 312KB | Health data, workouts, records |
| Combine | combine-index.md | 153KB | Publishers, subscribers, operators |
| SwiftData | swiftdata-index.md | 86KB | Models, containers, queries |
| Observation | observation-index.md | 3KB | @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
- Check whether the detailed page is already available in one of your installed Apple skills.
- Use skill names, descriptions, or
SKILL.mdfrontmatter to find likely skill directories, then grep their local.mdfiles before fetching. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the same path with the
sosumi.aiMarkdown 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:
- Summary - Answer the question concisely
- File paths - List relevant files for full details
Files
backgroundtasks-index.md- Framework overview, task typesbgtaskscheduler.md- Task scheduling and registration
Combine Documentation
Search these docs to answer questions about Combine APIs.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details, e.g.:
combine-index.mdfor 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:
- Summary — answer the question concisely.
- File paths — list relevant files for full details, e.g.:
calayer.mdfor layer geometry, contents, hierarchycabasicanimation.mdfor animating a single property between two valuescatransaction.mdfor batching, disabling implicit animations, or changing default duration
Files
| File | Content |
|---|---|
core-animation-index.md | Full QuartzCore framework index — layer basics, animation classes, transactions, layer subclasses |
calayer.md | CALayer — the root layer class: geometry, contents, hierarchy, layout, animations |
caanimation.md | CAAnimation — abstract base class for all Core Animation animation types |
capropertyanimation.md | CAPropertyAnimation — abstract subclass animating a single layer property |
cabasicanimation.md | CABasicAnimation — interpolate a layer property between two values |
cakeyframeanimation.md | CAKeyframeAnimation — animate a property through a sequence of keyframes |
caspringanimation.md | CASpringAnimation — spring-based interpolation with mass, stiffness, damping |
caanimationgroup.md | CAAnimationGroup — run multiple animations together with a shared duration |
catransition.md | CATransition — fade, push, reveal, and move-in transitions between layer states |
camediatiming.md | CAMediaTiming — protocol shared by layers and animations (beginTime, duration, repeat, speed) |
catransaction.md | CATransaction — batch property changes, disable implicit animations, set default duration/timing |
catransform3d.md | CATransform3D — 4×4 matrix used by CALayer.transform for 3D transforms |
cashapelayer.md | CAShapeLayer — vector-shape layer driven by a CGPath (stroke, fill, line dash) |
cagradientlayer.md | CAGradientLayer — axial, radial, and conic gradient layers |
caemitterlayer.md | CAEmitterLayer — particle emitter layer (fire, smoke, confetti, sparkles) |
caemittercell.md | CAEmitterCell — individual particle definition used by CAEmitterLayer |
careplicatorlayer.md | CAReplicatorLayer — replicate a sublayer with offsets and transforms |
cametallayer.md | CAMetalLayer — layer backed by a Metal drawable for GPU-rendered content |
catextlayer.md | CATextLayer — layer that renders plain or attributed text |
catiledlayer.md | CATiledLayer — tile-based asynchronous content rendering for large or zoomable layers |
cadisplaylink.md | CADisplayLink — 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
CADisplayLinkper-frame callback (custom drawing loops, scrubbing, physics). - You're rendering thousands of particles with
CAEmitterLayeror replicating sublayers withCAReplicatorLayer.
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
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills, then grep their local files.
- If no installed skill has the page, the QuartzCore path on Apple's site is
/documentation/quartzcore/<symbol>— fetch via thesosumi.aiMarkdown mirror (e.g.https://sosumi.ai/documentation/quartzcore/camediatimingfunction) or by runningpnpm fetch-docagainst the apple-skills tooling.
Core Haptics Documentation
Search these docs to answer questions about haptic feedback APIs.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details
Files
corehaptics-index.md- Framework overview, patterns, eventschhapticengine.md- Haptic engine setup and playback
EventKit Documentation
Search these docs to answer questions about calendar and reminder APIs.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details
Files
eventkit-index.md- Framework overview, events, remindersekeventstore.md- Event store access and permissionsekreminder.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
-
Bootstrap the project folder
- Copy
assets/templates/bootstrap/into a new repo. - Rename
MyAppinPackage.swift,Sources/MyApp/, andversion.env. - Customize
APP_NAME,BUNDLE_ID, and versions.
- Copy
-
Build, package, and run the bootstrapped app
- Copy scripts from
assets/templates/into your repo (for example,Scripts/). - Build/tests:
swift buildandswift test. - Package:
Scripts/package_app.sh. - Run:
Scripts/compile_and_run.sh(preferred) orScripts/launch.sh. - Release (optional):
Scripts/sign-and-notarize.shandScripts/make_appcast.sh. - Tag + GitHub release (optional): create a git tag, upload the zip/appcast to the GitHub release, and publish.
- Copy scripts from
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
| Symptom | Likely Cause | Recovery |
|---|---|---|
The software asset has already been uploaded | Duplicate submission for same version | Bump BUILD_NUMBER in version.env and repackage. |
Package Invalid: Invalid Code Signing Entitlements | Entitlements in .entitlements file don't match provisioning | Audit entitlements against Apple's allowed set; remove unsupported keys. |
The executable does not have the hardened runtime enabled | Missing --options runtime flag in codesign invocation | Edit sign-and-notarize.sh to add --options runtime to all codesign calls. |
| Notarization hangs / no status email | xcrun notarytool network or credential issue | Run xcrun notarytool history to check status; re-export App Store Connect API key if expired. |
stapler validate fails after successful notarization | Ticket not yet propagated | Wait ~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), soBUILD_NUMBERinversion.envmust increase for each update. - For menu bar apps, set
MENU_BAR_APP=1when packaging to emitLSUIElementin 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 Sendableto fix compiler errors — prefer actors, value types, orsendingparameters.
Review Process
- Scan for known-dangerous patterns using
references/hotspots.md. - Check for Swift 6.2 concurrency behavior using
references/new-features.md. - Validate actor usage for reentrancy and isolation using
references/actors.md. - Ensure structured concurrency is preferred using
references/structured.md. - Check unstructured task usage using
references/unstructured.md. - Verify cancellation handling using
references/cancellation.md. - Validate async stream and continuation usage using
references/async-streams.md. - Check bridging code between sync and async using
references/bridging.md. - Review legacy concurrency migrations using
references/interop.md. - Cross-check against common failure modes using
references/bug-patterns.md. - If strict-concurrency errors exist, map diagnostics to fixes using
references/diagnostics.md. - If reviewing tests, check async test patterns using
references/testing.md.
If doing partial work, load only the relevant reference files.
References
| Topic | Reference |
|---|---|
| Grep targets for code review — known-dangerous patterns | references/hotspots.md |
Swift 6.2: default isolation, @concurrent, Task.immediate, isolated deinit | references/new-features.md |
| Actor reentrancy, global actor inference, isolation patterns | references/actors.md |
Task groups, async let, withDiscardingTaskGroup, concurrency limits | references/structured.md |
Task vs Task.detached, when Task {} is a code smell | references/unstructured.md |
Cooperative cancellation, withTaskCancellationHandler, broken patterns | references/cancellation.md |
AsyncStream.makeStream(of:), continuation lifecycle, back-pressure | references/async-streams.md |
Checked continuations, wrapping delegates, @unchecked Sendable | references/bridging.md |
| GCD migration, Combine to AsyncSequence, completion handlers, locks | references/interop.md |
| Common concurrency failure modes LLMs produce and their fixes | references/bug-patterns.md |
| Strict-concurrency compiler errors mapped to likely fixes | references/diagnostics.md |
| Async test patterns, race detection, avoiding timing-based tests | references/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
- Ensure tests follow core conventions using
references/core-rules.md. - Validate structure, assertions, dependency injection, and best practices using
references/writing-better-tests.md. - Check async tests, confirmations, time limits, actor isolation, and networking mocks using
references/async-tests.md. - Ensure new features like raw identifiers, exit tests, and attachments are used correctly using
references/new-features.md. - If migrating from XCTest, follow
references/migrating-from-xctest.md.
If doing partial work, load only the relevant reference files.
References
| Topic | Reference |
|---|---|
Structs over classes, @Suite, parallel execution, withKnownIssue, tags | references/core-rules.md |
Test hygiene, structure, DI, #expect vs #require, Issue.record(), verification methods | references/writing-better-tests.md |
Serialized tests, confirmation(), time limits, actor isolation, mocking networking | references/async-tests.md |
| Raw identifiers, exit tests, attachments, test scoping traits, range-based confirmations | references/new-features.md |
| XCTest-to-Swift Testing conversion, assertion mappings, floating-point tolerance | references/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
- Check for core SwiftData issues using
references/core-rules.md. - Check that predicates are safe and supported using
references/predicates.md. - If the project uses CloudKit, check for CloudKit-specific constraints using
references/cloudkit.md. - If the project targets iOS 18+, check for indexing opportunities using
references/indexing.md. - 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
| Topic | Reference |
|---|---|
Autosave, relationships, delete rules, @Query restrictions, #Unique, @Transient | references/core-rules.md |
| Supported predicates, dangerous patterns that crash at runtime, unsupported methods | references/predicates.md |
CloudKit constraints: no #Unique, optional requirements, eventual consistency | references/cloudkit.md |
| Database indexing (iOS 18+), single and compound property indexes | references/indexing.md |
Model subclassing (iOS 26+), @available requirements, predicate filtering | references/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
| Topic | Reference |
|---|---|
| Marks, axes, selection, styling, composition, Chart3D | references/charts.md |
| Accessibility, VoiceOver, Audio Graph, custom descriptors | references/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
- Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.
- If code is available, start with a code-first review using
references/code-smells.md. - If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.
- If code review is inconclusive or runtime evidence is required, guide the user through profiling with
references/profiling-intake.md. - 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
bodyor 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
ForEachand lists. - Move heavy work out of
bodyinto derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use@Stateonly 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:
- Summary - Answer the question concisely
- File paths - List relevant files for full details, e.g.:
hkhealthstore.mdfor HKHealthStore APIhkunit.mdfor unit conversions
Files
healthkit-index.md- Framework overview and all available APIshkhealthstore.md- Health data store operationshkquantitysample.md- Quantity samples (weight, heart rate, etc.)hkquantitytypeidentifier.md- All quantity type identifiershksamplequery.md- Querying health datahkunit.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
| File | Content | Size |
|---|---|---|
| hig-index.md | Full HIG table of contents | 11KB |
| designing-for-ios.md | iOS design principles | 5KB |
Foundations
| File | Content | Size |
|---|---|---|
| app-icons.md | App icon design guidelines | 14KB |
| color.md | Color usage and system colors | 17KB |
| typography.md | Fonts, text styles, Dynamic Type | 17KB |
| layout.md | Layout principles, safe areas | 21KB |
| materials.md | Materials, blur effects, vibrancy | 14KB |
| motion.md | Animation principles | 9KB |
| accessibility.md | Accessibility best practices | 19KB |
| sf-symbols.md | SF Symbols usage | 21KB |
Patterns
| File | Content | Size |
|---|---|---|
| onboarding.md | Onboarding flows | 6KB |
| modality.md | Modal presentations | 7KB |
| launching.md | App launch experience | 6KB |
| feedback.md | User feedback patterns | 5KB |
| playing-haptics.md | Haptic feedback | 10KB |
| searching.md | Search patterns | 7KB |
| settings.md | Settings patterns | 7KB |
Components - Navigation
| File | Content | Size |
|---|---|---|
| tab-bars.md | Tab bar design | 11KB |
| navigation-bars.md | Navigation bar patterns | 17KB |
| toolbars.md | Toolbar design | 17KB |
| sidebars.md | Sidebar patterns | 8KB |
Components - Presentation
| File | Content | Size |
|---|---|---|
| sheets.md | Sheet presentations | 11KB |
| alerts.md | Alert dialogs | 10KB |
| action-sheets.md | Action sheets | 4KB |
| menus.md | Menu design | 14KB |
Components - Controls
| File | Content | Size |
|---|---|---|
| buttons.md | Button styles and usage | 17KB |
| lists-and-tables.md | List and table patterns | 9KB |
| toggles.md | Toggle/switch design | 9KB |
| pickers.md | Picker controls | 6KB |
| sliders.md | Slider controls | 6KB |
| steppers.md | Stepper controls | 2KB |
| text-fields.md | Text input fields | 6KB |
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
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant Human Interface Guidelines path with the
sosumi.aiMarkdown mirror. For example,/design/human-interface-guidelines/buttonsmaps tohttps://sosumi.ai/design/human-interface-guidelines/buttons.
Common HIG Doc Paths
| Topic | URL Path |
|---|---|
| Full Index | human-interface-guidelines |
| iOS Design | human-interface-guidelines/designing-for-ios |
| iPadOS Design | human-interface-guidelines/designing-for-ipados |
| macOS Design | human-interface-guidelines/designing-for-macos |
| App Icons | human-interface-guidelines/app-icons |
| Color | human-interface-guidelines/color |
| Typography | human-interface-guidelines/typography |
| Layout | human-interface-guidelines/layout |
| Accessibility | human-interface-guidelines/accessibility |
| SF Symbols | human-interface-guidelines/sf-symbols |
| Buttons | human-interface-guidelines/buttons |
| Tab Bars | human-interface-guidelines/tab-bars |
| Navigation Bars | human-interface-guidelines/navigation-bars |
| Sheets | human-interface-guidelines/sheets |
| Alerts | human-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
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
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,
glassEffectmodifiers, orGlassEffectContainer - 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):
| Principle | Description |
|---|---|
| Hierarchy | Controls float above content. Glass frames content rather than obscuring it. |
| Harmony | Software design aligns with hardware — concentric corners, fluid gestures. |
| Consistency | Adapts 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
| Variant | Use Case |
|---|---|
.regular | Toolbars, nav bars, tab bars, standard controls |
.clear | Floating controls over media (photos, maps, video) |
.identity | Conditional 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
| File | Content |
|---|---|
| mapkit-overview.md | Full MapKit framework index |
| map.md | Map view |
| marker.md | Marker (pin-style annotations) |
| annotation.md | Custom annotations |
| mapcameraposition.md | MapCameraPosition |
| mapkit-for-swiftui.md | MapKit SwiftUI integration |
| mapfeature.md | MapFeature |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
mapkit-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/mapkit/mkmapviewmaps tohttps://sosumi.ai/documentation/mapkit/mkmapview.
PhotosUI Documentation
Search these docs to answer questions about photo picker APIs.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details
Files
photosui-index.md- Framework overview, Live Photo viewsphotospicker.md- SwiftUI PhotosPicker for selecting photos
StoreKit Reference
StoreKit 2 for in-app purchases and subscriptions (iOS 26+).
Downloaded Reference Files
| File | Content |
|---|---|
| storekit-overview.md | Full StoreKit framework index |
| product.md | Product struct |
| transaction.md | Transaction verification & history |
| subscriptioninfo.md | Subscription info & status |
| storeview.md | StoreView (product display) |
| subscriptionstoreview.md | SubscriptionStoreView |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
storekit-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/storekit/productmaps tohttps://sosumi.ai/documentation/storekit/product.
Swift Concurrency Reference
Structured concurrency, actors, and async sequences in Swift.
Downloaded Reference Files
| File | Content |
|---|---|
| concurrency-overview.md | Swift concurrency index |
| task.md | Task struct |
| taskgroup.md | TaskGroup for parallel work |
| actor.md | Actor protocol |
| asyncsequence.md | AsyncSequence protocol |
| asyncstream.md | AsyncStream |
| checkedcontinuation.md | CheckedContinuation for bridging |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
concurrency-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/swift/taskmaps tohttps://sosumi.ai/documentation/swift/task.
Swift Testing Reference
Apple's modern testing framework (import Testing) for iOS 26+.
Downloaded Reference Files
| File | Content |
|---|---|
| testing-overview.md | Full Testing framework index |
| defining-tests.md | Defining test functions with @Test |
| organizing-tests.md | Organizing tests with @Suite |
| expectations.md | #expect, #require, confirmations |
| parameterized-testing.md | Parameterized test patterns |
| traits.md | Test traits (tags, conditions, time limits) |
| migrating-from-xctest.md | Migration guide from XCTest |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
testing-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/testing/testmaps tohttps://sosumi.ai/documentation/testing/test.
SwiftData Documentation
Search these docs to answer questions about SwiftData APIs.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details, e.g.:
swiftdata-model.mdfor @Model macroswiftdata-query.mdfor @Query usage
Files
swiftdata-index.md- Framework overview and all available APIsswiftdata-model.md- @Model macro and model definitionswiftdata-modelcontext.md- ModelContext for CRUD operationsswiftdata-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):
| File | Content |
|---|---|
| swiftui-overview.md | Full SwiftUI framework index (907KB) |
| view-protocol.md | View 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.md | NavigationStack (iOS 16+) |
| navigationsplitview.md | NavigationSplitView |
| tabview.md | TabView |
| list.md | List view |
| canvas.md | Canvas — immediate-mode drawing (iOS 15+) |
| graphicscontext.md | GraphicsContext — drawing API used inside Canvas |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
swiftui-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/swiftui/buttonmaps tohttps://sosumi.ai/documentation/swiftui/button.
Common SwiftUI Doc Paths
| Topic | URL Path |
|---|---|
| Text | swiftui/text |
| Button | swiftui/button |
| Image | swiftui/image |
| VStack | swiftui/vstack |
| HStack | swiftui/hstack |
| ZStack | swiftui/zstack |
| Form | swiftui/form |
| Sheet | swiftui/sheet |
| Alert | swiftui/alert |
| Picker | swiftui/picker |
| Toggle | swiftui/toggle |
| Slider | swiftui/slider |
| ProgressView | swiftui/progressview |
| AsyncImage | swiftui/asyncimage |
| GeometryReader | swiftui/geometryreader |
| ScrollView | swiftui/scrollview |
| LazyVStack | swiftui/lazyvstack |
| LazyHStack | swiftui/lazyhstack |
| NavigationLink | swiftui/navigationlink |
| ToolbarItem | swiftui/toolbaritem |
| Canvas | swiftui/canvas |
| GraphicsContext | swiftui/graphicscontext |
Usage Instructions
- Check downloaded files first - Grep the local
.mdfiles for your topic - Use the overview as an index - Search
swiftui-overview.mdfor documentation paths - Fetch only when needed - If no installed skill has the page, use
sosumi.aiwith 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
| File | Content |
|---|---|
| tipkit-overview.md | Full TipKit framework index |
| tip.md | Tip protocol |
| tipview.md | TipView (inline tips) |
| popuptipview.md | TipUIPopoverViewController |
| tips.md | Tips namespace |
| configure.md | Tips.configure() setup |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
tipkit-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/tipkit/tipmaps tohttps://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.
| File | Content |
|---|---|
| uikit-overview.md | Full UIKit framework index |
| uikit-updates.md | UIKit updates |
| uiapplication.md | UIApplication |
| uiapplicationdelegate.md | UIApplicationDelegate |
| uiwindowscene.md | UIWindowScene |
| uiview.md | UIView |
| uiviewcontroller.md | UIViewController |
| uicontrol.md | UIControl |
| uibutton.md | UIButton |
| uilabel.md | UILabel |
| uiimage.md | UIImage |
| uiimageview.md | UIImageView |
| uicolor.md | UIColor |
| uifont.md | UIFont |
| uiscrollview.md | UIScrollView |
| uitableview.md | UITableView |
| uicollectionview.md | UICollectionView |
| uistackview.md | UIStackView |
| nslayoutconstraint.md | NSLayoutConstraint |
| uinavigationcontroller.md | UINavigationController |
| uitabbarcontroller.md | UITabBarController |
| uisplitviewcontroller.md | UISplitViewController |
| uigesturerecognizer.md | UIGestureRecognizer |
| uialertcontroller.md | UIAlertController |
| uiactivityviewcontroller.md | UIActivityViewController |
| uivisualeffectview.md | UIVisualEffectView |
| uiblureffect.md | UIBlurEffect |
| uihostingcontroller.md | UIHostingController bridge from SwiftUI |
| using-swiftui-with-uikit.md | Using SwiftUI with UIKit |
Fetching More Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from
uikit-overview.mdwith thesosumi.aiMarkdown mirror. For example,/documentation/uikit/uiviewmaps tohttps://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:
- Summary - Answer the question concisely
- File paths - List relevant files for full details, e.g.:
notifications-overview.mdfor notification center and triggers
Files
notifications-overview.md- Framework overview and notification typesunusernotificationcenter.md- Central notification managementunnotificationrequest.md- Creating notification requestsunmutablenotificationcontent.md- Notification content (title, body, etc.)uncalendarnotificationtrigger.md- Date/time-based triggersuntimeintervalnotificationtrigger.md- Interval-based triggers
WidgetKit Documentation
Search these docs to answer questions about widget development.
Return Format
Always include:
- Summary - Answer the question concisely
- File paths - List relevant files for full details, e.g.:
widgetkit-overview.mdfor widget basicswidgetkit-timelineprovider.mdfor timeline providers
Files
widgetkit-overview.md- Framework overview and widget familieswidgetkit-timelineentry.md- Timeline entry protocolwidgetkit-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):
| File | Content |
|---|---|
| element-queries.md | Core API classes: XCUIApplication, XCUIElement, XCUIElementQuery, XCUICoordinate |
| interactions.md | Taps, presses, text input, swipes, coordinate-based and other gestures |
| waiting.md | waitForExistence, XCTWaiter, non-existence, property waits, Xcode 26 KeyPath waits |
| swift6-concurrency.md | Swift 6 strict concurrency: @MainActor test classes, async setUp/tearDown, nonisolated |
| assertions.md | XCTAssert patterns, custom messages, existence checks |
| screenshots.md | Screenshots, XCTAttachment, screenshot-on-failure, extracting from .xcresult |
| launch-arguments.md | Launch arguments/environment, UserDefaults override, localization and accessibility testing |
| permissions.md | resetAuthorizationStatus, XCUIProtectedResource, interruption monitors, springboard/system alerts |
| test-helpers.md | Page Object Model, reusable helpers, timeout constants |
| troubleshooting.md | Common failures (element not found, flaky tests) and what's new in Xcode 26 / iOS 26 |
| patterns.md | Advanced patterns: base test class, system dialogs, scroll/wait, debugging, test organization |
Downloaded Reference Files
Apple documentation pages available locally:
| File | Content |
|---|---|
| xctest-index.md | Full XCTest framework index |
| xcuiautomation-index.md | Full XCUIAutomation framework index |
| xcuiapplication.md | XCUIApplication class |
| xcuielement.md | XCUIElement class |
| xcuielementquery.md | XCUIElementQuery class |
| xcuicoordinate.md | XCUICoordinate class |
| xcuiprotectedresource.md | XCUIProtectedResource enum |
| xcuiscreenshot.md | XCUIScreenshot class |
Sources
Apple Documentation
- XCTest | Apple Developer Documentation
- XCUIAutomation | Apple Developer Documentation
- XCUIElementQuery | Apple Developer Documentation
- waitForExistence | Apple Developer Documentation
- wait(for:toEqual:timeout:) | Apple Developer Documentation
- resetAuthorizationStatus(for:) | Apple Developer Documentation
- XCUIProtectedResource | Apple Developer Documentation
- XCUIScreenshot | Apple Developer Documentation
WWDC Sessions
Community Resources
- XCTest Meets @MainActor | Quality Coding
- Issues with setUp() and tearDown() in XCTest for Swift 6 | Swift Forums
- Waiting in XCTest | Masilotti.com
- UI Testing Cheat Sheet | Masilotti.com
- XCUIElement Actions and Gestures | Apps Developer Blog
- Configuring UI tests with launch arguments | polpiella.dev
- UI Testing improvements in Xcode 16 | Jesse Squires
Fetching More Apple Docs
- Search this skill's local
.mdfiles first. - If the topic is not here, check the other installed Apple skills you have available by their names, descriptions, or
SKILL.mdfrontmatter, then grep their local files. This is faster and uses less context than fetching new docs from the internet. - If no installed skill has the page, use the relevant documentation path from the local XCTest or XCUIAutomation indexes with the
sosumi.aiMarkdown mirror. For example,/documentation/xcuiautomation/xcuielementmaps tohttps://sosumi.ai/documentation/xcuiautomation/xcuielement.
Sponsors
Details
- Marketplace
- Prisma-Labs-Dev/apple-skills
- Category
- Development