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

apple-hig-foundations

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines foundations for accessibility, app icons, branding, color, Dark Mode, icons, images, immersive experiences, inclusion, layout, materials, motion, privacy, right-to-left layout, SF Symbols, spatial layout, typography, and writing. Use when designing, reviewing, or implementing Apple-platform interface foundations.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to apply the cross-cutting design foundations that shape every Apple-platform experience.

    line 8
  2. Very specific:

    If the task is platform-specific, check apple-hig-getting-started first.

    line 16
  3. Distinctive:

    Use SF Symbols where a symbol exists and communicates clearly.

    line 27
  4. Distinctive:

    Use platform typography, Dynamic Type, semantic colors, system materials, and native accessibility semantics before custom styles.

    line 28
  5. Distinctive:

    Use adjacent skills deliberately.

    line 31
  6. Very specific:

    Use fluid-interface-design for fluid motion, direct manipulation, springs, materials, typography polish, and reduced-motion details.

    line 32
  7. Very specific:

    Use apple-charts for chart-specific design.

    line 33

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

Use this skill to apply the cross-cutting design foundations that shape every Apple-platform experience. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

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

Workflow

  1. Establish the context.
    • Identify platform, device posture, input methods, content type, task criticality, user risk, and accessibility needs.
    • If the task is platform-specific, check apple-hig-getting-started first.
  2. Design foundations in this order.
    • Accessibility and inclusion: make the experience operable, understandable, and respectful for more people.
    • Privacy: minimize collection, expose control, and avoid surprising disclosure.
    • Layout and spatial layout: make hierarchy, grouping, safe areas, depth, and adaptive behavior clear.
    • Typography and writing: make text legible, concise, localizable, and hierarchy-aware.
    • Color, Dark Mode, icons, images, and app icons: use visual identity to clarify meaning, not decoration.
    • Materials and motion: use depth, transparency, and movement only when they reinforce hierarchy, causality, or focus.
  3. Prefer system primitives.
    • Use SF Symbols where a symbol exists and communicates clearly.
    • Use platform typography, Dynamic Type, semantic colors, system materials, and native accessibility semantics before custom styles.
    • For web implementations, map to the same intent: semantic HTML, responsive layout, reduced motion/transparency, high contrast, keyboard access, and localized text.
  4. Use adjacent skills deliberately.
    • Use fluid-interface-design for fluid motion, direct manipulation, springs, materials, typography polish, and reduced-motion details.
    • Use apple-charts for chart-specific design.
  5. Refresh official HIG pages when exact wording or recently changed guidance matters.

Foundation Rules

  • Accessibility is a design input. Include Dynamic Type, VoiceOver, Switch Control, keyboard navigation, contrast, reduced motion, reduced transparency, and alternate text where relevant.
  • Inclusion affects language, imagery, defaults, pronouns, assumptions, and failure states. Avoid making a single user identity the default.
  • Privacy-sensitive UI needs clear purpose, minimal data, transparent permission timing, and reversible choices.
  • Layout should explain relationships. Use spacing, grouping, alignment, hierarchy, and platform safe areas before adding borders or decoration.
  • Color must carry semantic or brand meaning and must not be the only signal.
  • Dark Mode is not simple inversion. Verify contrast, emphasis, shadows, materials, imagery, and semantic colors in both appearances.
  • Typography should support scanning and reading. Avoid tiny fixed text; test with Dynamic Type and localization.
  • Motion should communicate state and causality, remain interruptible where interactive, and have a reduced-motion equivalent.
  • Materials should express depth and separation; avoid stacking translucent surfaces until legibility collapses.
  • RTL support is structural: navigation direction, alignment, icons, gestures, text fields, and layout mirroring all need review.

Topic Map

Official HIG pages currently under Foundations:

Review Checklist

  • The interface remains usable with assistive technologies, increased contrast, reduced motion, reduced transparency, larger text, localization expansion, RTL layout, and dark appearance.
  • Visual identity clarifies recognition and meaning without overpowering content.
  • Privacy-sensitive states avoid surprise and give the user control.
  • Motion, material, color, type, and imagery all support the task hierarchy.

Attribution

Apple, SF Symbols, and related product 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.