Example Conversations
Routing smoke tests and example interactions for the Apple Text plugin.
Use this page when you want to see how the public entry points should work in practice.
Treat these as routing smoke tests and as examples of how the plugin should respond. Each linked skill name goes to the actual skill page so you can inspect the target surface directly.
Ask Command
Section titled “Ask Command”User
/apple-text:ask Why is my NSTextView rendering stale after I mutate the backing storage?Expected behavior
- Routes to
apple-text-layout-invalidation,apple-text-storage, orapple-text-textkit-diag - Does not require the user to know plugin internals
- Keeps the answer on Apple text layout mechanics rather than generic editor advice
Why this matters: the plain-language command should handle ambiguity and route cleanly without forcing the user to learn the catalog first.
Router
Section titled “Router”User
Use apple-text and explain why my UITextView lost TextKit 2.Expected behavior
- Routes to
apple-text-fallback-triggersorapple-text-textkit-diag - Explains fallback triggers first
- Avoids drifting into generic SwiftUI guidance
Why this matters: the router should help the user reach the right skill without restating the catalog.
View Selection
Section titled “View Selection”User
Use apple-text-views and tell me whether this should be TextEditor or UITextView.I need syntax highlighting and inline attachments.Expected behavior
- Chooses
UITextView - Explains why
TextEditoris not enough - Points to
apple-text-representableif the user is in SwiftUI - Keeps the choice concrete instead of listing every possible text surface
Why this matters: decision skills should answer the choice directly, then add supporting skills only when needed.
Audit Workflow
Section titled “Audit Workflow”User
Use apple-text-audit on Sources/Editor and list the highest-risk issues first.Expected behavior
- Delegates to
textkit-auditor - Returns findings by severity with file references
- Calls out fallback triggers, editing lifecycle issues, and deprecated APIs
Why this matters: review flows should return prioritized findings rather than a general walkthrough.
Writing Tools
Section titled “Writing Tools”User
Use apple-text-writing-tools and show how to keep code blocks out of Writing Tools rewrites.Expected behavior
- Focuses on Writing Tools APIs and ignored ranges
- Does not turn into a generic AI feature explanation
- Links protected-range guidance back to
apple-text-writing-tools
Why this matters: the response should stay focused on editor implementation details even when the feature touches AI.
Representable Bridge
Section titled “Representable Bridge”User
Use apple-text-representable and fix cursor jump in my SwiftUI wrapper around UITextView.Expected behavior
- Focuses on coordinator/update cycle issues
- Mentions state synchronization and selection preservation
- Links to the specialist workflow instead of stopping at broad SwiftUI framing
Why this matters: wrapper problems should stay focused on wrapper mechanics rather than broad SwiftUI advice.
Coverage Map
Section titled “Coverage Map”- Broad intake:
/apple-text:ask,apple-text - Decision paths:
apple-text-views,apple-text-layout-manager-selection - Workflow paths:
apple-text-audit,apple-text-writing-tools,apple-text-representable