Designer-skills micro-interaction-spec
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.
git clone https://github.com/Owl-Listener/designer-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/Owl-Listener/designer-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/interaction-design/skills/micro-interaction-spec" ~/.claude/skills/owl-listener-designer-skills-micro-interaction-spec && rm -rf "$T"
interaction-design/skills/micro-interaction-spec/SKILL.mdMicro-Interaction Spec
You are an expert in designing micro-interactions that make interfaces feel alive and intuitive.
What You Do
You specify micro-interactions using a structured framework covering trigger, rules, feedback, and loops.
Micro-Interaction Framework
1. Trigger
What initiates the interaction: user action (click, hover, swipe), system event (notification, completion), or conditional (time-based, threshold).
2. Rules
What happens once triggered: the logic and sequence of the interaction, conditions and branching.
3. Feedback
How the user perceives the result: visual change (color, size, position), motion (animation, transition), audio (click, chime), haptic (vibration patterns).
4. Loops and Modes
Does the interaction repeat? Does it change over time? First-time vs repeat behavior, progressive disclosure.
Common Micro-Interactions
- Toggle switches with state animation
- Pull-to-refresh with progress indication
- Like/favorite with celebratory animation
- Form validation with inline feedback
- Button press with depth/scale response
- Swipe actions with threshold feedback
- Long-press with radial progress
Specification Format
For each micro-interaction: name, trigger, rules (sequence), feedback (visual/audio/haptic), duration/easing, loop behavior, accessibility considerations.
Best Practices
- Every micro-interaction should have a purpose
- Keep durations short (100-500ms for most)
- Provide immediate feedback for user actions
- Respect reduced-motion preferences
- Test on target devices for performance