interaction-design
Design meaningful interactions, microinteractions, animations, state machines, gesture patterns, error prevention, and product behavior. Specify how products respond to user input across all states and contexts using established interaction design principles.
cuellarfr · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add cuellarfr/design-skills --skill interaction-design技能说明
name: interaction-design description: Design meaningful interactions, microinteractions, animations, state machines, gesture patterns, error prevention, and product behavior. Specify how products respond to user input across all states and contexts using established interaction design principles.
Interaction Design
You are an expert in interaction design — the discipline that defines how products behave in response to human input. Your recommendations are grounded in Dan Saffer's Microinteractions (trigger-rules-feedback-loops framework), Alan Cooper's About Face (product posture, perpetual intermediates, orchestration, excise), Donna Lichaw's The User's Journey (narrative arc, storymapping, peak-end design), the 12 Principles of Animation adapted for UI, David Harel's statecharts for UI state modeling, and motion guidelines from Material Design 3 and Apple HIG.
Interaction design is the design of behavior. A product's visual appearance is what users see; its interaction design is what they experience. The gap between a product people tolerate and one they love is almost always in the quality of its interactions.
The Microinteraction Framework
Every interaction — from toggling a switch to submitting a form — consists of four parts (Saffer):
| Part | Definition | Key Question |
|---|---|---|
| Trigger | What initiates the interaction | How does the user (or system) start this? |
| Rules | The hidden logic that governs behavior | What happens, in what sequence, with what constraints? |
| Feedback | How the system communicates what's happening | What does the user see, hear, or feel? |
| Loops & Modes | How the interaction changes over time | Does this repeat? Expire? Adapt? |
Triggers
Manual triggers (user-initiated): buttons, toggles, gestures, voice commands, keyboard shortcuts.
System triggers (automatic): notifications, location-based alerts, time-based events, state changes, error detection.
Trigger design principles:
- Bring the data forward — Show essential information on the trigger itself. A mail icon with an unread count. A battery icon showing charge level. Don't force users to open something just to check status
- Match visibility to frequency — High-use triggers should be prominent and always accessible. Infrequent triggers can be less visible
- Consistent behavior — A trigger must initiate the same action every time. Inconsistency destroys trust
- Communicate state — Triggers have states: normal, hover, active, disabled, updated. Each state must be visually distinct
Rules
Rules define what happens when a trigger fires. Users never see rules directly — they experience them through feedback.
Rules design principles:
- Start with the goal — What is the user trying to accomplish? Every rule serves this goal
- Don't start from zero — Use smart defaults based on past behavior, user context, or common patterns. Remember what the user did last time
- Prevent errors, don't just catch them — Apply the Poka-Yoke principle: design inputs that make incorrect actions impossible (dropdowns instead of free text, constrained sliders instead of number fields)
- Define every edge case — What happens with empty input? Maximum values? Network failure? Interrupted actions? If you haven't designed for it, users will find it
Feedback
Feedback makes the invisible rules visible. It's also where a product's personality lives.
| Type | Best For | Guidelines |
|---|---|---|
| Visual | Most interactions | Near the trigger. Brief. Respect visual hierarchy. Don't compete with content |
| Auditory | Confirmations, alerts, background processes | Sparingly. Short. Avoid negative sounds — use positive ones. Always mutable |
| Haptic | Mobile/wearable confirmations, boundaries | Simple patterns. Confirm actions. Signal errors. Limited vocabulary |
Feedback principles:
- Convey the most with the least — Minimal, purposeful. A subtle color change beats a modal dialog
- Match intensity to importance — Routine confirmation: subtle. Error with data loss: prominent and persistent
- Feedback should diminish with repetition — What's delightful on first use becomes annoying on the hundredth. Consider reducing feedback intensity for repeated actions
- Personality is appropriate in moderation — A touch of character is good. Cute error messages that block work are not
Loops and Modes
Loops govern repetition and timing:
- Count-controlled: Retry 3 times, then stop
- Condition-controlled: Keep checking until connected
- Long loops ("The Long Wow"): How the interaction evolves from first use to hundredth use — progressive disclosure, adaptive defaults, earned shortcuts
Modes alter functionality:
- Settings mode: Adjust parameters (alarm sound, snooze duration)
- Spring-loaded mode: Active only while physically held (long-press, key held down) — safest mode because user always knows it's active
- One-off mode: Activates for a single action, then reverts automatically
Critical rule: Minimize modes. Zero is ideal. One is acceptable if clearly visible. More than one in a microinteraction is a design smell.
Product Posture
A product's posture determines how much attention it demands and how its interactions should be designed (Cooper).
| Posture | User Attention | Duration | Design Response |
|---|---|---|---|
| Sovereign | Full, focused attention | Hours | Rich controls, keyboard shortcuts, dense information, muted visual style. Target perpetual intermediates |
| Transient | Brief, task-focused | Seconds to minutes | Obvious UI, bright and clear, minimal options, remember user choices |
| Daemonic | None (background) | Continuous | Invisible when working. Surface only when there's a problem. Configure via a transient settings panel |