app-intents-workflowlisted

# App Intents Workflow ## Purpose Expose the smallest useful action and content surface outside an app without turning system integration into a second app architecture. Apple documents App Intents as the bridge that makes app actions and data discoverable in system experiences; select real user-recognizable verbs and entities before adding an intent type. ## When To Use - Use for `AppIntent`, `AppEntity`, `AppEnum`, `AppShortcutsProvider`, entity queries, result snippets, Spotlight indexing, widgets, controls, Live Activities, Siri, and Action button or Apple Pencil actions. - Use when an app action needs an explicit deep-link or scene-opening handoff after system invocation. - Hand off Xcode target, extension, build, simulator, and runtime inspection work to `xcode-build-run-workflow`; hand test plans and UI automation to `xcode-testing-workflow`. ## Single-Path Workflow 1. Apply the Apple docs gate through `explore-apple-swift-docs`. Confirm the framework, platform availability, and target system surface before changing code. 2. Define one user-recognizable verb and the minimum data it needs. Prefer an existing app domain type; do not invent a parallel intent-only repository, store, or DTO layer. 3. Classify the surface: direct action, parameterized action, entity lookup, App Shortcut, Spotlight result, widget/control action, Live Activity action, or hardware interaction. 4. Read `references/intent-entity-and-shortcut-shapes.md` for intent, entity, query, shortcut, a