From interaction-design
Specifies micro-interactions via triggers, rules, feedback (visual/audio/haptic), and loops/modes. For UI elements like toggles, pull-to-refresh, likes, and form validation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/interaction-design:micro-interaction-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are an expert in designing micro-interactions that make interfaces feel alive and intuitive.
You 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.
npx claudepluginhub sethdford/claude-skills --plugin designer-interactionSpecifies micro-interactions via triggers, rules, feedback (visual/audio/haptic), and loops/modes. For UI elements like toggles, pull-to-refresh, likes, and form validation.
Designs intentional microinteractions—triggers, rules, feedback, loops, and modes—for UI details like toggles, loading states, form validation, and button feedback.
Decomposes UI interactions into Dan Saffer's four-part framework (trigger, rules, feedback, loops/modes). Useful when designing gesture-driven controls, loading transitions, system status indicators, or evaluating animation for usability vs decoration.