agentleFS
inttegrointtegro/labor/skills/apple-hig-getting-started/SKILL.md

apple-hig-getting-started

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines getting-started and platform-fit guidance. Use when designing, reviewing, or implementing an app for iOS, iPadOS, macOS, tvOS, visionOS, watchOS, or Apple-platform games, especially before choosing foundations, patterns, components, inputs, or technologies.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 10 are distinctive, and 5 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to decide how an experience should adapt to each Apple platform before selecting lower-level components or patterns.

    line 8
  2. Distinctive:

    Ask which platforms are first-class and which are adaptations.

    line 15
  3. Distinctive:

    If the user names no platform, choose the primary usage context from the product: phone, tablet, desktop, TV, spatial, watch, or game.

    line 16
  4. Distinctive:

    Start from platform intent, not screen size.

    line 18
  5. Distinctive:

    Keep the same core model, terminology, and task outcomes across platforms.

    line 28
  6. Distinctive:

    Do not ship one scaled layout across all devices.

    line 30
  7. Very specific:

    Use apple-hig-foundations for accessibility, layout, color, materials, motion, typography, privacy, writing, and related primitives.

    line 33
  8. Very specific:

    Use apple-hig-patterns for user flows such as onboarding, search, settings, loading, notifications, or file management.

    line 34
  9. Very specific:

    Use apple-hig-components for controls, navigation, presentation surfaces, status UI, and system experiences.

    line 35
  10. Very specific:

    Use apple-hig-inputs for touch, pointer, keyboard, focus, gaze, remote, game controller, and sensor input.

    line 36
  11. Very specific:

    Use apple-hig-technologies for Apple Pay, Siri, Wallet, CarPlay, HealthKit, SharePlay, iCloud, and other Apple technology integrations.

    line 37
  12. Distinctive:

    Verify with platform evidence.

    line 39
  13. Distinctive:

    If exact current wording, new platform behavior, or OS-version support matters, reopen the official HIG page before finalizing.

    line 42
  14. Distinctive:

    Prefer direct manipulation, familiar system conventions, and immediate feedback.

    line 47
  15. Distinctive:

    Keep visual hierarchy calm.

    line 49

≈ “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 Getting Started

Use this skill to decide how an experience should adapt to each Apple platform before selecting lower-level components or patterns. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

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

Workflow

  1. Identify the target platform set.
    • Ask which platforms are first-class and which are adaptations.
    • If the user names no platform, choose the primary usage context from the product: phone, tablet, desktop, TV, spatial, watch, or game.
  2. Start from platform intent, not screen size.
    • iPhone: short, personal, one-handed, interruptible tasks.
    • iPad: focused touch work, larger layouts, multitasking, keyboard and pointer support.
    • Mac: dense productivity, windows, menu bar, keyboard fluency, file workflows.
    • Apple TV: distance viewing, focus engine, minimal text entry, remote-first navigation.
    • Apple Vision Pro: spatial context, depth, eye and hand input, comfort, persistent surroundings.
    • Apple Watch: glanceable, short interactions, complications, haptics, personal health/safety context.
    • Games: immersion and responsiveness first; system conventions still apply around controls, settings, privacy, and purchase.
  3. Preserve the product's identity while adapting structure.
    • Keep the same core model, terminology, and task outcomes across platforms.
    • Let navigation density, command placement, input support, and presentation style differ by platform.
    • Do not ship one scaled layout across all devices.
  4. Choose the next HIG skill.
    • Use apple-hig-foundations for accessibility, layout, color, materials, motion, typography, privacy, writing, and related primitives.
    • Use apple-hig-patterns for user flows such as onboarding, search, settings, loading, notifications, or file management.
    • Use apple-hig-components for controls, navigation, presentation surfaces, status UI, and system experiences.
    • Use apple-hig-inputs for touch, pointer, keyboard, focus, gaze, remote, game controller, and sensor input.
    • Use apple-hig-technologies for Apple Pay, Siri, Wallet, CarPlay, HealthKit, SharePlay, iCloud, and other Apple technology integrations.
  5. Verify with platform evidence.
    • For native work, inspect the target SDK/framework conventions before inventing custom behavior.
    • For web approximations, translate the behavior and hierarchy rather than cloning Apple chrome literally.
    • If exact current wording, new platform behavior, or OS-version support matters, reopen the official HIG page before finalizing.

Design Principles

  • Make the primary task obvious in the first screen or state.
  • Prefer direct manipulation, familiar system conventions, and immediate feedback.
  • Preserve user control: clear exits, reversible operations, predictable state, and safe destructive actions.
  • Keep visual hierarchy calm. Let content and task state drive emphasis.
  • Respect accessibility, localization, privacy, and platform input from the start, not as late QA.
  • Make cross-platform adaptation feel native on each platform, not merely responsive.

Topic Map

Official HIG pages currently under Getting started:

Review Checklist

  • The platform choice is explicit.
  • Each platform adaptation has a clear reason.
  • The design uses system conventions where they fit.
  • Content, navigation, commands, input, and presentation match the platform's dominant context.
  • Accessibility, localization, privacy, and state recovery are accounted for.

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.