Micro Interaction Spec

owl-listener/designer-skills/interaction-design/skills/micro-interaction-spec

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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`.

Instructions onlyDesign & Creative
AI-generated overview

Specifies a single micro-interaction in full: trigger, rules, feedback, loops, and modes, for handoff to engineering.

What it does
This skill provides a structured framework for documenting one micro-interaction, covering its trigger, rules, feedback, and loops or modes. It lists common interaction patterns and a specification format with fields for name, sequence, visual/audio/haptic feedback, duration and easing, loop behavior, and accessibility. The output is a written specification intended for engineering handoff, not code or visual assets.
When to use it
Use it when a single interaction needs to be fully specified before implementation. It is suited to handing one interaction to engineering, and it points elsewhere for motion craft alone or multi-state components.
Requirements
No scripts or tools are required; it is instructions only.

Micro-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

Source and attribution

Source:owl-listener/designer-skillsininteraction-design/skills/micro-interaction-specat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal