agentsclimarketplace

Timing feedback

Skill Dragoon0x/taste-skills/skills/interaction/timing-feedback

Agent skills for design taste and visual judgment. Hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design

Install
npx -y skills add Dragoon0x/taste-skills --skill timing-feedback

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.

SKILL.md

1.7 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.