agentleFS
Sign inStart free
cpodercpoder/claude-apple-plugin/skills/docs/SKILL.md

docs

Skill0 starsChanged 30 days agoMITView on GitHub

Look up Apple developer documentation (frameworks, APIs, REST endpoints, Swift/Objective-C symbols, articles) and render it as Markdown. Use for questions about SwiftUI, UIKit, Foundation, App Store Connect API endpoints, WeatherKit, MusicKit, CloudKit, Xcode, visionOS... or when the user runs /apple-services:docs <query>.

168 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, perf and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • vbrevikSkill

    work

    Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

    Also in 7 projects that use this

  • mbwsimsSkill

    impact

    This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 131 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    If the query already looks like a documentation path or URL (swiftui/view, https://developer.apple.com/documentation/...), call apple_docs …

    line 13
  2. Very specific:

    Call apple_docs_index with the technology and the remaining words as query to get page paths, then apple_docs on the best match (section: …

    line 20

“Common” is measured: kept by at least 6 in 10 of the 131 edited versions of this file we could read. “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-services:docs — Apple developer documentation

Query: $ARGUMENTS

Strategy (all public, no credentials):

  1. If the query already looks like a documentation path or URL (swiftui/view, https://developer.apple.com/documentation/...), call apple_docs directly.
  2. Otherwise identify the technology: if unsure of the slug, call apple_technologies with a keyword (e.g. weather, music, notification). Common slugs: swiftui, uikit, foundation, swift, combine, coredata, swiftdata, cloudkit, storekit, appstoreconnectapi, appstoreserverapi, applemusicapi, weatherkitrestapi, applemapsserverapi, usernotifications, xcode, visionos, realitykit, arkit.
  3. Call apple_docs_index with the technology and the remaining words as query to get page paths, then apple_docs on the best match (section: overview for API shape only, topics to browse members).
  4. Answer with the declaration, availability, key discussion points and a link (https://developer.apple.com/documentation/<path>). Quote code from the page when useful.

Tips: paths are lowercase; symbols nest under their type (swiftui/view/padding(_:)); REST endpoints appear as GET /v1/... titles in appstoreconnectapi.

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.

Check your setup, free