Skip to content
Back to skills

Interaction Review

ASecurity

Use to evaluate or design a user interaction flow — states, edge cases, microinteractions, motion, and feedback patterns.

  • 359 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 6, 2026
ai-agentsgospringbackendperformance

Works with

  • cli

Security analysis

A100/100

Scanned June 6, 2026

npx -y skills add getcrew44/crew44 --skill interaction-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Interaction Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Interaction Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/getcrew44-interaction-review/badge)](https://www.skillsdirectory.com/skills/getcrew44-interaction-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: interaction-review
description: Use to evaluate or design a user interaction flow — states, edge cases, microinteractions, motion, and feedback patterns.
---

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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.