Apple TextApple Text

Focused Apple text docs

Apple Text helps route Apple text questions to the right skill or guide.

It covers TextKit, UIKit and AppKit text views, attributed text, layout invalidation, editor behavior, and Writing Tools.

39 skills1 command5 agents

Status: Apple Text is still in an early phase. Some routes, docs, or packaging paths may still be incomplete or wrong. If you hit a bug or something looks off, please open an issue. Feedback is welcome too.

Start Here

Choose the shortest path that matches the client you are using. Apple Text is one collection, surfaced through plugin commands, MCP, and Xcode MCP.

Ask A Question Start with `/apple-text:ask` for broad Apple text intake.

Use In Xcode Configure Apple Text inside Xcode Claude Agent or Codex via MCP.

Browse Skills Browse the catalog when you already know the API family.

Review Editor Code Use the audit path when you want findings from real code.

Install Add the marketplace in Claude Code, install Apple Text, and verify it in Manage and install.

Use With MCP Connect Apple Text to generic MCP clients and start from `apple_text_route`.

Examples See example prompts, routing, and answer shapes.

Guide Read the routing model for an overview of the entry points.

For findings-first review work, start with apple-text-audit or the Agents page.

Front Doors

These are the main entry points.

apple-text Use when the user clearly has an Apple text-system problem but the right specialist skill is not obvious yet, or when the request mixes TextKit, text views, storage, layout, parsing, and Writing Tools. Reach for this router when you need the next best Apple-text skill, not when the subsystem is already clear.

apple-text-audit Use when the user wants a review-style scan of Apple text code for risks such as TextKit fallback, editing lifecycle bugs, deprecated APIs, performance traps, or Writing Tools breakage. Reach for this when the job is findings from real code, not a symptom-first debug answer or direct API lookup.

apple-text-recipes Use when the user has a "how do I..." question about text views and you need a quick working recipe, or when they want a copy-paste snippet for a common text task rather than architecture guidance. Covers the 25 most common text tasks - background colors per paragraph, line numbers, character limits, text wrapping around images, clickable links, syntax highlighting, placeholder text, auto-growing text views, and more.

apple-text-texteditor-26 Use when building rich-text editing with SwiftUI TextEditor and AttributedString on iOS 26+, or deciding whether the new native APIs are enough versus a UITextView wrapper. Reach for this when the question is specifically about the iOS 26 TextEditor rich-text boundary, not generic SwiftUI wrapping.

apple-text-textkit-diag Use when the user starts with a broken Apple text symptom such as stale layout, fallback, crashes in editing, rendering artifacts, missing Writing Tools, or large-document slowness. Reach for this when debugging misbehavior, not when reviewing code systematically or looking up APIs.

apple-text-views Use when the main task is choosing the right Apple text view or deciding whether a problem belongs in SwiftUI text, UIKit/AppKit text views, or TextKit mode. Reach for this when comparing capabilities and tradeoffs, not when implementing a specific wrapper or low-level API.

apple-text-apple-docs Use when you need direct access to Apple-authored text-system documentation from the Xcode-bundled for-LLM markdown docs that MCP can expose at runtime, especially for AttributedString updates, styled TextEditor behavior, toolbars near editors, or official Swift diagnostic writeups. Reach for this when Apple’s wording matters more than repo-authored guidance.

Install Fast

Pick the surface first, then use the matching front door:

• Claude Code plugin -> install from the marketplace, then start with /apple-text:ask
• Generic MCP client -> connect Apple Text MCP, then start with apple_text_route
• Xcode Claude Agent or Codex -> connect the MCP server inside Xcode, then use the same route-first MCP flow

Claude Code plugin install is the default path:

/plugin marketplace add sitapix/apple-text

Use /plugin to open the plugin menu, search for apple-text, and install it.

Use /plugin, then open Manage and install, to verify that Apple Text is installed.

Clone the repo only when you want to load Apple Text through a local checkout:

git clone https://github.com/sitapix/apple-text
cd apple-text

Use this path when your client can discover skills from a cloned repo or workspace.

If that client exposes commands, start with /apple-text:ask for broad Apple text questions.

If it only loads direct skills, open the matching Apple Text skill or copy one focused skill into your local skills folder.

Marketplace install is also supported:

/plugin marketplace add sitapix/apple-text
/plugin install apple-text@apple-text-marketplace

If you only want a subset in another workspace, copy a focused skill instead of the whole collection:

mkdir -p /path/to/your/project/.agents/skills
cp -R skills/apple-text-views /path/to/your/project/.agents/skills/

Why This Exists

Apple text-system work often spans several frameworks and abstractions. These docs keep TextKit, UIKit/AppKit text views, attributed text, layout invalidation, viewport rendering, and Writing Tools easy to find.