mcpField
T
timing-feedback

timing-feedback

github.com/dragoon0xDesign & UI677 installsUpdated 35w ago
Repository

About timing-feedback

timing-feedback is an interaction-design skill for matching response timing and feedback to user actions. It defines timing bands, feedback types, and patterns to avoid.

Key features

  1. 01Four response-time bands
  2. 02Visual, spatial, and informational feedback
  3. 03Feedback for every user action
  4. 04Guidance for long operations
  5. 05Interaction anti-pattern checks

Use cases

  1. 01Specify feedback for interface actions
  2. 02Choose timing for page changes and searches
  3. 03Design progress feedback for long tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dragoon0x/taste-skills --skill timing-feedback

After installing, type/timing-feedbackin Claude Code to confirm it loaded.

Details

From the project README

Timing & Feedback

Every user action deserves acknowledgment. The question is what kind and how fast.

How to use

  • /timing-feedback Apply timing and feedback constraints to interaction design in this conversation.

Constraints

Timing Scale
  • Instant (< 100ms): Direct manipulation. Button presses, toggles, drags. Any delay here feels broken.
  • Fast (100-300ms): Page changes, panel opens, filter applications. Most UI animation lives here.
  • Deliberate (300ms-1s): Complex operations. Loading a view, running a search. User accepts the wait because the action feels significant.
  • Patient (> 1s): Needs explicit feedback. Progress indicator, skeleton, status message. Silence here feels like failure.
Feedback Types
  • Visual: Color change, animation, state shift. Minimum viable feedback.
  • Spatial: Element movement, expansion, collapse. Communicates where something went.
  • Informational: Text confirmation, count update, status change. Communicates what happened.
  • MUST provide at least one feedback type for every user action
  • SHOULD mute the device and verify: can you still tell what's happening?
Anti-Patterns
  • Identical response timing for all actions regardless of significance
  • No feedback for destructive actions (delete, remove, disconnect)
  • Spinners where skeletons would preserve spatial context
  • Feedback animations that outlast the actual operation

Comments

Markdown supported