Commands

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

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

apple-text Broad questions route here first.

apple-text-audit Review or integration flows usually land here.

apple-text-textkit-diag Broken behavior routes into diagnosis.

apple-text-views Tradeoff questions route into comparison.

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

If the prompt is already scoped, start with Skills. If the task is a specialist code scan, use Agents.