agentleFS
Sign inStart free
Dragoon0xDragoon0x/taste-skills/skills/interaction/timing-feedback/SKILL.md

timing-feedback

Skill5 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every user action deserves acknowledgment.

    line 8
  2. Distinctive:

    MUST provide at least one feedback type for every user action

    line 26
  3. Distinctive:

    SHOULD mute the device and verify: can you still tell what's happening?

    line 27
  4. Distinctive:

    No feedback for destructive actions (delete, remove, disconnect)

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free