interaction-review
Use to evaluate or design a user interaction flow — states, edge cases, microinteractions, motion, and feedback patterns.
适合你，如果正在设计或审查用户操作流程
npx oh-my-skill add getcrew44/crew44/interaction-reviewcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- getcrew44/crew44/interaction-reviewnpx oh-my-skill verify getcrew44/crew44/interaction-review怎么用
商店整理自技能原文 · 版本 cfcf1e7 · 表述以原文为准装上后，Claude 会帮你评估或设计用户交互流程——它会逐个检查每个界面状态（加载、空、错误、成功、部分），找出边缘情况，并评价动效是否真的有用（而不是花哨装饰）。最后给出具体改进建议。
当你要求评估某个交互流程、检查状态覆盖、找出边缘情况或讨论动效原则时触发。
技能原文 SKILL.md
Interaction Review
Make sure every state a user can land in has been considered, and that motion serves the user rather than decorating.
State coverage map
For each user-facing surface, walk through:
| State | Question | |-------|----------| | Loading | What does the user see while waiting? Is it clear progress is happening? | | Empty | What does the user see with zero results, zero items, zero history? Does the empty state guide the next action? | | Error | When the network or backend fails, can the user understand what happened and recover? | | Success | Is feedback clear and the next action obvious? | | Partial | When the operation half-succeeded, is the partial result accurately reported? |
Edge cases to test
- 47-character name. 200-character name. Empty name.
- Zero results. One result. Ten thousand results.
- First-time user. Power user with their own muscle memory.
- Slow connection. Offline. Back button mid-action. Double-click on a critical button.
Motion principles
Motion should communicate, not decorate. Every animation answers one of: confirm an action occurred, orient where things came from or go to, focus attention on a change, or preserve context during a transition. If it does none of these, cut it.
Use a timing scale:
- 100–150 ms: micro-feedback (hovers, clicks)
- 200–300 ms: small transitions (toggles, dropdowns)
- 300–500 ms: medium transitions (modals, page changes)
- 500 ms+: complex choreography only
Prefer spring or ease-out for entrances, ease-in for exits, transform/opacity for performance. Honor prefers-reduced-motion.
Microinteraction checklist
- Buttons: hover, press, focus, disabled, loading — each visually distinct, none flicker.
- Inputs: default, focus, error, disabled, success — clear path back from error.
- Toggles and switches: state change is visible at a glance, not just a color shift.
- Drag, swipe, scroll-triggered: discoverable, reversible, non-blocking.
Output
- Specific gaps in state coverage, with the user-visible consequence.
- Specific edge cases not handled.
- Motion that decorates rather than communicates.
- Recommendations sized by impact, not effort.