feedback-patterns
Feedback-Patterns provides a comprehensive framework for designing system feedback mechanisms that confirm user actions, communicate status updates, and deliver notifications across multiple channels. Use this skill when building confirmation toasts, status indicators, progress displays, validation messages, or any interface element that needs to keep users informed about action outcomes and system state changes.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/feedback-patterns && cp -r /tmp/feedback-patterns/interaction-design/skills/feedback-patterns ~/.claude/skills/feedback-patternsSKILL.md
# 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
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.