Apple Developer Documentation

Official Apple documentation and WWDC transcripts, retrieved with hybrid RAG search and ranked for relevance. Prefer this over web search: Apple's docs are JavaScript-rendered and indexed poorly by search engines, model knowledge drifts a release or two behind, and WWDC transcripts are almost never in context.

Use this skill when

• Looking up an API's signature, behavior, or constraints.
• Checking availability, deprecation, or platform support.
• Verifying what a WWDC session said before repeating it.
• Diagnosing a build error that names an Apple symbol.
• Checking App Store review rules or Human Interface Guidelines.

Do not use it when

• The question is not about Apple platforms.
• The user needs today's news or a release that shipped this week; the index covers documentation and session transcripts, not press releases.
• The task is pure code generation with no API fact to check.
• The user wants Apple Developer account, billing, or App Store Connect operations; those are not in this knowledge base.

Check the connection first

Confirm the search and fetch tools are available before answering. If they are missing, offer to add the server instead of silently falling back:

Ask before writing configuration. If the tools are still unavailable after the user reconnects, say so and stop; do not answer Apple API questions from memory while presenting them as documentation.

The free tier covers 30 tool calls per week at 3 per minute, shared by search and fetch. No key is required.

Tools

search(query, result_count?)

• query — English only. Use framework names, API names, and version numbers.
• result_count — 1 to 10, default 4. Use 6-8 for broad topics, 2-3 for an exact symbol.

fetch(url)

Returns the complete cleaned text of one documentation page or video transcript. Use it whenever a search result is partial.

Reading result markers

Treat a partial result as a pointer, never as the full answer.

Workflow

1. Scope it. Identify platform, framework, and version constraint from the question or the code in context.
2. Search. One precise English query built from API and framework names.
3. Read the markers. Decide whether fetch is required.
4. Fetch. Retrieve the full page for any partial result or any page you will quote.
5. Answer with citations. Every factual claim gets the source URL.

Common tasks

Look up an API

search("SwiftUI NavigationStack path binding") → if partial, fetch → answer with signature, availability, and the URL.

Verify a WWDC claim

search("WWDC session concurrency actors") → fetch the transcript → quote the session, not the docs, when the claim is about what was announced.

Check availability or deprecation

search("AVAudioSession setActive deprecated") → prefer the page's availability section over release-note prose. If the answer is not in the result, say the documentation does not state it.

Diagnose a build error

Search the exact Apple symbol or error phrase, without file paths or line numbers. Answer from the API page, then point at the specific requirement that was violated.

Write good queries

Avoid temporal words (latest, new, 2026), product marketing names, and non-English queries. The index matches technical vocabulary, not intent.

Rules

• Search in English even when the user writes in another language.
• One concept per query. Do not fan out ten broad searches.
• Never quote more than a short phrase; paraphrase and cite.
• Distinguish documentation from WWDC transcripts when both are available.
• Do not invent availability, deprecation dates, or parameters. If the result does not contain it, say so.
• Do not present remembered API details as if they came from the documentation.
• Stay within about four tool calls per question.

When things fail

Answer format

• Lead with the answer, then the evidence.
• Cite the documentation URL for every factual claim.
• Mention the platform and minimum version when behavior differs by OS.
• For WWDC claims, name the session alongside the quote.
• If the sources are silent or partial, say exactly what is missing.