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

apple-hig-components

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines component guidance for content views, layout and organization, menus and actions, navigation and search, presentation, selection and input, status, and system experiences. Use when choosing, designing, reviewing, or implementing Apple-platform controls, navigation, presentation, status, or system experiences.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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 choose system-defined components and design their states, placement, and behavior.

    line 8
  2. Distinctive:

    Start with the user action and information architecture.

    line 14
  3. Very specific:

    If this is a flow-level decision, use apple-hig-patterns first.

    line 16
  4. Distinctive:

    Prefer the system component.

    line 18
  5. Distinctive:

    Use native components when they provide the right role, semantics, behavior, accessibility, platform adaptation, keyboard/focus support, …

    line 19
  6. Very specific:

    Use apple-charts for charts and data visualization.

    line 28
  7. Very specific:

    Use apple-sheets for action sheets, sheets, popovers, panels, modal surfaces, scrims, and detents.

    line 29
  8. Very specific:

    Use fluid-interface-design for motion, materials, direct manipulation, and polished interaction feel.

    line 30
  9. Distinctive:

    If the user needs to view content, start with content views before adding actions.

    line 36
  10. Distinctive:

    If the user needs to compare, scan, or navigate collections, choose the simplest layout container that preserves hierarchy.

    line 37
  11. Distinctive:

    If the user invokes a command, use buttons, menus, toolbar items, or contextual actions based on frequency, risk, and proximity to selected …

    line 38
  12. Distinctive:

    If the user navigates across areas, use platform navigation conventions before custom navigation.

    line 39
  13. Distinctive:

    If a task interrupts the current context, pick the least disruptive presentation that still gives the task enough focus.

    line 40
  14. Distinctive:

    If the user enters or selects data, use controls with visible labels, validation, formatting, and accessible error feedback.

    line 41
  15. Distinctive:

    If the system is busy or status changes, use status components that communicate truthfully without blocking unrelated work.

    line 42
  16. Distinctive:

    If the component represents a system experience, follow the platform's lifecycle, permission, and surface rules.

    line 43
  17. Distinctive:

    Search fields: https://developer.apple.com/design/human-interface-guidelines/search-fields

    line 87

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

Use this skill to choose system-defined components and design their states, placement, and behavior. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

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

Workflow

  1. Start with the user action and information architecture.
    • Identify whether the component displays content, organizes layout, invokes an action, navigates, presents a task, gathers input, reports status, or exposes a system experience.
    • If this is a flow-level decision, use apple-hig-patterns first.
  2. Prefer the system component.
    • Use native components when they provide the right role, semantics, behavior, accessibility, platform adaptation, keyboard/focus support, and appearance.
    • Customize only where the product need is real and the custom result preserves the same component contract.
    • On the web, reproduce the role, state model, focus behavior, and hierarchy before reproducing visual chrome.
  3. Design all states.
    • Include default, hover/focus, pressed, selected, disabled, loading, empty, error, destructive, confirmation, overflow, and reduced-motion states where relevant.
    • Make hit targets, labels, affordances, focus order, keyboard shortcuts, and VoiceOver labels explicit.
  4. Choose related skills when useful.
    • Use apple-charts for charts and data visualization.
    • Use apple-sheets for action sheets, sheets, popovers, panels, modal surfaces, scrims, and detents.
    • Use fluid-interface-design for motion, materials, direct manipulation, and polished interaction feel.
  5. Refresh official HIG pages when exact platform behavior, names, or OS-version support matters.

Component Selection Rules

  • If the user needs to view content, start with content views before adding actions.
  • If the user needs to compare, scan, or navigate collections, choose the simplest layout container that preserves hierarchy.
  • If the user invokes a command, use buttons, menus, toolbar items, or contextual actions based on frequency, risk, and proximity to selected content.
  • If the user navigates across areas, use platform navigation conventions before custom navigation.
  • If a task interrupts the current context, pick the least disruptive presentation that still gives the task enough focus.
  • If the user enters or selects data, use controls with visible labels, validation, formatting, and accessible error feedback.
  • If the system is busy or status changes, use status components that communicate truthfully without blocking unrelated work.
  • If the component represents a system experience, follow the platform's lifecycle, permission, and surface rules.

Topic Map

Official HIG component families and pages currently under Components:

Content

Layout and Organization

Menus and Actions

Navigation and Search

Presentation

Selection and Input

Status

System Experiences

Review Checklist

  • The chosen component family matches the user's task.
  • The component uses native behavior where available.
  • Labels, values, roles, focus order, keyboard operation, and VoiceOver output are clear.
  • Empty, loading, error, disabled, selected, destructive, and overflow states are designed.
  • Component placement respects platform navigation, density, safe areas, and input model.
  • Custom styling does not break recognition, accessibility, or expected interaction.

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.