interaction-and-motion
Skill0 starsChanged 3 months agoMITView on GitHub
Design purposeful interaction feedback and motion that clarify cause, state, continuity, and control.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessible-interfaceSkill
- color-and-contrastSkill
- design-contextSkill
- design-system-auditSkill
- forms-and-validationSkill
- interface-critiqueSkill
- layout-and-spacingSkill
- loading-empty-error-statesSkill
- responsive-designSkill
- typographySkill
- visual-hierarchySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 8
Use interaction feedback and motion to explain what changed, preserve spatial continuity, and make controls feel responsive.
- Distinctive: line 12
Do not animate merely to appear polished.
- Distinctive: line 30
Verify on constrained devices and with keyboard, touch, pointer, zoom, and reduced motion.
≈ “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.
Files
Interaction and Motion
Use interaction feedback and motion to explain what changed, preserve spatial continuity, and make controls feel responsive. Apply this to transitions, microinteractions, gestures, direct manipulation, and state feedback.
Do not animate merely to appear polished. Do not delay essential actions, animate large regions without purpose, or make motion the only state signal.
Workflow
- Describe the trigger, user intent, state change, and information the response must communicate.
- Choose the least motion that clarifies cause and effect. Immediate feedback often matters more than a transition.
- Define origin, destination, property, duration, easing, interruption, reversal, repeat behavior, and final state. Prefer compositor-friendly properties when implementing.
- Preserve input control. Handle rapid repeated actions, cancellation, navigation, async completion, and state changes during animation.
- Pair motion with persistent visual and semantic state. Ensure focus and assistive-technology updates follow the actual interaction.
- Respect reduced-motion preferences with a meaningful alternative, not simply a slower version. Avoid flashing and motion likely to cause vestibular harm.
- Verify on constrained devices and with keyboard, touch, pointer, zoom, and reduced motion.
Output
Return an interaction specification with trigger, states, feedback purpose, timing rationale, interruption behavior, reduced-motion alternative, and test conditions.
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.