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

   /plugin install apple-text@apple-text

3. 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 has an Apple text-system problem but the right specialist skill is not obvious, or when the request mixes multiple text subsystems.

apple-text-audit Use when reviewing Apple text code for TextKit fallback risk, editing lifecycle bugs, deprecated APIs, or Writing Tools breakage.

apple-text-recipes Use when building common text features or looking up quick recipes.

apple-text-texteditor-26 Use when building rich-text editing with SwiftUI TextEditor on iOS 26+ or evaluating whether it replaces a UITextView wrapper.

apple-text-textkit-diag Use when debugging broken text.

apple-text-views Use when choosing between SwiftUI Text/TextField/TextEditor, UITextView, or NSTextView.

apple-text-apple-docs Use when you need official Apple-authored documentation, exact API signatures, or Swift diagnostic explanations from Xcode-bundled docs.

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.