apple-design-interaction
Skill18 starsChanged 6 months agoLicence not identifiedView on GitHub
Use when deciding HOW an Apple-style interface should BEHAVE — the functional UX/interaction logic, not the looks. Navigation-model decisions (push vs sheet vs modal vs tab vs popover vs split-view vs full-screen, back behavior, deep-linking, state restoration), state & feedback behavior (loading/skeleton timing, empty/error/disabled states, optimistic UI, pull-to-refresh, pagination), perceived-performance rules (latency thresholds, instant feedback, prefetch, progressive loading), input/focus/keyboard/pointer handling + hit-target affordances, and scroll-as-input decisions (when cinematic scroll helps vs hurts, scroll affordance, momentum, inertia, scroll-jacking prohibition, scroll-driven UX decision). Part of the apple-design family. Keywords: navigation model, push pop, sheet vs modal, tab bar, back behavior, deep link, state restoration, loading state, skeleton, empty state, optimistic UI, pull to refresh, perceived performance, latency threshold, prefetch, focus order, keyboard navigation, hit target, affordance, pointer vs touch, scroll as input, scroll affordance, momentum, inertia, scroll-jacking, when cinematic scroll, scroll-driven UX decision.
In this repository8 other files it gives its agents.
- apple-design-backendSkill
- apple-design-foundationsSkill
- apple-design-materialsSkill
- apple-design-motionSkill
- apple-design-osSkill
- apple-designSkill
- apple-design-tacticsSkill
- apple-design-webSkill
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.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.

