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

apple-hig-patterns

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines patterns for common user actions, tasks, and experiences. Use when Codex is designing, reviewing, or implementing flows such as onboarding, searching, settings, loading, notifications, feedback, file management, drag and drop, collaboration, media playback, haptics, undo and redo, accounts, ratings, help, workouts, or other Apple app workflow patterns.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to shape common Apple-platform workflows before selecting specific components.

    line 8
  2. Distinctive:

    Keep people oriented with clear source and destination states.

    line 23
  3. Distinctive:

    Keep destructive or irreversible actions confirmable and reversible where possible.

    line 25
  4. Distinctive:

    Avoid teaching before value.

    line 26
  5. Distinctive:

    Use the platform's expected pattern first.

    line 28
  6. Distinctive:

    Prefer system search, share, notification, media, document, settings, and account conventions.

    line 29
  7. Distinctive:

    Do not make custom flows for standard tasks unless the product domain requires it.

    line 30
  8. Distinctive:

    Keep cross-platform behavior conceptually consistent while allowing platform-specific presentation.

    line 31
  9. Very specific:

    Use apple-hig-components for exact control, menu, sheet, alert, navigation, and status choices.

    line 34
  10. Very specific:

    Use apple-hig-inputs for drag, focus, keyboard, gestures, pointer, and remote behavior.

    line 35
  11. Very specific:

    Use apple-charts for charting-data work.

    line 36
  12. Very specific:

    Use apple-sheets for sheets, action sheets, popovers, and modal presentation details.

    line 37
  13. Distinctive:

    Search should support recognition, correction, recency, filtering, empty states, and fast result refinement.

    line 45

≈ “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 Patterns

Use this skill to shape common Apple-platform workflows before selecting specific components. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

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

Workflow

  1. Classify the user job.
    • Acquisition and first use: launching, onboarding, help, ratings.
    • Data and control: entering data, searching, settings, undo and redo, file management.
    • System state: loading, notifications, feedback, full screen, multitasking, live-viewing apps.
    • Collaboration and transfer: sharing, collaboration, drag and drop, printing.
    • Media and sensory: audio, video, haptics, charts, workouts.
    • Identity and account: managing accounts.
  2. Preserve task continuity.
    • Keep people oriented with clear source and destination states.
    • Make progress, cancellation, errors, and recovery visible.
    • Keep destructive or irreversible actions confirmable and reversible where possible.
    • Avoid teaching before value; introduce features when they become useful.
  3. Use the platform's expected pattern first.
    • Prefer system search, share, notification, media, document, settings, and account conventions.
    • Do not make custom flows for standard tasks unless the product domain requires it.
    • Keep cross-platform behavior conceptually consistent while allowing platform-specific presentation.
  4. Choose supporting skills.
    • Use apple-hig-components for exact control, menu, sheet, alert, navigation, and status choices.
    • Use apple-hig-inputs for drag, focus, keyboard, gestures, pointer, and remote behavior.
    • Use apple-charts for charting-data work.
    • Use apple-sheets for sheets, action sheets, popovers, and modal presentation details.
  5. Refresh official HIG pages when exact current guidance matters.

Pattern Rules

  • Onboarding must earn its space. Prefer progressive disclosure over upfront tours.
  • Loading states need truthful progress, useful placeholders, cancellation where appropriate, and no fake certainty.
  • Search should support recognition, correction, recency, filtering, empty states, and fast result refinement.
  • Settings should be rare, organized by user mental model, and not a dumping ground for design uncertainty.
  • Notifications should be timely, actionable, respectful, and user-controlled.
  • Feedback should connect cause and effect without becoming noise.
  • Drag and drop should preview results, support cancellation, and preserve data integrity.
  • Undo and redo should be predictable, scoped, and discoverable for risky edits.
  • Media playback should respect context, interruptions, output routes, captions, controls, and background behavior.
  • Accounts should minimize authentication burden while protecting sensitive data and account switching.

Topic Map

Official HIG pages currently under Patterns:

Review Checklist

  • The pattern matches the user's task and platform context.
  • The flow has clear entry, progress, completion, cancellation, error, and recovery states.
  • Standard platform affordances are used where they fit.
  • Accessibility, privacy, localization, and multitasking interruptions are handled.
  • The design explains what happened, what can happen next, and how to reverse or recover.

Attribution

Apple and related platform names 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.