apple-docs
Skill5 starsChanged 10 months agoMITView on GitHub
Look up Apple Developer Documentation (Swift, SwiftUI, HealthKit, UIKit, etc.) and WWDC session transcripts using the sosumi CLI tool. Use when working with Swift/iOS code and need to check API signatures, find documentation, or understand Apple frameworks.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- g-cqd/skillstheir own version, first seen Oct 23, 2026
- mishafyi/Apple-Docs-2.0-MCPtheir own version, first seen Oct 20, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- mishafyi/Apple-Docs-2.0-MCP★ 25same name
- g-cqd/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- agent-browserSkill
- changelog-generatorSkill
- code-reviewSkill
- database-cliSkill
- docker-cliSkill
- github-actionsSkill
- git-workflowSkill
- lighthouse-auditSkill
- testingSkill
- vercel-cliSkill
- xcode-mcp-app-testingSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
When the user needs to find an API, framework, or concept:
- Distinctive: line 29
When the user provides a documentation path or URL:
- Distinctive: line 35
When the user asks about a WWDC session:
- Very specific: line 42
If $ARGUMENTS starts with /documentation or /videos or https://developer.apple.com → use fetch
- Very specific: line 43
If $ARGUMENTS is a search query (e.g.
- Distinctive: line 44
If no arguments provided → ask the user what they want to look up
- Distinctive: line 48
Run the appropriate sosumi command
- Distinctive: line 49
Read the output (markdown-formatted Apple documentation)
- Distinctive: line 51
If the search returned multiple results, pick the most relevant and offer to fetch the full docs
- Distinctive: line 52
When fetching API docs, highlight: signature, availability, key parameters, and usage notes
- Distinctive: line 102
Search returns up to 50+ results — pick the most relevant
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Apple Documentation Lookup
Fetch Apple Developer Documentation and WWDC session transcripts as clean markdown using the sosumi CLI tool.
Installation
npm install -g @nshipster/sosumi
# or use directly with npx (no install needed)Commands
Search documentation
When the user needs to find an API, framework, or concept:
npx @nshipster/sosumi search "$ARGUMENTS" 2>/dev/nullFetch specific documentation page
When the user provides a documentation path or URL:
npx @nshipster/sosumi fetch "$ARGUMENTS" 2>/dev/nullFetch WWDC session transcript
When the user asks about a WWDC session:
npx @nshipster/sosumi fetch "/videos/play/wwdc{year}/{session-id}" 2>/dev/nullHow to decide which command to use
- If
$ARGUMENTSstarts with/documentationor/videosorhttps://developer.apple.com→ usefetch - If
$ARGUMENTSis a search query (e.g. "SwiftData", "HealthKit sleep") → usesearch - If no arguments provided → ask the user what they want to look up
Workflow
- Run the appropriate sosumi command
- Read the output (markdown-formatted Apple documentation)
- Present the relevant information to the user in a concise summary
- If the search returned multiple results, pick the most relevant and offer to fetch the full docs
- When fetching API docs, highlight: signature, availability, key parameters, and usage notes
Common documentation paths
/documentation/swiftui
/documentation/swiftdata
/documentation/observation
/documentation/charts
/documentation/healthkit
/documentation/widgetkit
/documentation/backgroundtasks
/documentation/foundation
/documentation/uikit
/documentation/combine
/documentation/concurrency
/documentation/corelocation
/documentation/mapkit
/documentation/avfoundation
/documentation/coreml
/documentation/createml
/documentation/vision
/documentation/naturallanguage
/documentation/appintentsExample usage
User: /apple-docs HKCategoryValueSleepAnalysis
→ Run: npx @nshipster/sosumi search "HKCategoryValueSleepAnalysis"
→ Then fetch the top result if needed
User: /apple-docs /documentation/swiftui/view
→ Run: npx @nshipster/sosumi fetch "/documentation/swiftui/view"
User: /apple-docs SwiftData model macro
→ Run: npx @nshipster/sosumi search "SwiftData model macro"
User: /apple-docs WWDC23 SwiftData
→ Run: npx @nshipster/sosumi search "WWDC 2023 SwiftData"
→ Then fetch the session path from the results
Requirements
- Node.js 18+
- Internet connection (fetches from developer.apple.com)
Notes
- Output is clean markdown, ideal for reading in terminal
- Search returns up to 50+ results — pick the most relevant
- Documentation paths are case-insensitive
- WWDC transcripts include full session text with timestamps
- Works with all Apple frameworks: SwiftUI, UIKit, HealthKit, CoreML, etc.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

