Quick Start

Fastest path from install to first good answer

Add the marketplace, install Apple Text in Claude Code, verify it, then ask one broad Apple text question.

This page is a short path from installation to a first question.

1. Add the marketplace

   /plugin marketplace add sitapix/apple-text

2. Install the plugin

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

3. Verify installation

   Use /plugin, then open Manage and install. Apple Text should be listed there.

4. Ask one plain-language question

   Start with /apple-text:ask.

   Good first prompts:

   • “My UITextView fell back to TextKit 1”
   • “Which text view should I use?”
   • “How do I wrap UITextView in SwiftUI?”

Advanced paths

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.

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.

Route common prompts

• “I have an Apple text problem but I do not know the subsystem yet.” -> start with /apple-text:ask.
• “Review this editor code for risks.” -> start with apple-text-audit.
• “My layout is stale or TextKit fell back.” -> start with apple-text-textkit-diag.
• “Should this use TextEditor, UITextView, or NSTextView?” -> start with apple-text-views.

What next

• Read Routing Model if the question is still broad.
• Use Problem Routing if you already know the answer shape.
• Browse Skills if you want the full catalog.