app-intents
Implement App Intents to expose app functionality to Siri, Shortcuts, Spotlight, widgets, and Apple Intelligence.
Works with
1
total installs
1
this week
372
GitHub stars
0
upvotes
Install Skill
Run in your terminal
1
installs
1
this week
372
stars
What it does
Covers seven integration surfaces: Siri/Shortcuts, configurable widgets, Control Center, Spotlight search, Apple Intelligence schemas, interactive snippets, and visual intelligence queries
Requires shadow AppEntity models with EntityQuery variants (base, string search, enumerable, or singleton), plus AppEnum for fixed parameter choices
Includes AppShortcutsProvider for pr
Installation Guide
How to use app-intents on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
app-intents
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches app-intents from dpearson2699/swift-ios-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate app-intents. Access via /app-intents in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
App Intents (iOS 26+)
Implement, review, and extend App Intents to expose app functionality to Siri, Shortcuts, Spotlight, widgets, Control Center, and Apple Intelligence.
Contents
- Triage Workflow
- AppIntent Protocol
- @Parameter
- AppEntity
- EntityQuery (4 Variants)
- AppEnum
- AppShortcutsProvider
- Siri Integration
- Interactive Widget Intents
- Control Center Widgets (iOS 18+)
- Spotlight and IndexedEntity (iOS 18+)
- iOS 26 Additions
- Common Mistakes
- Review Checklist
- References
Triage Workflow
Step 1: Identify the integration surface
Determine which system feature the intent targets:
| Surface | Protocol | Since |
|---|---|---|
| Siri / Shortcuts | AppIntent |
iOS 16 |
| Configurable widget | WidgetConfigurationIntent |
iOS 17 |
| Control Center | ControlConfigurationIntent |
iOS 18 |
| Spotlight search | IndexedEntity |
iOS 18 |
| Apple Intelligence | @AppIntent(schema:) |
iOS 18 |
| Interactive snippets | SnippetIntent |
iOS 26 |
| Visual Intelligence | IntentValueQuery |
iOS 26 |
Step 2: Define the data model
- Create
AppEntityshadow models (do NOT conform core data models directly). - Create
AppEnumtypes for fixed parameter choices. - Choose the right
EntityQueryvariant for resolution. - Mark searchable entities with
IndexedEntityand@Property(indexingKey:).
Step 3: Implement the intent
- Conform to
AppIntent(or a specialized sub-protocol). - Declare
@Parameterproperties for all user-facing inputs. - Implement
perform() async throws -> some IntentResult. - Add
parameterSummaryfor Shortcuts UI. - Register phrases via
AppShortcutsProvider.
Step 4: Verify
- Build and run in Shortcuts app to confirm parameter resolution.
- Test Siri phrases with the intent preview in Xcode.
- Confirm Spotlight results for
IndexedEntitytypes. - Check widget configuration for
WidgetConfigurationIntentintents.
AppIntent Protocol
The system instantiates the struct via init(), sets parameters, then calls
perform(). Declare a title and parameterSummary for Shortcuts UI.
struct OrderSoupIntent: AppIntent {
static var title: LocalizedStringResource = "Order Soup"
static var description = IntentDescription("Place a soup order.")
@Parameter(title: "Soup") var soup: SoupEntity
@Parameter(title: "Quantity", default: 1) var quantity: Int
static var parameterSummary: some ParameterSummary {
Summary("Order \(\.$soup)") { \.$quantity }
}
func perform() async throws -> some IntentResult {
try await OrderService.shared.place(soup: soup.id, quantity: quantity)
return .result(dialog: "Ordered \(quantity) \(soup.name).")
}
}
Optional members: description (IntentDescription), openAppWhenRun (Bool),
isDiscoverable (Bool), authenticationPolicy (IntentAuthenticationPolicy).
@Parameter
Declare each user-facing input with @Parameter. Optional parameters are not
required; non-optional parameters with a default are pre-filled.
// WRONG: Non-optional parameter without default -- system cannot preview
@Parameter(title: "Count")
var count: Int
// CORRECT: Provide a default or make optional
@Parameter(title: "Count", default: 1)
var count: Int
@Parameter(title: "Count")
var count: Int?
Supported value types
Primitives: Int, Double, Bool, String, URL, Date, DateComponents.
Framework: Currency, Person, IntentFile. Measurements: Measurement<UnitLength>,
Measurement<UnitTemperature>, and others. Custom: any AppEntity or AppEnum.
Common initializer patterns
// Basic
@Parameter(title: "Name")
var name: String
// With default
@Parameter(title: "Count", default: 5)
var count: Int
// Numeric slider
@Parameter(title: "Volume", controlStyle: .slider, inclusiveRange: (0, 100))
var volume: Int
// Options provider (dynamic list)
@Parameter(title: "Category", optionsProvider: CategoryOptionsProvider())
var category: Category
// File with content types
@Parameter(title: "Document", supportedContentTypes: [.pdf, .plainText])
var document: IntentFile
// Measurement with unit
@Parameter(title: "Distance", defaultUnit: .miles, supportsNegativeNumbers: false)
var distance: Measurement<UnitLength>
See references/appintents-advanced.md for all initializer variants.
AppEntity
Create shadow models that mirror app data -- never conform core data model types directly.
struct SoupEntity: AppEntity {
static let defaultQuery = SoupEntityQuery()
static var typeDisplayRepresentation: TypeDisplayRepresentation = "Soup"
var id: String
@Property(title: "Name") var name: String
@Property(title: "Price") var price: Double
var displayRepresentation: DisplayRepresentation {
DisplayRepresentation(title: "\(name)", subtitle: "$\(String(format: "%.2f", price))")
}
init(from soup: Soup) {
self.id = soup.id; self.name = soup.name; self.price = soup.price
}
}
Required: id, defaultQuery (static), displayRepresentation,
typeDisplayRepresentation (static). Mark properties with @Property(title:)
to expose for filtering/sorting. Properties without @Property remain internal.
EntityQuery (4 Variants)
1. EntityQuery (base -- resolve by ID)
struct SoupEntityQuery: EntityQuery {
func entities(for identifiers: [String]) async throws -> [SoupEntity] {
SoupStoreList & Monetize Your Skill
Submit your Claude Code skill and start earning
Get started →Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
386mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
98pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- DDiego Mehta★★★★★Dec 24, 2024
Useful defaults in app-intents — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- AArya Malhotra★★★★★Dec 16, 2024
We added app-intents from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- SShikha Mishra★★★★★Dec 12, 2024
Solid pick for teams standardizing on skills: app-intents is focused, and the summary matches what you get after install.
- NNoah Martin★★★★★Dec 12, 2024
I recommend app-intents for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMin Liu★★★★★Dec 8, 2024
Keeps context tight: app-intents is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSakshi Patil★★★★★Nov 27, 2024
I recommend app-intents for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- OOlivia Khan★★★★★Nov 27, 2024
Registry listing for app-intents matched our evaluation — installs cleanly and behaves as described in the markdown.
- MMin Bhatia★★★★★Nov 23, 2024
app-intents reduced setup friction for our internal harness; good balance of opinion and flexibility.
- NNoah Mehta★★★★★Nov 15, 2024
Useful defaults in app-intents — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNoor Diallo★★★★★Nov 7, 2024
Solid pick for teams standardizing on skills: app-intents is focused, and the summary matches what you get after install.
showing 1-10 of 53
Discussion
Comments — not star reviews- No comments yet — start the thread.