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.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- apple-sheetsSkill
- batch-commitSkill
- fluid-interface-designSkill
- git-change-controlSkill
- improve-animationsSkill
- marketing-art-directionSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- product-marketing-personasSkill
- security-auditSkill
- systems-builder-writingSkill
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
- Distinctive: line 8
Use this skill to choose system-defined components and design their states, placement, and behavior.
- Distinctive: line 14
Start with the user action and information architecture.
- Very specific: line 16
If this is a flow-level decision, use apple-hig-patterns first.
- Distinctive: line 18
Prefer the system component.
- Distinctive: line 19
Use native components when they provide the right role, semantics, behavior, accessibility, platform adaptation, keyboard/focus support, …
- Very specific: line 28
Use apple-charts for charts and data visualization.
- Very specific: line 29
Use apple-sheets for action sheets, sheets, popovers, panels, modal surfaces, scrims, and detents.
- Very specific: line 30
Use fluid-interface-design for motion, materials, direct manipulation, and polished interaction feel.
- Distinctive: line 36
If the user needs to view content, start with content views before adding actions.
- Distinctive: line 37
If the user needs to compare, scan, or navigate collections, choose the simplest layout container that preserves hierarchy.
- Distinctive: line 38
If the user invokes a command, use buttons, menus, toolbar items, or contextual actions based on frequency, risk, and proximity to selected …
- Distinctive: line 39
If the user navigates across areas, use platform navigation conventions before custom navigation.
- Distinctive: line 40
If a task interrupts the current context, pick the least disruptive presentation that still gives the task enough focus.
- Distinctive: line 41
If the user enters or selects data, use controls with visible labels, validation, formatting, and accessible error feedback.
- Distinctive: line 42
If the system is busy or status changes, use status components that communicate truthfully without blocking unrelated work.
- Distinctive: line 43
If the component represents a system experience, follow the platform's lifecycle, permission, and surface rules.
- Distinctive: line 87
Search fields: https://developer.apple.com/design/human-interface-guidelines/search-fields
≈ “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.
Files
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
- 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-patternsfirst.
- 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.
- 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.
- Choose related skills when useful.
- Use
apple-chartsfor charts and data visualization. - Use
apple-sheetsfor action sheets, sheets, popovers, panels, modal surfaces, scrims, and detents. - Use
fluid-interface-designfor motion, materials, direct manipulation, and polished interaction feel.
- Use
- 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
- Charts: https://developer.apple.com/design/human-interface-guidelines/charts
- Image views: https://developer.apple.com/design/human-interface-guidelines/image-views
- Text views: https://developer.apple.com/design/human-interface-guidelines/text-views
- Web views: https://developer.apple.com/design/human-interface-guidelines/web-views
Layout and Organization
- Boxes: https://developer.apple.com/design/human-interface-guidelines/boxes
- Collections: https://developer.apple.com/design/human-interface-guidelines/collections
- Column views: https://developer.apple.com/design/human-interface-guidelines/column-views
- Disclosure controls: https://developer.apple.com/design/human-interface-guidelines/disclosure-controls
- Labels: https://developer.apple.com/design/human-interface-guidelines/labels
- Lists and tables: https://developer.apple.com/design/human-interface-guidelines/lists-and-tables
- Lockups: https://developer.apple.com/design/human-interface-guidelines/lockups
- Outline views: https://developer.apple.com/design/human-interface-guidelines/outline-views
- Split views: https://developer.apple.com/design/human-interface-guidelines/split-views
- Tab views: https://developer.apple.com/design/human-interface-guidelines/tab-views
Menus and Actions
- Activity views: https://developer.apple.com/design/human-interface-guidelines/activity-views
- Buttons: https://developer.apple.com/design/human-interface-guidelines/buttons
- Context menus: https://developer.apple.com/design/human-interface-guidelines/context-menus
- Dock menus: https://developer.apple.com/design/human-interface-guidelines/dock-menus
- Edit menus: https://developer.apple.com/design/human-interface-guidelines/edit-menus
- Home Screen quick actions: https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions
- Menus: https://developer.apple.com/design/human-interface-guidelines/menus
- Ornaments: https://developer.apple.com/design/human-interface-guidelines/ornaments
- Pop-up buttons: https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons
- Pull-down buttons: https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons
- The menu bar: https://developer.apple.com/design/human-interface-guidelines/the-menu-bar
- Toolbars: https://developer.apple.com/design/human-interface-guidelines/toolbars
Navigation and Search
- Path controls: https://developer.apple.com/design/human-interface-guidelines/path-controls
- Search fields: https://developer.apple.com/design/human-interface-guidelines/search-fields
- Sidebars: https://developer.apple.com/design/human-interface-guidelines/sidebars
- Tab bars: https://developer.apple.com/design/human-interface-guidelines/tab-bars
- Token fields: https://developer.apple.com/design/human-interface-guidelines/token-fields
Presentation
- Action sheets: https://developer.apple.com/design/human-interface-guidelines/action-sheets
- Alerts: https://developer.apple.com/design/human-interface-guidelines/alerts
- Page controls: https://developer.apple.com/design/human-interface-guidelines/page-controls
- Panels: https://developer.apple.com/design/human-interface-guidelines/panels
- Popovers: https://developer.apple.com/design/human-interface-guidelines/popovers
- Scroll views: https://developer.apple.com/design/human-interface-guidelines/scroll-views
- Sheets: https://developer.apple.com/design/human-interface-guidelines/sheets
- Windows: https://developer.apple.com/design/human-interface-guidelines/windows
Selection and Input
- Color wells: https://developer.apple.com/design/human-interface-guidelines/color-wells
- Combo boxes: https://developer.apple.com/design/human-interface-guidelines/combo-boxes
- Digit entry views: https://developer.apple.com/design/human-interface-guidelines/digit-entry-views
- Image wells: https://developer.apple.com/design/human-interface-guidelines/image-wells
- Pickers: https://developer.apple.com/design/human-interface-guidelines/pickers
- Segmented controls: https://developer.apple.com/design/human-interface-guidelines/segmented-controls
- Sliders: https://developer.apple.com/design/human-interface-guidelines/sliders
- Steppers: https://developer.apple.com/design/human-interface-guidelines/steppers
- Text fields: https://developer.apple.com/design/human-interface-guidelines/text-fields
- Toggles: https://developer.apple.com/design/human-interface-guidelines/toggles
- Virtual keyboards: https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards
Status
- Activity rings: https://developer.apple.com/design/human-interface-guidelines/activity-rings
- Gauges: https://developer.apple.com/design/human-interface-guidelines/gauges
- Progress indicators: https://developer.apple.com/design/human-interface-guidelines/progress-indicators
- Rating indicators: https://developer.apple.com/design/human-interface-guidelines/rating-indicators
System Experiences
- App Shortcuts: https://developer.apple.com/design/human-interface-guidelines/app-shortcuts
- Complications: https://developer.apple.com/design/human-interface-guidelines/complications
- Controls: https://developer.apple.com/design/human-interface-guidelines/controls
- Live Activities: https://developer.apple.com/design/human-interface-guidelines/live-activities
- Notifications: https://developer.apple.com/design/human-interface-guidelines/notifications
- Snippets: https://developer.apple.com/design/human-interface-guidelines/snippets
- Status bars: https://developer.apple.com/design/human-interface-guidelines/status-bars
- Top Shelf: https://developer.apple.com/design/human-interface-guidelines/top-shelf
- Watch faces: https://developer.apple.com/design/human-interface-guidelines/watch-faces
- Widgets: https://developer.apple.com/design/human-interface-guidelines/widgets
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.
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
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.

