agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/ios-app-intents/SKILL.md

ios-app-intents

Skill7 starsChanged 4 months agoMITView on GitHub

Design, implement, and verify App Intents, App Entities, App Shortcuts, widgets, Siri, Spotlight, and Apple Intelligence surfaces with stable identity and safe execution.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start from a user-visible action that is useful outside the main app.

    line 10
  2. Distinctive:

    Keep identifiers stable across launches and devices when the capability requires continuity.

    line 12
  3. Distinctive:

    Keep intent execution deterministic and independent from foreground-only UI state.

    line 14
  4. Distinctive:

    Verify discovery and execution in each claimed surface, including foreground/background behavior and locked-device constraints.

    line 16
  5. Distinctive:

    Read references/contract.md for the intent contract and test matrix.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

iOS App Intents

Workflow

  1. Start from a user-visible action that is useful outside the main app.
  2. Define parameters, entity identity, lookup/query behavior, confirmation rules, execution mode, cancellation, and result copy before code.
  3. Keep identifiers stable across launches and devices when the capability requires continuity.
  4. Gate destructive, sensitive, shared, or public changes with the appropriate confirmation and ownership checks.
  5. Keep intent execution deterministic and independent from foreground-only UI state.
  6. Localize titles, parameter summaries, errors, shortcut phrases, and result dialogs.
  7. Verify discovery and execution in each claimed surface, including foreground/background behavior and locked-device constraints.

Current API caution

Apple's June 2026 App Intents updates add new execution, cancellation, undo, ownership, indexing, and Apple Intelligence integration options. Consult the exact SDK documentation and availability before using them. Do not rename those additions as an iOS version without primary-source evidence.

Read references/contract.md for the intent contract and test matrix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free