home / skills / charleswiltgen / axiom / axiom-apple-docs

This skill helps you fetch authoritative Apple API details and Swift diagnostics from bundled docs to ensure correct usage and diagnostics.

npx playbooks add skill charleswiltgen/axiom --skill axiom-apple-docs

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.9 KB
---
name: axiom-apple-docs
description: Use when ANY question involves Apple framework APIs, Swift compiler errors, or Xcode-bundled documentation. Covers Liquid Glass, Swift 6.2 concurrency, Foundation Models, SwiftData, StoreKit, 32 Swift compiler diagnostics.
license: MIT
---

# Apple Documentation Router

Apple bundles for-LLM markdown documentation inside Xcode. These are authoritative, up-to-date guides and diagnostics written by Apple engineers. Use them alongside Axiom skills for the most accurate information.

## When to Use

Use Apple's bundled docs when:
- You need the exact API signature or behavior from Apple
- Axiom skills reference an Apple framework and you want the official source
- A Swift compiler diagnostic needs explanation
- The user asks about a specific Apple framework feature

**Priority**: Axiom skills provide opinionated guidance (decision trees, anti-patterns, pressure scenarios). Apple docs provide authoritative API details. Use both together.

## Guide Topics (AdditionalDocumentation)

Read these with the MCP `axiom_read_skill` tool using the skill name.

### UI & Design

| Topic | Skill Name |
|-------|-----------|
| Liquid Glass in SwiftUI | `apple-guide-swiftui-implementing-liquid-glass-design` |
| Liquid Glass in UIKit | `apple-guide-uikit-implementing-liquid-glass-design` |
| Liquid Glass in AppKit | `apple-guide-appkit-implementing-liquid-glass-design` |
| Liquid Glass in WidgetKit | `apple-guide-widgetkit-implementing-liquid-glass-design` |
| SwiftUI toolbar features | `apple-guide-swiftui-new-toolbar-features` |
| SwiftUI styled text editing | `apple-guide-swiftui-styled-text-editing` |
| SwiftUI WebKit integration | `apple-guide-swiftui-webkit-integration` |
| SwiftUI AlarmKit integration | `apple-guide-swiftui-alarmkit-integration` |
| Swift Charts 3D visualization | `apple-guide-swift-charts-3d-visualization` |
| Foundation AttributedString | `apple-guide-foundation-attributedstring-updates` |

### Data & Persistence

| Topic | Skill Name |
|-------|-----------|
| SwiftData class inheritance | `apple-guide-swiftdata-class-inheritance` |

### Concurrency & Performance

| Topic | Skill Name |
|-------|-----------|
| Swift concurrency updates | `apple-guide-swift-concurrency-updates` |
| InlineArray and Span | `apple-guide-swift-inlinearray-span` |

### Apple Intelligence

| Topic | Skill Name |
|-------|-----------|
| Foundation Models (on-device LLM) | `apple-guide-foundationmodels-using-on-device-llm-in-your-app` |

### System Integration

| Topic | Skill Name |
|-------|-----------|
| App Intents updates | `apple-guide-appintents-updates` |
| StoreKit updates | `apple-guide-storekit-updates` |
| MapKit GeoToolbox | `apple-guide-mapkit-geotoolbox-placedescriptors` |
| Widgets for visionOS | `apple-guide-widgets-for-visionos` |

### Accessibility

| Topic | Skill Name |
|-------|-----------|
| Assistive Access in iOS | `apple-guide-implementing-assistive-access-in-ios` |

### Computer Vision

| Topic | Skill Name |
|-------|-----------|
| Visual Intelligence in iOS | `apple-guide-implementing-visual-intelligence-in-ios` |

## Swift Compiler Diagnostics

These explain specific Swift compiler errors and warnings with examples and fixes.

### Concurrency Diagnostics

| Diagnostic | Skill Name |
|-----------|-----------|
| Actor-isolated call from nonisolated context | `apple-diag-actor-isolated-call` |
| Conformance isolation | `apple-diag-conformance-isolation` |
| Isolated conformances | `apple-diag-isolated-conformances` |
| Nonisolated nonsending by default | `apple-diag-nonisolated-nonsending-by-default` |
| Sendable closure captures | `apple-diag-sendable-closure-captures` |
| Sendable metatypes | `apple-diag-sendable-metatypes` |
| Sending closure risks data race | `apple-diag-sending-closure-risks-data-race` |
| Sending risks data race | `apple-diag-sending-risks-data-race` |
| Mutable global variable | `apple-diag-mutable-global-variable` |
| Preconcurrency import | `apple-diag-preconcurrency-import` |

### Type System Diagnostics

| Diagnostic | Skill Name |
|-----------|-----------|
| Existential any | `apple-diag-existential-any` |
| Existential member access limitations | `apple-diag-existential-member-access-limitations` |
| Nominal types | `apple-diag-nominal-types` |
| Multiple inheritance | `apple-diag-multiple-inheritance` |
| Protocol type non-conformance | `apple-diag-protocol-type-non-conformance` |
| Opaque type inference | `apple-diag-opaque-type-inference` |

### Build & Migration Diagnostics

| Diagnostic | Skill Name |
|-----------|-----------|
| Deprecated declaration | `apple-diag-deprecated-declaration` |
| Error in future Swift version | `apple-diag-error-in-future-swift-version` |
| Strict language features | `apple-diag-strict-language-features` |
| Strict memory safety | `apple-diag-strict-memory-safety` |
| Implementation only deprecated | `apple-diag-implementation-only-deprecated` |
| Member import visibility | `apple-diag-member-import-visibility` |
| Missing module on known paths | `apple-diag-missing-module-on-known-paths` |
| Clang declaration import | `apple-diag-clang-declaration-import` |
| Availability unrecognized name | `apple-diag-availability-unrecognized-name` |
| Unknown warning group | `apple-diag-unknown-warning-group` |

### Swift Language Diagnostics

| Diagnostic | Skill Name |
|-----------|-----------|
| Dynamic callable requirements | `apple-diag-dynamic-callable-requirements` |
| Property wrapper requirements | `apple-diag-property-wrapper-requirements` |
| Result builder methods | `apple-diag-result-builder-methods` |
| String interpolation conformance | `apple-diag-string-interpolation-conformance` |
| Trailing closure matching | `apple-diag-trailing-closure-matching` |
| Temporary pointers | `apple-diag-temporary-pointers` |

## Routing Decision Tree

```
User question about Apple API/framework?
├── Specific compiler error/warning → Read matching apple-diag-* skill
├── Liquid Glass implementation → Read apple-guide-*-liquid-glass-design (SwiftUI/UIKit/AppKit)
├── Swift concurrency patterns → Read apple-guide-swift-concurrency-updates
├── Foundation Models / on-device AI → Read apple-guide-foundationmodels-*
├── SwiftData features → Read apple-guide-swiftdata-*
├── StoreKit / IAP → Read apple-guide-storekit-updates
├── App Intents / Siri → Read apple-guide-appintents-updates
├── Charts / visualization → Read apple-guide-swift-charts-3d-visualization
├── Text editing / AttributedString → Read apple-guide-swiftui-styled-text-editing or apple-guide-foundation-attributedstring-updates
├── WebKit in SwiftUI → Read apple-guide-swiftui-webkit-integration
├── Toolbar features → Read apple-guide-swiftui-new-toolbar-features
└── Other → Search with axiom_search_skills using source filter "apple"
```

## Resources

**Skills**: axiom-ios-ui, axiom-ios-concurrency, axiom-ios-data, axiom-ios-ai, axiom-ios-integration

Overview

This skill provides authoritative routing to Apple-bundled Xcode documentation and diagnostics for questions about Apple frameworks, Swift compiler errors, and Xcode docs. It pairs opinionated Axiom guidance with Apple's official references so you get practical recommendations plus exact API and diagnostic details. Use it whenever you need the precise behavior, signatures, or official examples from Apple.

How this skill works

When a query involves an Apple API, a Swift compiler diagnostic, or Xcode-bundled guidance, the skill maps the topic to the correct Apple guide or diagnostic document. It recommends reading the matching Apple guide (e.g., Liquid Glass, Swift concurrency, Foundation Models) or the specific compiler diagnostic skill for exact error explanations and fixes. Use the recommended Apple doc together with Axiom opinionated guidance for complete answers.

When to use it

  • You need the exact API signature, availability, or behavior from Apple.
  • A Swift compiler error or warning requires the official diagnostic explanation and example fixes.
  • You want Apple-authored implementation examples for features like Liquid Glass, SwiftData, or Foundation Models.
  • A question targets Xcode-bundled documentation or a recent Apple framework update.
  • You need to cross-check Axiom guidance with Apple’s authoritative docs before shipping.

Best practices

  • Prefer Apple-bundled docs for exact API signatures, availability annotations, and official examples.
  • Use Axiom guidance for decision-making, patterns, and anti-patterns; consult Apple docs for definitive behavior.
  • When diagnosing compiler messages, open the matching Apple diagnostic doc for concrete examples and suggested fixes.
  • Combine the Apple guide and Axiom advice: follow official constraints, then apply opinionated patterns to your design.
  • Search by diagnostic name or feature (e.g., 'actor-isolated call' or 'Liquid Glass') to route to the correct guide quickly.

Example use cases

  • Fixing a Swift compiler error about actor isolation: route to the actor-isolated call diagnostic and follow Apple’s examples.
  • Implementing Liquid Glass visuals in SwiftUI: read the Apple guide for recommended APIs and examples.
  • Integrating on-device Foundation Models: consult the FoundationModels guide for requirements and sample usage.
  • Resolving a SwiftData inheritance question: open the SwiftData class inheritance guide for constraints and examples.
  • Handling StoreKit or App Intents updates: read the respective Apple update guides to ensure correct implementation.

FAQ

How do I pick between Axiom guidance and Apple docs?

Use Apple docs for authoritative API details and compiler diagnostics; use Axiom guidance for higher-level decisions, patterns, and trade-offs.

What if my question matches multiple Apple guides?

Start with the most specific guide (e.g., a diagnostic or feature guide). Then consult related guides for integration or broader context.