playbooks

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

apple-docs-research skill

/apple-docs-research

This skill helps you research Apple platform APIs and WWDC content using authoritative Apple docs and the apple-docs MCP tools.

npx playbooks add skill vladimirbrejcha/ios-ai-skills --skill apple-docs-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-docs-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 features across Apple platforms by querying the Apple Developer Documentation and WWDC catalog using the apple-docs MCP tools. It is designed for accurate, citation-backed answers about APIs, frameworks, availability, and WWDC guidance. Use it instead of a general web search when you need authoritative Apple sources and version-aware recommendations.

How this skill works

I first clarify the target platform, framework, API, or WWDC topic. Then I pick the appropriate apple-docs MCP tool path: search_apple_docs and get_apple_doc_content for API lookups, list_technologies and search_framework_symbols for exploration, list_wwdc_videos or search_wwdc_content for session material, and get_platform_compatibility or get_documentation_updates for availability and recent changes. I synthesize the retrieved docs and sessions into concise guidance, include platform/version constraints, and provide example code or migration steps grounded in Apple’s official references.

When to use it

  • You need authoritative details about a Swift/Objective-C API or framework (SwiftUI, UIKit, AppKit, Combine, AVFoundation, etc.).
  • You want WWDC sessions or official sample code relevant to a platform feature or migration.
  • You must verify platform availability or deployment target constraints for an API.
  • You want the most recent Apple documentation updates or release notes for an API.
  • You’re choosing between similar Apple APIs and need documented guidance or related-API references.

Best practices

  • Always specify platform(s) and minimum deployment targets up front to get precise compatibility info.
  • Start with search_apple_docs for symbols and use get_apple_doc_content to extract authoritative text and sample code.
  • When asking for “latest” behavior, request get_documentation_updates or filter WWDC by year to avoid assumptions.
  • Include relevant WWDC session IDs or keywords when you need in-depth demos or design rationale.
  • If a direct doc isn’t found, broaden to adjacent frameworks and list searched terms and gaps clearly.

Example use cases

  • Find the official declaration, discussion, and sample for a SwiftUI view modifier and its availability per OS version.
  • Compare AVFoundation APIs for recording versus using newer MediaCapture APIs and cite Apple guidance.
  • Locate WWDC sessions showing Combine integrations with SwiftUI and pull authoritative clips or transcripts.
  • Check platform compatibility for an AppKit API when preparing a macOS-first feature and provide migration notes.
  • Get the latest documentation updates for SceneKit or RealityKit before adopting a new 3D approach.

FAQ

Do you use general web search results?

No. I use the apple-docs MCP tools to query Apple Developer Documentation and WWDC material as the primary, authoritative sources.

What if the docs don’t mention a specific example I need?

I report what was searched, broaden to related APIs or WWDC talks, and provide recommended patterns grounded in official guidance while noting gaps.