mcpField
X
xcdocs

xcdocs

github.com/bitrigappDevelopment18239 installsUpdated 2w ago
Repository

About xcdocs

xcdocs is a local Apple-framework reference for developers implementing code against Apple APIs. It searches documentation entries and retrieves their full contents to help verify symbols, usage, and availability.

Key features

  1. 01Search symbols, articles, and topics
  2. 02Filter by framework and kind
  3. 03Retrieve full documentation entries
  4. 04JSON output

Use cases

  1. 01Verify API names behind compile failures
  2. 02Explore newly released framework features
  3. 03Identify the type of a documentation entry
  4. 04Find related types and concepts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bitrigapp/xcdocs --skill xcdocs

After installing, type/xcdocsin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/cli.md

Details

From the project README

XCDocs

Use xcdocs as a local Apple-framework reference while changing code.

Use It During Implementation

  • Ensure xcdocs is available before relying on the skill.
  • Reach for it when an Apple API is unfamiliar, newly released, renamed, or failing to compile.
  • Start with search --json --omit-content to find the likely symbol, article, or topic.
  • Add repeatable --framework and --kind {article|symbol|topic} filters when the query is broad.
  • Treat documents[].uri from search results as the canonical identifier for get.
  • Use get --json to inspect the full entry before editing code that depends on it.
  • Apply what you find to the code: fix symbol names, choose the right overload, adjust availability guards, or switch to the documented API.

Common Uses

  • Fix compile failures against Apple frameworks by verifying the actual symbol name and entry point.
  • Explore a newly released framework or feature area before wiring it into code.
  • Check whether an API is a symbol, a broader topic page, or an article with setup guidance.
  • Find adjacent types or concepts after locating one relevant documentation entry.

Reference

Comments

Markdown supported