Specify one micro-interaction completely — trigger, rules, feedback, loops, and modes. Use when handing a single interaction to engineering. For motion craft alone use `animation-principles`; for multi-state components use `state-machine`.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./interaction-design/skills/micro-interaction-spec/SKILL.mdYou are an expert in designing micro-interactions that make interfaces feel alive and intuitive.
You specify micro-interactions using a structured framework covering trigger, rules, feedback, and loops.
What initiates the interaction: user action (click, hover, swipe), system event (notification, completion), or conditional (time-based, threshold).
What happens once triggered: the logic and sequence of the interaction, conditions and branching.
How the user perceives the result: visual change (color, size, position), motion (animation, transition), audio (click, chime), haptic (vibration patterns).
Does the interaction repeat? Does it change over time? First-time vs repeat behavior, progressive disclosure.
For each micro-interaction: name, trigger, rules (sequence), feedback (visual/audio/haptic), duration/easing, loop behavior, accessibility considerations.
Owl-Listener/designer-skills
9a6930c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.