feedback-patterns

feedback-patterns is a skill for Claude Code from Owl-Listener/designer-skills. It costs 48 tokens per session (443 once invoked), scanned A, original, MIT.

A guide to confirmations, status updates, and notifications that show people when an action was received or completed.

In plain words
What is it for?
Use it to design button responses, success messages, progress indicators, badges, banners, and other feedback.
Why use it?
It prevents uncertainty by making success, progress, changes, and next steps visible.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the interaction-design plugin — 22 skills, 5 commands shipped together

not rated 2.6krepo +94 3d ago A scan Socket: passSnyk: passSkillSpector: pass 48 tokens original MIT

Good fit Use it to design button responses, success messages, progress indicators, badges, banners, and other feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designer-skills/feedback-patterns
About the project

Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.

Owl-Listener/designer-skills · 2,572 stars · on GitHub

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 Owl-Listener/designer-skills --skill feedback-patterns
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designer-skills

Made for: Claude Code.

Or install interaction-design, the plugin that ships this one along with the rest of its 22 skills, 5 commands.

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 feedback-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designer-skills/feedback-patterns.svg)](https://agentmods.dev/skills/owl-listener/designer-skills/feedback-patterns)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/feedback-patterns"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/feedback-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 443 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 9 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 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.00048 $0.00443
Opus 5 $0.00024 $0.00221
Sonnet 5 $0.00010 $0.00089
Haiku 4.5 $0.00005 $0.00044

Measured 5d ago against content hash 1dda7d6b9990, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

feedback-patterns 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 5d 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.

interaction-design/skills/feedback-patterns/SKILL.md · 52 lines

What it actually says

Feedback Patterns

You are an expert in designing system feedback that keeps users informed and confident.

What You Do

You design feedback mechanisms that confirm actions, communicate status, and guide next steps.

Feedback Types

Immediate Feedback

  • Button state change on click
  • Inline validation on input
  • Toggle visual response
  • Drag position update

Confirmation Feedback

  • Success toast/snackbar after action
  • Checkmark animation on completion
  • Summary of what was done
  • Undo option for reversible actions

Status Feedback

  • Progress indicators for ongoing processes
  • Status badges (pending, active, complete)
  • Activity indicators (typing, uploading, syncing)
  • System health indicators

Notification Feedback

  • In-app notifications for events
  • Badge counts for unread items
  • Banner alerts for system-wide messages
  • Push notifications for time-sensitive items

Feedback Channels

  • Visual: Color change, icon, animation, badge
  • Text: Toast message, inline text, status label
  • Audio: Click sound, notification chime, alert tone
  • Haptic: Tap feedback, success vibration, warning buzz

Feedback Hierarchy

  1. Inline/contextual — closest to the action (preferred)
  2. Component-level — within the current component
  3. Page-level — banner or toast at page level
  4. System-level — notification outside current view

Duration and Dismissal

  • Toasts: auto-dismiss after 3-5 seconds
  • Errors: persist until resolved or dismissed
  • Confirmations: brief display with undo window
  • Status: persist while relevant

Best Practices

  • Acknowledge every user action
  • Match feedback intensity to action importance
  • Don't interrupt flow for minor confirmations
  • Provide undo rather than 'Are you sure?'
  • Ensure feedback is accessible (not color-only)
  • Test that feedback timing feels right
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. 5d ago First seen · 52 lines · 48 tokens per session scan A 1dda7d6b9990

Subscribe to this mod's changes

feedback-patterns is a skill published in the GitHub repository Owl-Listener/designer-skills (2,572 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 443 once invoked, about $0.0002 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

ui-review

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

LiHongwei-cn/lihongwei-cn · 26 tokens

design-system

Use this skill BEFORE writing or restyling ANY user-facing interface in WrongStack. It drives the Design Studio engine: commit to a kit, tune it (radius / density / font / motion), materialize the tokens into a real theme file, build against those tokens, then verify adherence. Trigger it whenever the user asks to…

WrongStack/WrongStack · 248 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

frontend-mockup-loop

Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…

BlackBeltTechnology/pi-agent-dashboard · 185 tokens

frontend-mockup-loop-dashboard

Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens