Index of every page on this site: llms.txt
All skills
Run it yourself

Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. Use when asked about: "gesture design", "Apple Pencil", "keyboard shortcuts", "game controller", "pointer support", "mouse support", "trackpad", "Digital Crown", "eye tracking", "visionOS input", "focus system", "remote control", "gyroscope", "spatial interaction". Also use when the user says "what gestures should I support," "how do I add keyboard shortcuts," "how does input work on Apple TV," "should I support Apple Pencil," or asks about input device handling. Cross-references: hig-components-status, hig-components-system, hig-technologies for VoiceOver and Siri.

Use this Skill: https://skilld.dev/gh/raintree-technology/hig-doctor/hig-inputs

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈209 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈6.4k more on demand in 13 files.

Description uses 10.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈836 characters, or 10.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Apple HIG: Inputs

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

  1. Support multiple input methods. Touch, pointer, keyboard, pencil, voice, eyes, hands, controllers. Design for the inputs available on each platform. On iPadOS, support both touch and pointer; on macOS, both pointer and keyboard.

  2. Consistent feedback for every input action. Visible, audible, or haptic response.

  3. Standard gestures must behave consistently. Tap to activate, swipe to scroll/navigate, pinch to zoom, long press for context menus, drag to move. Don't override system gestures (edge swipes for back, Home, notifications).

  4. Use standard recognizers; keep custom gestures discoverable. Apple's built-in recognizers handle edge cases and accessibility. If you add non-standard gestures, provide hints or coaching to teach them.

  5. Apple Pencil: precision drawing, markup, and selection. Support pressure, tilt, and hover. Distinguish finger from Pencil when appropriate (finger pans, Pencil draws).

  6. Support Scribble in text fields. Users expect to write with Pencil in any text input.

  7. Keyboard shortcuts and full navigation. Standard shortcuts (Cmd+C/V/Z) plus custom ones visible in the iPadOS Command key overlay. Logical tab order.

  8. Respect the software keyboard. Adjust layout when keyboard appears. Use keyboard-avoidance APIs.

  9. Game controllers: MFi controllers with on-screen fallbacks. Map to extended gamepad profile, sensible defaults, remappable. Always offer touch or keyboard alternatives.

  10. Pointer and trackpad: native feel. Hover effects, pointer shape adaptation, standard cursor behaviors. Two-finger scroll, pinch to zoom, swipe to navigate.

  11. Digital Crown: primary scrolling and value-adjustment input on watchOS. Scrolling lists, adjusting values, navigating views. Haptic feedback at detents.

  12. Eyes and spatial (visionOS): look and pinch. Generous hit targets (eye tracking is less precise than touch). Avoid sustained gaze for activation. Direct hand manipulation in immersive experiences.

  13. Focus system: critical for tvOS and visionOS. Predictable focus movement. Every interactive element focusable. Clear visual indicators (scale, highlight, elevation). Logical focus groups.

  14. Siri Remote: limited surface. Touch area for swiping, clickpad for selection, few physical buttons. Keep interactions simple.

  15. Gyroscope, accelerometer, UWB: use judiciously. Suits gaming, fitness, AR. Not for essential tasks. Provide calibration and reset. For UWB, communicate distance and direction with visual or haptic cues.

Reference Index

Reference Topic Key content
gestures.md Touch gestures Tap, swipe, pinch, long press, drag, system gestures
apple-pencil-and-scribble.md Apple Pencil Precision, pressure, tilt, hover, handwriting
keyboards.md Keyboards Shortcuts, navigation, software keyboard, Command key
game-controls.md Game controllers MFi, extended gamepad, remapping, fallbacks
pointing-devices.md Pointer/trackpad Hover, cursor morphing, trackpad gestures
digital-crown.md Digital Crown Scrolling, value adjustment, haptic detents
eyes.md Eye tracking Look and tap, gaze targeting, hit target sizing
spatial-interactions.md Spatial input Hand gestures, direct manipulation, immersive input
focus-and-selection.md Focus system tvOS/visionOS navigation, focus indicators, groups
remotes.md Remotes Touch surface, clickpad, simple interactions
gyro-and-accelerometer.md Motion sensors Gyroscope, accelerometer, calibration, gaming
nearby-interactions.md Nearby interactions U1 chip, directional finding, proximity triggers
camera-control.md Camera Control iPhone camera hardware button, quick launch

Output Format

  1. Input method recommendations by platform and how they interact.
  2. Gesture specification table -- standard and custom gestures with expected behaviors.
  3. Keyboard shortcut recommendations following system conventions.
  4. Accessibility input alternatives for VoiceOver, Switch Control, etc.

Questions to Ask

  1. Which platforms and input devices?
  2. Productivity or casual app?
  3. Custom gestures in the design?
  4. Game controller support needed?

Related Skills

  • hig-components-status -- Progress indicators responding to input (pull-to-refresh)
  • hig-components-system -- System experiences with unique input constraints
  • hig-technologies -- VoiceOver, Siri voice input, ARKit spatial gesture context

Built by Raintree Technology · More developer tools

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    No security risks identified. The skill consists exclusively of static markdown reference documentation for the Apple Human Interface Guidelines.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a0f1e4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 9 months ago
version
1.0.0

README badge

README badge for raintree-technology/hig-doctor/hig-inputs