user-feedback-clarity

user-feedback-clarity is a skill for Claude Code, Codex from dylantarre/animation-principles. It costs 24 tokens per session (611 once invoked), scanned A, original, MIT.

A guide for making animated interface feedback easy to notice when an action is received, completed, or failed. It covers loading states, message duration, placement, contrast, motion, and combined visual cues.

In plain words
What is it for?
It is for designing clearer success, error, loading, and state-change feedback near the control that caused it.
Why use it?
It helps prevent repeated clicks and confusion when users cannot tell whether a form submission or other action worked.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for designing clearer success, error, loading, and state-change feedback near the control that caused it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dylantarre/animation-principles/user-feedback-clarity
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add dylantarre/animation-principles --skill user-feedback-clarity
Clone the repo
git clone --depth 1 https://github.com/dylantarre/animation-principles

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for user-feedback-clarity

README.md
[![agentmods](https://agentmods.dev/badge/skills/dylantarre/animation-principles/user-feedback-clarity/github.svg)](https://agentmods.dev/skills/dylantarre/animation-principles/user-feedback-clarity)
Your own site
<a href="https://agentmods.dev/skills/dylantarre/animation-principles/user-feedback-clarity"><img src="https://agentmods.dev/badge/skills/dylantarre/animation-principles/user-feedback-clarity/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for user-feedback-clarity

Your own site · 80×15
<a href="https://agentmods.dev/skills/dylantarre/animation-principles/user-feedback-clarity"><img src="https://agentmods.dev/badge/skills/dylantarre/animation-principles/user-feedback-clarity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 15 Feb 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00611
Opus 5 $0.00012 $0.00305
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00002 $0.00061

Measured 9d ago against content hash 737bc0e0414d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

user-feedback-clarity scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/12-by-problem-type/user-feedback-clarity/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Feedback Clarity

Make feedback animations unmissable using Disney's principles.

Problem Indicators

  • Users click multiple times (didn't see feedback)
  • "Did it work?" questions
  • Users miss success/error states
  • Form submission confusion
  • State changes go unnoticed

Diagnosis by Principle

Anticipation

Issue: No buildup before action completes Fix: Show loading/processing state immediately. User should know their input was received.

Follow Through

Issue: Feedback appears and vanishes too quickly Fix: Let feedback linger. Success messages need 2-3 seconds minimum. Add settle animation.

Staging

Issue: Feedback appears outside user's focus Fix: Show feedback near the trigger. If button was clicked, feedback should appear on/near button.

Exaggeration

Issue: Feedback is too subtle Fix: Increase contrast, size change, or motion. Feedback must compete with user's task focus.

Secondary Action

Issue: Only one feedback channel Fix: Combine channels: visual + motion + color. Error = red + shake. Success = green + checkmark + pulse.

Quick Fixes

  1. Immediate acknowledgment - Show something within 100ms
  2. Animate the trigger - Button should respond visibly
  3. Use color + motion together - Redundant signals
  4. Keep feedback in viewport - Near user's focus
  5. Add haptic feedback - On supported devices

Troubleshooting Checklist

  • Does feedback appear within 100ms of action?
  • Is feedback in user's current focus area?
  • Would feedback be noticed peripherally?
  • Are multiple senses engaged (visual, motion)?
  • Does feedback last long enough to read?
  • Is error feedback more prominent than success?
  • Test: Can users tell if action succeeded without reading text?
  • Test with users—ask "did that work?"

Code Pattern

/* Button feedback */
.button:active {
  transform: scale(0.95);
}

.button.loading {
  pointer-events: none;
}

.button.success {
  animation: successPulse 300ms ease-out;
}

@keyframes successPulse {
  0% { transform: scale(1); }
  50% { transform: scale(1.05); background: var(--success); }
  100% { transform: scale(1); }
}

/* Error shake */
@keyframes errorShake {
  0%, 100% { transform: translateX(0); }
  25% { transform: translateX(-4px); }
  75% { transform: translateX(4px); }
}

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 87 lines · 24 tokens per session scan A 737bc0e0414d

Subscribe to this mod's changes

user-feedback-clarity is a skill published in the GitHub repository dylantarre/animation-principles (81 stars, last pushed 8mo ago), licensed MIT. It adds 24 tokens to every session and 611 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

anthropics/claude-plugins-official · 40 tokens

visual-plan

Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.

BuilderIO/skills · 32 tokens

baseline-ui

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

ibelick/ui-skills · 34 tokens

antv-x6-editor

A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.

antvis/chart-visualization-skills · 253 tokens

infographic-creator

Create beautiful infographics based on given text content. Use when users request to create infographics.

antvis/chart-visualization-skills · 24 tokens

extract

Crawl an existing website (capped, multi-page) and seed stardust/current/ with PRODUCT.md, DESIGN.md, DESIGN.json, a per-page inventory, and the consolidated brand surface — the captured design system, palette, typography, motifs, and voice of the live site. Use when the user wants to analyze an existing site's…

adobe/skills · 188 tokens