agentleFS
inttegrointtegro/labor/skills/apple-hig-technologies/SKILL.md

apple-hig-technologies

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines technology-integration guidance for AirPlay, Always On, App Clips, Apple Pay, augmented reality, CareKit, CarPlay, Game Center, Generative AI, HealthKit, HomeKit, iCloud, ID Verifier, iMessage apps and stickers, in-app purchase, Live Photos, Mac Catalyst, machine learning, Maps, NFC, Photo editing, ResearchKit, SharePlay, ShazamKit, Sign in with Apple, Siri, Tap to Pay on iPhone, VoiceOver, and Wallet. Use when Codex is designing, reviewing, or implementing Apple technology integrations or Apple-platform service experiences.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    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:

    Use this skill to decide whether and how an Apple technology belongs in an app experience.

    line 8
  2. Distinctive:

    Verify device/platform availability, entitlement requirements, geography, age, payment, account, privacy, and fallback constraints.

    line 16
  3. Distinctive:

    If the integration is not central to the task, keep it secondary or omit it.

    line 17
  4. Distinctive:

    Use system flows and branding rules.

    line 19
  5. Distinctive:

    Prefer Apple-provided UI, sheets, buttons, authorization flows, and terminology.

    line 20
  6. Distinctive:

    Do not re-create secure, payment, identity, health, wallet, Siri, or permission surfaces when system UI exists.

    line 21
  7. Distinctive:

    Keep Apple brand and product names exact.

    line 22
  8. Distinctive:

    Ask at the moment of clear user intent.

    line 26
  9. Distinctive:

    Avoid logging or exposing sensitive identifiers, payment details, health data, identity documents, precise location, or voice content.

    line 28
  10. Distinctive:

    Always On: https://developer.apple.com/design/human-interface-guidelines/always-on

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Apple HIG Technologies

Use this skill to decide whether and how an Apple technology belongs in an app experience. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

Source: https://developer.apple.com/design/human-interface-guidelines/technologies

Workflow

  1. Confirm user value and eligibility.
    • State the user problem the technology solves.
    • Verify device/platform availability, entitlement requirements, geography, age, payment, account, privacy, and fallback constraints.
    • If the integration is not central to the task, keep it secondary or omit it.
  2. Use system flows and branding rules.
    • Prefer Apple-provided UI, sheets, buttons, authorization flows, and terminology.
    • Do not re-create secure, payment, identity, health, wallet, Siri, or permission surfaces when system UI exists.
    • Keep Apple brand and product names exact; do not invent badges or endorsement language.
  3. Design the permission and privacy story.
    • Explain why data or capability access is needed before asking.
    • Ask at the moment of clear user intent.
    • Provide useful denied, unavailable, restricted, and revoked states.
    • Avoid logging or exposing sensitive identifiers, payment details, health data, identity documents, precise location, or voice content.
  4. Build lifecycle states.
    • Include setup, available, active, suspended, interrupted, denied, expired, failed, completed, and recovery states where applicable.
    • Make cross-device continuity explicit for iCloud, Handoff-like behavior, SharePlay, AirPlay, Wallet, CarPlay, and HomeKit.
  5. Refresh official HIG and framework docs for exact requirements.
    • Many technology pages are policy-sensitive and change over time.
    • For implementation, check the relevant Apple framework documentation in addition to HIG design guidance.

Integration Rules

  • Secure payment, identity, health, wallet, and commerce integrations must use system trust surfaces and clear recovery states.
  • AI and machine-learning features need transparent scope, user control, privacy protection, and graceful failure.
  • CarPlay, watchOS, TV, and spatial integrations must be designed for their attention model, not copied from iPhone.
  • SharePlay, AirPlay, Game Center, and collaboration features need clear participant state, ownership, privacy, and handoff behavior.
  • Maps, location, NFC, nearby interactions, and AR need physical-world safety, permission clarity, and useful unavailable states.
  • Siri, App Shortcuts, snippets, and voice flows need concise language, predictable results, and confirmation for risky operations.

Topic Map

Official HIG pages currently under Technologies:

Review Checklist

  • The technology solves a clear user problem and is available for the target platform.
  • System UI, permissions, branding, and policy-sensitive flows are respected.
  • Denied, unavailable, failed, interrupted, and recovery states are designed.
  • Sensitive data is minimized, protected, and never exposed unnecessarily.
  • The integration remains understandable without assuming expert Apple terminology.

Attribution

Apple and the product names listed above are trademarks of Apple Inc. This independently written skill is not affiliated with or endorsed by Apple.

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.