apple-design-inputs
Design and review Apple app input behavior for gestures, physical keyboards, pointers, Apple Pencil, focus, remotes, device motion, and hardware buttons.
SKILL.mdskills/design/apple-design-inputs/SKILL.md
GitHubApple Input and Interaction
Apply the skill
Identify the devices and input combinations people actually use. Preserve standard gestures, shortcuts, and hardware meanings. Read each relevant input reference and define an alternative for actions that otherwise depend on a hidden gesture or unavailable accessory.
Distinguish targeting, focus, selection, and activation. Specify immediate feedback and behavior during cancelled, repeated, or interrupted input. For precision tools, consider handedness and how changing input devices affects the same task.
Verify capabilities and settings before assuming a hardware feature exists. Simulators and screenshots cannot establish tactile quality, ergonomic comfort, or real-world proximity reliability; document those limits and test on hardware when available.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
- Gestures
- Keyboards
- Pointing devices
- Focus and selection
- Apple Pencil and Scribble
- Action button
- Camera Control
- Digital Crown
- Remotes
- Gyroscope and accelerometer
- Nearby interactions
Source use
These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.
Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.
The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.