All skills

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

This session only. Nothing lands on disk.

referenceseyes.md

≈617 tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- hig-doctor:attribution -->

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/eyes. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

Eyes

Best practices

Always give people multiple ways to interact with your app.

Design for visual comfort.

Place content at a comfortable viewing distance.

Prefer using standard UI components.

Making items easy to see

Minimize visual distractions.

Make it easy for people to look at an item by providing enough space around it.

Avoid using a repeating pattern or texture that fills the field of view.

Encouraging interaction

Consider using subtle visual cues to encourage people to look at the item they’re most likely to want.

In general, give an interactive item a rounded shape.

If you create an interactive component that consists of more than one element, be sure to provide an overall containing shape that visionOS can highlight.

Custom hover effects

Prefer using a custom hover effect to emphasize or enhance a special moment in your experience.

Choose the right delay.

  • No delay (default). A custom hover effect that appears without delay tends to be especially useful when the effect is subtle or invites interaction, like when a knob appears on a slider.

  • Short delay. Consider using a short delay to let people look at an element and quickly interact with it without waiting for the effect to appear; for example, the expansion of tabs in a tab bar works this way.

  • Long delay. If your custom hover effect shows additional information, like when a tooltip appears below a button, a slightly longer delay can work well because most people won’t need to view the additional information every time.

Aim to keep one or more of the element’s primary views unchanged in both states of a custom hover effect.

Thoroughly test custom hover effects.


<!-- hig-doctor:canonical-footer -->

For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/eyes

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

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

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub 4 weeks ago.

Activeupdated 7 months ago
version
1.0.0

README badge

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