agentleFS
itsnex1sitsnex1s/awesome-claude-skills/skills/apple-docs/SKILL.md

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

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
  1. Distinctive:

    When the user needs to find an API, framework, or concept:

    line 23
  2. Distinctive:

    When the user provides a documentation path or URL:

    line 29
  3. Distinctive:

    When the user asks about a WWDC session:

    line 35
  4. Very specific:

    If $ARGUMENTS starts with /documentation or /videos or https://developer.apple.com → use fetch

    line 42
  5. Very specific:

    If $ARGUMENTS is a search query (e.g.

    line 43
  6. Distinctive:

    If no arguments provided → ask the user what they want to look up

    line 44
  7. Distinctive:

    Run the appropriate sosumi command

    line 48
  8. Distinctive:

    Read the output (markdown-formatted Apple documentation)

    line 49
  9. Distinctive:

    If the search returned multiple results, pick the most relevant and offer to fetch the full docs

    line 51
  10. Distinctive:

    When fetching API docs, highlight: signature, availability, key parameters, and usage notes

    line 52
  11. Distinctive:

    Search returns up to 50+ results — pick the most relevant

    line 102

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/null

Fetch specific documentation page

When the user provides a documentation path or URL:

npx @nshipster/sosumi fetch "$ARGUMENTS" 2>/dev/null

Fetch WWDC session transcript

When the user asks about a WWDC session:

npx @nshipster/sosumi fetch "/videos/play/wwdc{year}/{session-id}" 2>/dev/null

How to decide which command to use

  1. If $ARGUMENTS starts with /documentation or /videos or https://developer.apple.com → use fetch
  2. If $ARGUMENTS is a search query (e.g. "SwiftData", "HealthKit sleep") → use search
  3. If no arguments provided → ask the user what they want to look up

Workflow

  1. Run the appropriate sosumi command
  2. Read the output (markdown-formatted Apple documentation)
  3. Present the relevant information to the user in a concise summary
  4. If the search returned multiple results, pick the most relevant and offer to fetch the full docs
  5. 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/appintents

Example 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.