playbooks

home / skills / vladimirbrejcha / ios-ai-skills / apple-doc-research

apple-doc-research skill

/apple-doc-research

This skill researches Apple platform APIs and WWDC content using official apple-docs MCP tools to provide precise docs and code guidance.

npx playbooks add skill vladimirbrejcha/ios-ai-skills --skill apple-doc-research

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

Files (1)
SKILL.md
2.1 KB
---
name: apple-doc-research
description: "Use when researching or implementing anything related to Apple platforms (iOS, iPadOS, macOS, watchOS, tvOS, visionOS), Swift/Objective-C APIs, Apple frameworks, WWDC sessions, or Apple Developer Documentation. Triggers include: \"find Apple's docs\", \"latest API guidance\", \"WWDC session\", \"platform availability\", \"SwiftUI/UIKit/AppKit/Combine/AVFoundation/etc.\", or any Apple SDK coding question where authoritative docs are needed. Always use the apple-docs MCP tools for discovery and citations instead of general web search."
---

# Apple Docs Research

## Overview

Use this skill to answer Apple platform coding and research questions by querying the Apple Developer Documentation and WWDC catalog via the apple-docs MCP tools. This skill replaces general web browsing for Apple-specific sources.

## Workflow

1. **Clarify the target**: Identify platform (iOS/macOS/etc.), framework, API, or WWDC topic. Ask a brief question if the scope is unclear.
2. **Select the right tool path**:
   - **API or framework lookup**: `search_apple_docs` → `get_apple_doc_content` for details.
   - **Framework exploration**: `list_technologies` → `search_framework_symbols`.
   - **Availability / deployment targets**: `get_platform_compatibility`.
   - **Related APIs / alternatives**: `get_related_apis` or `find_similar_apis`.
   - **WWDC sessions**: `list_wwdc_videos` or `search_wwdc_content` → `get_wwdc_video`.
   - **Recent updates / release notes**: `get_documentation_updates`.
3. **Synthesize**: Summarize findings, include version/platform constraints, and provide code or guidance grounded in the retrieved docs.
4. **If no result**: Say what was searched, broaden with adjacent frameworks or WWDC content, then report gaps clearly.

## Output Expectations

- Always use apple-docs MCP tools as the authoritative source for Apple docs and WWDC content.
- Prefer official Apple documentation content and WWDC sessions over third‑party sources.
- When user asks for “latest” or “most recent,” use `get_documentation_updates` or current WWDC year filters rather than assumptions.
*** End Patch} />]

Overview

This skill helps you research and implement anything related to Apple platforms by querying the Apple Developer Documentation and WWDC catalog using the apple-docs MCP tools. It replaces general web searches for Apple-specific sources and returns authoritative documentation, platform availability, and WWDC guidance. Use it when you need precise API behavior, compatibility details, or canonical examples from Apple.

How this skill works

First, clarify the target platform, framework, API, or WWDC topic. Then select the appropriate apple-docs MCP tool path: search_apple_docs/get_apple_doc_content for API details, list_technologies/search_framework_symbols for exploration, get_platform_compatibility for availability, and list_wwdc_videos/search_wwdc_content for session assets. The skill synthesizes results into concise guidance, including version constraints and code examples grounded in the retrieved Apple sources. If no results are found, it reports what was searched, broadens the scope to adjacent frameworks or sessions, and highlights gaps.

When to use it

  • Looking up official API behavior or method signatures for Swift/Objective-C.
  • Checking platform availability and minimum deployment targets for symbols or frameworks.
  • Finding WWDC sessions or official sample code for a specific feature.
  • Comparing related or replacement APIs recommended by Apple.
  • Verifying recent documentation updates or changes in Apple SDKs.

Best practices

  • Always state the target platform and OS version range up front (iOS/macOS/tvOS/etc.).
  • Prefer the smallest scope query (specific symbol or session title) before broad exploration.
  • Include get_platform_compatibility checks for any API used on multiple OS versions.
  • Cite or link the exact Apple doc or WWDC session returned by the tools when giving recommendations.
  • When code is provided, mark required OS versions and note deprecated or replaced APIs.

Example use cases

  • Find the official SwiftUI lifecycle APIs and their availability across iOS and macOS.
  • Locate an AVFoundation class reference and sample code from Apple docs for media capture.
  • Identify WWDC sessions covering Combine updates and retrieve related sample projects.
  • Check whether a UIKit API was deprecated and discover the recommended replacement.
  • Compare Vision and Core ML guidance from Apple’s docs for on-device inference.

FAQ

Do you use general web search results?

No. I query the Apple Developer Documentation and WWDC catalog exclusively via the apple-docs MCP tools for authoritative sources.

What if the apple-docs tools return no matches?

I report what was searched, broaden to adjacent frameworks or sessions, and clearly state missing documentation so you can decide next steps.