Hig Inputs

Organization

raintree-technology

hig-inputs

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.

Overview

Publisher	raintree-technology
Repository	`hig-doctor`
Skill name	`hig-inputs`
Stars	148
Forks	10
Bundled files	13
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
13 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by raintree-technology on GitHub. Read the source before you install it.

Installation

Install the Hig Inputs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-inputs
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/raintree-technology/hig-doctor.git /tmp/hig-doctor
mkdir -p .claude/skills
cp -r /tmp/hig-doctor/skills/hig-inputs .claude/skills/hig-inputs

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hig Inputs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hig Inputs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hig Inputs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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.
Consistent feedback for every input action. Visible, audible, or haptic response.
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).
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.
Apple Pencil: precision drawing, markup, and selection. Support pressure, tilt, and hover. Distinguish finger from Pencil when appropriate (finger pans, Pencil draws).
Support Scribble in text fields. Users expect to write with Pencil in any text input.
Keyboard shortcuts and full navigation. Standard shortcuts (Cmd+C/V/Z) plus custom ones visible in the iPadOS Command key overlay. Logical tab order.
Respect the software keyboard. Adjust layout when keyboard appears. Use keyboard-avoidance APIs.
Game controllers: MFi controllers with on-screen fallbacks. Map to extended gamepad profile, sensible defaults, remappable. Always offer touch or keyboard alternatives.
Pointer and trackpad: native feel. Hover effects, pointer shape adaptation, standard cursor behaviors. Two-finger scroll, pinch to zoom, swipe to navigate.
Digital Crown: primary scrolling and value-adjustment input on watchOS. Scrolling lists, adjusting values, navigating views. Haptic feedback at detents.
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.
Focus system: critical for tvOS and visionOS. Predictable focus movement. Every interactive element focusable. Clear visual indicators (scale, highlight, elevation). Logical focus groups.
Siri Remote: limited surface. Touch area for swiping, clickpad for selection, few physical buttons. Keep interactions simple.
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

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

Questions to Ask

Which platforms and input devices?
Productivity or casual app?
Custom gestures in the design?
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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Hig Inputs AI skill do?

Why use Hig Inputs on TypingMind?

Because you install it once and use it with any model. Hig Inputs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hig Inputs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-inputs. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hig Inputs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hig Inputs?

As many as you like. As long as a model supports skills, you can use Hig Inputs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hig Inputs AI skill free?

Yes. It is published on GitHub by raintree-technology under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Apple HIG: Inputs

Key Principles

Reference Index

Output Format

Questions to Ask

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now