Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getcrew44/interaction-review
Use to evaluate or design a user interaction flow — states, edge cases, microinteractions, motion, and feedback patterns.
Passed 18 of 22 test cases with the skill, and 16 of 22 without it.
2 fixed16 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just finished designing the checkout flow for our web application. Could you audit the interaction design? Please check if we're missing any UI states, look for unhandled edge cases like network glitches or extreme input lengths, review our transitions to catch unnecessary animations, and summarize any usability gaps alongside high-impact recommendations.
| Checked | Without skill | With skill |
|---|---|---|
| Recommends 100–150 ms timing for micro-feedback. | Passed | Passed |
| Recommends 200–300 ms timing for small transitions. | Missed | Passed |
| Lists state coverage gaps accompanied by user-visible consequences. | Passed | Passed |
The instructions your model reads when the skill loads.
Make sure every state a user can land in has been considered, and that motion serves the user rather than decorating.
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? |
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:
Prefer spring or ease-out for entrances, ease-in for exits, transform/opacity for performance. Honor prefers-reduced-motion.
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.