ios-app-intents

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill ios-app-intents-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-app-intents
Source: https://github.com/AarnavBaddam/skills/tree/main/ios-app-intents
Command: npx skills add https://github.com/AarnavBaddam/skills --skill ios-app-intents-aarnavbaddam

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 decisions about which intents, entities, and shortcuts to ship, and mistakes lead to bloated or unusable integrations. ## Core Features & Use Cases - Intent Design Guidance: Choose the first high-value actions, decide between inline and open-app intents, and plan a clean runtime handoff into the main app scene. - Entity and Query Modeling: Define narrow AppEntity types, EntityQuery implementations, AppEnum choices, and dependent queries for widget configuration. - Swift Code Templates: Copy and adapt ready-made templates for open-app handoff intents, inline action intents, widget configuration intents, and AppShortcutsProvider entries. - Use Case: You want your task app to support "Create a task" from Siri and Shortcuts. Use this Skill to design a small intent surface, implement the inline action intent, and register shortcut phrases. ## 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 intent, 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. Use openAppWhenRun for actions that should open the app and inline intents for actions that complete in the background.

How do I pass data from an App Intent into my app's UI?

Use a central router or handoff service that stores the handled intent, then let the main app scene translate it into tabs, sheets, or routes. This keeps one predictable entry path instead of scattered side effects.

When should I use AppEntity versus AppEnum in App Intents?

Use AppEnum for small fixed sets like tabs, modes, or visibility levels. Use AppEntity with an EntityQuery when the system needs to identify, display, or disambiguate real app objects such as accounts, projects, or lists.

Can App Intents be reused for widget configuration?

Yes, define a WidgetConfigurationIntent that reuses the same AppEntity types your shortcuts use. You can also use IntentParameterDependency so one parameter, like a selected workspace, filters the choices for another.

What are common mistakes when adding App Intents to an app?

Common mistakes include exposing every screen as an intent, mirroring the entire data model as entities, and using vague shortcut phrases. Start with one or two high-value actions, keep entities narrow, and write direct task-oriented phrases.