ios-app-intents

Design App Intents, app entities, and App Shortcuts for iOS system surfaces.

25|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill ios-app-intents-wisdom-in-a-nutshell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ios-app-intents
Source: https://github.com/wisdom-in-a-nutshell/agents/tree/main/plugins-source/external/build-ios-apps/skills/ios-app-intents
Command: npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill ios-app-intents-wisdom-in-a-nutshell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Exposing app actions and content to iOS system surfaces like Shortcuts, Siri, Spotlight, and widgets requires careful design of App Intents, entities, and shortcuts, and developers often over-expose screens or mirror entire data models instead of shipping a small useful surface. ## Core Features & Use Cases - Intent Design Workflow: Guides selection of 1-3 high-value actions, deciding between inline completion and open-app handoff with a single routing path. - Entity and Query Patterns: Provides AppEntity, EntityQuery, AppEnum, and dependent query templates for system-facing object selection. - Code Templates: Includes Swift templates for open-app intents, inline actions, widget configuration intents, and AppShortcutsProvider entries. - Use Case: A developer wants users to create tasks via Siri and configure a widget by workspace; this Skill provides the intent structure, entity queries, and shortcut phrases to ship that integration. ## Quick Start Use the ios-app-intents skill to design the first App Intents surface for my iOS app, including one open-app intent, one inline action, and an AppShortcutsProvider.

Frequently Asked Questions about ios-app-intents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose app actions to Siri and Shortcuts on iOS?▼

Define AppIntent types with clear titles and parameters, then register them in an AppShortcutsProvider with verb-led phrases. Keep intents thin and route open-app actions through a single handoff service in your main scene.

What is the difference between open-app and inline App Intents?▼

Open-app intents set openAppWhenRun to true and hand off to the app UI for richer workflows. Inline intents set it to false, perform the action directly in perform(), and return dialog feedback without launching the app.

How do I use AppEntity and EntityQuery in App Intents?▼

Create an AppEntity with an identifier and display representation, then provide a default query implementing entities(for:), suggestedEntities(), and optionally defaultResult(). Keep the entity narrower than your persistence model.

Can App Intents be used for widget configuration?▼

Yes, define a WidgetConfigurationIntent with AppEntity parameters so widgets reuse the same entity surface as your shortcuts. Use IntentParameterDependency when one parameter, like workspace, should filter another, like project.

When should I use AppEnum instead of AppEntity?▼

Use AppEnum for fixed choices such as tabs, modes, or visibility levels where the set of options is known at compile time. Reserve AppEntity for dynamic objects like accounts or projects that require lookup and suggestion.