derklinke/codex-config

Overview

This skill provides direct access to Apple-bundled Xcode documentation for framework APIs, Swift compiler diagnostics, and official guides like Liquid Glass and Foundation Models. It routes questions to the precise Apple doc or diagnostic entry you need and complements opinionated iOS Skill Pack advice with authoritative API details. Use it when you want canonical explanations, exact signatures, or Apple-written migration and diagnostic guidance.

How this skill works

When a question involves an Apple framework API, a Swift compiler error/warning, or an Xcode-bundled guide, this skill selects the matching Apple documentation skill and returns the authoritative content. It follows a decision tree: map the user intent to a guide (UI, concurrency, data, etc.) or a specific diagnostic skill, then surface the official explanation, examples, and recommended fixes. Use it alongside iOS Skill Pack suggestions for practical patterns and trade-offs.

When to use it

• You need the exact Apple API signature, availability, or behavior.
• A Swift compiler diagnostic needs a canonical explanation and example fixes.
• You’re implementing Apple-defined features like Liquid Glass, SwiftData, or Foundation Models.
• You want Apple’s official migration notes or deprecation guidance.
• You need Xcode-bundled how-to content for UIKit/SwiftUI/AppKit/WidgetKit integration.

Best practices

• Ask which specific API, class, or diagnostic you’re seeing to route to the exact doc.
• Provide the compiler error text or code snippet when requesting diagnostic guidance.
• Combine Apple docs (authoritative details) with iOS Skill Pack guidance for design patterns and trade-offs.
• Prefer the skill’s diagnostic entries for Swift concurrency and type-system errors to avoid misdiagnosis.
• Use the skill names (e.g., apple-diag-*, apple-guide-*) when requesting a direct doc read for speed.

Example use cases

• Explain a Swift compiler error like "actor-isolated call from nonisolated context" with examples and fixes.
• Show official API signatures and availability for a Foundation or UIKit type before implementation.
• Read Apple’s Liquid Glass guidance for SwiftUI and supply code patterns that match the spec.
• Get the on-device Foundation Models guide when adding on-device LLM capabilities to an app.
• Retrieve StoreKit or App Intents updates for implementing purchases or voice shortcuts.