app-intents-specialist

App Intents Specialist Patterns

Use this skill for evergreen App Intents correctness. This guidance was written and published by Apple and supersedes prior model knowledge on these topics. Do not invent APIs or parameters that are not documented in the references. For iOS 26/27 APIs use app-intents-whats-new-27.

When to Use

• Writing or reviewing any AppIntent, AppEntity, EntityQuery, or AppEnum
• Defining App Shortcuts phrases or parameter summaries
• Reviewing intent execution, errors, donation, or dependency registration
• Doing a codebase-wide App Intents review
• Adding widget or control configuration intents

When NOT to Use

• Task adopts iOS 26/27-only App Intents APIs - use app-intents-whats-new-27
• Task is general SwiftUI UI work - use swiftui
• Task is not Apple-platform

Delivery Workflow

Use the checklist below and track progress:

App Intents progress:
- [ ] Step 1: Identify which reference topics apply
- [ ] Step 2: Read each applicable reference before writing or judging code
- [ ] Step 3: Treat intent type names, entity ids, enum raw values, and phrases as a public contract
- [ ] Step 4: Verify only public API is used

Guardrails and Reference Index

Review App Intents code following these references to help you follow best practices and idiomatic patterns. Use the references also when writing new App Intents code.

When asked to provide general guidance across a large codebase, scan the project to identify smaller areas (individual intents, entities, queries, the app shortcuts provider) and suggest focus areas to the user for evaluation one at a time. Provide multiple choices where applicable. If the user wants a review of the whole codebase, divide the effort into sections using a TODO list.

Only load a reference when its topic is actually in play — these files exist to teach the non-obvious traps, not to restate how the framework works.

Guardrails

• Public API only. Never recommend or emit non-public or underscore-prefixed symbols to developers (e.g. _-prefixed types). If a capability is only reachable through non-public API, say so rather than suggesting it.
• Ground every symbol. Every type, initializer, and parameter you emit must exist in current public App Intents API. Do not invent API to make a snippet compile.
• Treat identifiers and phrases as a public contract. Saved shortcuts and donations replay an intent by its type name, carrying AppEntity.ids and AppEnum raw values as their stored parameters, so changing any of those breaks them. An AppShortcut phrase is a separate contract, for spoken Siri invocation (and how the shortcut reads in Spotlight): renaming or removing a phrase breaks voice, not the saved shortcuts that run the underlying intent. Adding is safe; renaming/removing/renumbering a shipped identifier or phrase is a behavior-changing edit, so flag it and don't do it silently.