← ClaudeAtlas

apple-docslisted

Research authoritative, version-aware Apple platform documentation for Swift, SwiftUI, UIKit, AppKit, Foundation, macOS, iOS, Xcode, Apple SDKs, Swift Evolution, compiler behavior, HIG, WWDC, signing, entitlements, capabilities, sandboxing, notarization, privacy manifests, distribution, and platform release changes. Use when implementation correctness depends on Apple API behavior, lifecycle, availability, deprecation, SDK or Xcode version, deployment target, platform conventions, or official guidance. In existing projects, detect Xcode, Swift, SDK, platform, dependencies, and deployment targets first. Prefer official Apple and Swift sources and clearly label forum discussions and community notes as secondary. Do not use for purely algorithmic Swift questions or non-Apple documentation.
martonpaulo/skills · ★ 1 · AI & Automation · score 71
Install: claude install-skill martonpaulo/skills
# Apple Docs Answer Apple development documentation questions with version and project context. Use this skill for authoritative lookups, not ordinary implementation, broad architecture, general product research, or purely algorithmic Swift work. ## Workflow 1. In an existing project, run `detect_apple_project_context()` first. Record resolved and unresolved Xcode, Swift, SDK, platform, deployment-target, dependency, entitlement, sandbox, capability, and signing context. 2. Define the exact documented behavior to verify. Include the relevant version, platform, and deployment target. 3. Use the highest-authority applicable source: 1. official Apple documentation and release notes; 2. official Apple or Swift source repositories; 3. accepted Swift Evolution proposals; 4. official WWDC pages and transcripts; 5. Apple Developer Forums or Swift Forums, labeled secondary; 6. community WWDC notes or summaries, labeled community. 4. Prefer documentation compatible with the detected context. State availability, deprecation, minimum version, fallback needs, and unresolved context explicitly. 5. Return a concise answer with source links or identifiers. Separate public API contracts from source implementation details, forum guidance, local Xcode additional documentation, and community notes. Do not present a Swift Evolution pitch, forum statement, community note, or undocumented implementation detail as guaranteed public API behavior. ## Runner This skill requires