Commands
Command overview for the Apple Text plugin.
One front door
Use the command surface when you know the question belongs to Apple text, but you do not want to pick the skill yourself.
This page covers the main intake command and the routes it typically suggests.
/apple-text:ask
Section titled “/apple-text:ask”Natural-language entry point for Apple Text. Use when the user has an Apple text question but does not know which skill or agent to invoke.
Good prompts
- broad Apple text questions
- first-contact prompts that mention symptoms instead of APIs
- mixed requests where routing matters more than memorizing the catalog
Skip this when
- the user already named the exact subsystem
- you are already on a matching skill page
- the task is a findings-first scan over real code
Typical routes
Section titled “Typical routes”Try prompts like these
Section titled “Try prompts like these”- “Why did my UITextView fall back to TextKit 1?”
- “Review this editor code for TextKit problems.”
- “Should this screen use TextEditor or UITextView?”
Next move
Section titled “Next move”If the prompt is already scoped, start with Skills. If the task is a specialist code scan, use Agents.
/apple-text:release-preflight
Section titled “/apple-text:release-preflight”Pre-release validation with guided fixes — checks versions, regenerates derived files, runs full validation, and reports blockers.
Good prompts
- broad Apple text questions
- first-contact prompts that mention symptoms instead of APIs
- mixed requests where routing matters more than memorizing the catalog
Skip this when
- the user already named the exact subsystem
- you are already on a matching skill page
- the task is a findings-first scan over real code
Typical routes
Section titled “Typical routes”Try prompts like these
Section titled “Try prompts like these”- “Why did my UITextView fall back to TextKit 1?”
- “Review this editor code for TextKit problems.”
- “Should this screen use TextEditor or UITextView?”
Next move
Section titled “Next move”If the prompt is already scoped, start with Skills. If the task is a specialist code scan, use Agents.
/apple-text:skill-quality
Section titled “/apple-text:skill-quality”Audit all skills for quality gaps — freshness, descriptions, routing, lint — and produce a prioritized fix list.
Good prompts
- broad Apple text questions
- first-contact prompts that mention symptoms instead of APIs
- mixed requests where routing matters more than memorizing the catalog
Skip this when
- the user already named the exact subsystem
- you are already on a matching skill page
- the task is a findings-first scan over real code
Typical routes
Section titled “Typical routes”Try prompts like these
Section titled “Try prompts like these”- “Why did my UITextView fall back to TextKit 1?”
- “Review this editor code for TextKit problems.”
- “Should this screen use TextEditor or UITextView?”
Next move
Section titled “Next move”If the prompt is already scoped, start with Skills. If the task is a specialist code scan, use Agents.