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.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- 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
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
- Distinctive: line 8
Use this skill to decide how an experience should adapt to each Apple platform before selecting lower-level components or patterns.
- Distinctive: line 15
Ask which platforms are first-class and which are adaptations.
- Distinctive: line 16
If the user names no platform, choose the primary usage context from the product: phone, tablet, desktop, TV, spatial, watch, or game.
- Distinctive: line 18
Start from platform intent, not screen size.
- Distinctive: line 28
Keep the same core model, terminology, and task outcomes across platforms.
- Distinctive: line 30
Do not ship one scaled layout across all devices.
- Very specific: line 33
Use apple-hig-foundations for accessibility, layout, color, materials, motion, typography, privacy, writing, and related primitives.
- Very specific: line 34
Use apple-hig-patterns for user flows such as onboarding, search, settings, loading, notifications, or file management.
- Very specific: line 35
Use apple-hig-components for controls, navigation, presentation surfaces, status UI, and system experiences.
- Very specific: line 36
Use apple-hig-inputs for touch, pointer, keyboard, focus, gaze, remote, game controller, and sensor input.
- Very specific: line 37
Use apple-hig-technologies for Apple Pay, Siri, Wallet, CarPlay, HealthKit, SharePlay, iCloud, and other Apple technology integrations.
- Distinctive: line 39
Verify with platform evidence.
- Distinctive: line 42
If exact current wording, new platform behavior, or OS-version support matters, reopen the official HIG page before finalizing.
- Distinctive: line 47
Prefer direct manipulation, familiar system conventions, and immediate feedback.
- Distinctive: line 49
Keep visual hierarchy calm.
≈ “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 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
- 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.
- 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.
- 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.
- Choose the next HIG skill.
- Use
apple-hig-foundationsfor accessibility, layout, color, materials, motion, typography, privacy, writing, and related primitives. - Use
apple-hig-patternsfor user flows such as onboarding, search, settings, loading, notifications, or file management. - Use
apple-hig-componentsfor controls, navigation, presentation surfaces, status UI, and system experiences. - Use
apple-hig-inputsfor touch, pointer, keyboard, focus, gaze, remote, game controller, and sensor input. - Use
apple-hig-technologiesfor Apple Pay, Siri, Wallet, CarPlay, HealthKit, SharePlay, iCloud, and other Apple technology integrations.
- Use
- 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:
- Design principles: https://developer.apple.com/design/human-interface-guidelines/design-principles
- Designing for iOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-ios
- Designing for iPadOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados
- Designing for macOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-macos
- Designing for tvOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos
- Designing for visionOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos
- Designing for watchOS: https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos
- Designing for games: https://developer.apple.com/design/human-interface-guidelines/designing-for-games
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.
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.

