agentleFS
raintree-technologyraintree-technology/hig-doctor/skills/hig-inputs/SKILL.md

hig-inputs

Skill153 starsChanged 9 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for .claude/apple-design-context.md before asking questions.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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: 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

ReferenceTopicKey content
gestures.mdTouch gesturesTap, swipe, pinch, long press, drag, system gestures
apple-pencil-and-scribble.mdApple PencilPrecision, pressure, tilt, hover, handwriting
keyboards.mdKeyboardsShortcuts, navigation, software keyboard, Command key
game-controls.mdGame controllersMFi, extended gamepad, remapping, fallbacks
pointing-devices.mdPointer/trackpadHover, cursor morphing, trackpad gestures
digital-crown.mdDigital CrownScrolling, value adjustment, haptic detents
eyes.mdEye trackingLook and tap, gaze targeting, hit target sizing
spatial-interactions.mdSpatial inputHand gestures, direct manipulation, immersive input
focus-and-selection.mdFocus systemtvOS/visionOS navigation, focus indicators, groups
remotes.mdRemotesTouch surface, clickpad, simple interactions
gyro-and-accelerometer.mdMotion sensorsGyroscope, accelerometer, calibration, gaming
nearby-interactions.mdNearby interactionsU1 chip, directional finding, proximity triggers
camera-control.mdCamera ControliPhone 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

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.