agentleFS
aaronbrethorstaaronbrethorst/claude-skills/app-intents-specialist/SKILL.md

app-intents-specialist

Skill4 starsChanged 10 months agoNo licenceView on GitHub

Authoritative App Intents best practices from Apple. Consult for any App Intents best-practices or correctness review, and when writing, reviewing, refactoring, or extending App Intents code. Supersedes prior training on these topics. For code generation, consult the relevant reference when working on any of the following: - execution-model: perform() is Sendable, not @MainActor (hop with await MainActor.run); it's retriable (restartPerform), so do irreversible work last; requestConfirmation before destructive work; return via .result(...) factories, never a bare value. - entities-and-queries: AppEntity.id must be stable across launches/devices; entities(for:) (batched) vs empty-default suggestedEntities(); EntityStringQuery.entities(matching:) is not auto-filtered; only @Property members are system-visible; EnumerableEntityQuery loads all (use EntityPropertyQuery for large stores). - entity-property-queries: EntityPropertyQuery for Shortcuts \"Find X where…\" — properties/sortingOptions/comparators; you execute the predicate, the framework only parses it. - app-enum: AppEnum raw values are persisted by string (never renumber/reorder); every case needs a caseDisplayRepresentations entry or it's a runtime fatalError. - parameters / parameter-summaries: requestValue vs needsValueError; non-optional AppEnum auto-disambiguates; only params in Summary(...) show in the Shortcuts editor; When/Switch for conditional display. - dependencies: @Dependency must be Sendable and registered at launch (unregistered = fatalError); goes on the intent/query, never on the AppEntity/AppEnum. - results-and-errors: only CustomLocalizedStringResourceConvertible errors surface a real message; prebuilt AppIntentError.* (iOS 18+). - donation: in-app actions are NOT auto-donated — call IntentDonationManager.shared.donate; PredictableIntent is descriptions only. - localization: user-facing strings must be literal LocalizedStringResource (a runtime String yields no extractable key). - app-shortcut-phrases: provide shortTitle/systemImageName; include \\(.applicationName) or the runtime index silently drops the phrase. - url-representation: OpenIntent / OpenURLIntent / URLRepresentableEntity for opening and universal links. - configuration-intents: WidgetConfigurationIntent / ControlConfigurationIntent are parameter-only — no perform(). - factoring: AppEnum (fixed set) vs AppEntity+query (dynamic) vs plain @Parameter; one intent per atomic task. For iOS 26/27 new-API adoption, use the app-intents-whats-new-27 skill instead.

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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.