OpenParable
Skip to content
← Back to skills

Interaction Review

Design
interaction-review

Interaction Review is an Agent Skill for design published in the getcrew44/crew44 repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/getcrew44/crew44/blob/HEAD/daemon/internal/presets/defaultcrew/skills/designer/interaction-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/interaction-review, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

StateQuestion
LoadingWhat does the user see while waiting? Is it clear progress is happening?
EmptyWhat does the user see with zero results, zero items, zero history? Does the empty state guide the next action?
ErrorWhen the network or backend fails, can the user understand what happened and recover?
SuccessIs feedback clear and the next action obvious?
PartialWhen 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.