Feedback Patterns
- 944 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
feedback-patterns is a Claude Code skill that designs multi-channel UI feedback—confirmations, status updates, and notifications—for developers who need users to stay informed and confident after every action.
About
feedback-patterns is a design-system skill from owl-listener/designer-skills that structures how interfaces confirm user actions and communicate state. The skill catalogs immediate feedback (button state changes, inline validation, toggle responses, drag updates), confirmation feedback (success toasts, checkmark animations, action summaries, undo for reversible operations), and status feedback for ongoing processes. Developers reach for feedback-patterns when building forms, dashboards, or mobile flows where silent actions create confusion or support tickets. The skill frames feedback as a consistent system—not one-off alerts—so confirmations, errors, and progress cues align across channels. Use it during component design or UX review when an agent or team needs concrete patterns instead of generic “add a toast” advice.
- Designs four distinct feedback types: Immediate, Confirmation, Status, and Notification
- Defines four feedback channels: Visual, Text, Audio, and Haptic
- Enforces a 4-level Feedback Hierarchy prioritizing inline/contextual responses
- Produces reusable feedback pattern specifications for buttons, forms, toasts, and banners
- Guides next-skill handoff to implementation after pattern approval
Feedback Patterns by the numbers
- 944 all-time installs (skills.sh)
- +42 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #439 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill feedback-patternsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 944 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you design consistent UI action feedback?
Generate consistent, multi-channel feedback patterns that confirm user actions and reduce confusion in interactive interfaces.
Who is it for?
Frontend developers and designers standardizing confirmations, validation, and status messaging across a product surface.
Skip if: Teams that only need a single alert component with no broader feedback system or accessibility review.
When should I use this skill?
The user asks for toast/snackbar patterns, inline validation feedback, undo after actions, or multi-channel status communication in UI.
What you get
A feedback pattern spec covering immediate, confirmation, and status channels with concrete UI examples.
- feedback pattern specification
- multi-channel confirmation guidelines
Files
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
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kHow it compares
Choose feedback-patterns when you need a full feedback taxonomy; use component-specific skills when you only need one widget implementation.
FAQ
What feedback types does feedback-patterns cover?
feedback-patterns covers immediate feedback (button state, inline validation, toggles, drag), confirmation feedback (toasts, checkmarks, summaries, undo), and status feedback for ongoing operations. Each type targets a distinct moment in the user action lifecycle.
When should developers use feedback-patterns?
Developers should use feedback-patterns when building interactive flows where users need clear confirmation after actions, real-time validation, or progress status. The skill prevents inconsistent alerts and silent failures across forms and dashboards.
Is Feedback Patterns safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.