Apple docs
My personal Agent Skills for coding agents: engineering workflows plus a few personal-use tools. Personalized forks, with every upstream author credited.
npx -y skills add martonpaulo/skills --skill apple-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.4 KB, as published. Nobody here has run it
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
- 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. - Define the exact documented behavior to verify. Include the relevant version, platform, and deployment target.
- Use the highest-authority applicable source:
- official Apple documentation and release notes;
- official Apple or Swift source repositories;
- accepted Swift Evolution proposals;
- official WWDC pages and transcripts;
- Apple Developer Forums or Swift Forums, labeled secondary;
- community WWDC notes or summaries, labeled community.
- Prefer documentation compatible with the detected context. State availability, deprecation, minimum version, fallback needs, and unresolved context explicitly.
- 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 local shell execution and Python 3.10 or newer. allowed-tools is optional compatibility metadata; agents that do not interpret it should invoke the runner with their normal shell tool:
python3 scripts/run.py "result = detect_apple_project_context()" --project-path /path/to/project --pretty
Submitted code cannot import modules, read arbitrary files, launch subprocesses, or access the network directly. It can call only the registered documentation APIs. It must assign a JSON-serializable final value to result.
Use small queries and filter before returning data. Read sandbox.md and security.md when changing or diagnosing the runner.
APIs and references
- Project context and local Xcode documentation: project-context.md
- Apple API documentation: apple-docs.md
- Swift Evolution and forums: swift-evolution.md
- Apple and Swift source: swift-repos.md
- Compiler internals: compiler.md
- HIG: hig.md
- WWDC: wwdc.md
- Legacy Documentation Archive: archive.md
- Xcode releases: xcode-releases.md
- Distribution, signing, and privacy: distribution.md
- Authority and cache behavior: source-authority.md, cache.md
Safety and completion
Context detection is read-only: do not build, sign, archive, update dependencies, execute project scripts, or modify the project. Local Xcode APIs search only expected installed-Xcode documentation folders and never accept arbitrary paths from sandbox code.
The lookup is complete when the answer identifies the applicable documentation and version, reports compatibility and uncertainty, labels source authority, and returns only the evidence needed for the task.