agentleFS
CarlosZieglerCarlosZiegler/zietec-skills/skills/design/apple-design-inputs/SKILL.md

apple-design-inputs

Skill1 starsChanged 51 days agoMITView on GitHub

Design and review Apple app input behavior for gestures, physical keyboards, pointers, Apple Pencil, focus, remotes, device motion, and hardware buttons.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify capabilities and settings before assuming a hardware feature exists.

    line 14

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

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.