agentleFS
inttegrointtegro/labor/skills/apple-hig-inputs/SKILL.md

apple-hig-inputs

Skill1 starsChanged 4 days agoMITView on GitHub

Apple Human Interface Guidelines input guidance for touch, gestures, keyboard, pointer, focus, eye input, Apple Pencil and Scribble, Camera Control, Digital Crown, game controls, sensors, nearby interactions, remotes, and related platform input systems. Use when designing, reviewing, or implementing Apple-platform input behavior or accessible alternatives.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to design interaction behavior around the ways people control Apple devices.

    line 8
  2. Distinctive:

    Never make a task depend on only one input path when the platform commonly supports alternatives.

    line 16
  3. Distinctive:

    Keep feedback immediate and continuous during direct manipulation.

    line 26
  4. Distinctive:

    Use adjacent skills deliberately.

    line 29
  5. Very specific:

    Use fluid-interface-design for gesture physics, velocity handoff, interruptibility, rubber-banding, springs, and reduced motion.

    line 30
  6. Very specific:

    Use apple-hig-components for controls that expose the input behavior.

    line 31
  7. Distinctive:

    Every primary task works with the platform's expected input methods.

    line 67

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Apple HIG Inputs

Use this skill to design interaction behavior around the ways people control Apple devices. Source baseline reviewed against the official Apple Developer HIG on 2026-11-09.

Source: https://developer.apple.com/design/human-interface-guidelines/inputs

Workflow

  1. Identify available inputs and required fallbacks.
    • Touch, pointer, keyboard, remote, focus, eyes, hand gestures, Pencil, controller, crown, sensors, and camera hardware can coexist.
    • Never make a task depend on only one input path when the platform commonly supports alternatives.
  2. Match the input to the task.
    • Direct manipulation: touch, gestures, Pencil, eyes/hands in spatial contexts.
    • Precision or productivity: keyboard, pointer, shortcuts, text input, selection, focus.
    • Lean-back navigation: focus engine, remotes, game controllers.
    • Personal/ambient control: Digital Crown, sensors, nearby interactions.
  3. Design for stateful feedback.
    • Show hover, focus, press, drag, selected, disabled, error, and active states.
    • Keep feedback immediate and continuous during direct manipulation.
    • Preserve target stability so focus, pointer, and touch do not fight layout changes.
  4. Use adjacent skills deliberately.
    • Use fluid-interface-design for gesture physics, velocity handoff, interruptibility, rubber-banding, springs, and reduced motion.
    • Use apple-hig-components for controls that expose the input behavior.
  5. Refresh official HIG pages when exact hardware behavior or new OS support matters.

Input Rules

  • Touch targets need enough space, stable hit regions, and immediate response.
  • Gestures need discoverability, cancellation, conflict resolution, and non-gesture alternatives.
  • Pointer interactions need hover affordances, precision, and keyboard parity.
  • Keyboard support needs visible focus, logical order, shortcuts only where useful, and no hidden keyboard traps.
  • Focus-based interfaces need predictable movement, clear current focus, and layouts that support directional navigation.
  • Eye and spatial input need comfort, clear targets, low fatigue, and confirmation for risky actions.
  • Pencil and Scribble should support precision and creativity without blocking touch or keyboard workflows.
  • Remotes and game controls need minimal text entry, clear focus, and quick recovery from misnavigation.
  • Sensor-based input must be optional, privacy-aware, and robust to motion, orientation, and environment changes.

Topic Map

Official HIG pages currently under Inputs:

Review Checklist

  • Every primary task works with the platform's expected input methods.
  • Focus, hover, press, drag, selected, disabled, and error states are visible.
  • Gesture and hardware shortcuts have accessible alternatives.
  • Input conflict, cancellation, recovery, and interruption behavior are defined.
  • Motion and feedback respect Reduce Motion, assistive technology, and fatigue.

Attribution

Apple, Apple Pencil, and related product names are trademarks of Apple Inc. This independently written skill is not affiliated with or endorsed by Apple.

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.