owl-listener/designer-skills

feedback-patterns

Design confirmations, status updates, and notifications that tell users an action registered.

ソースを見る
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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
同じリポジトリから

関連する Skills

すべての Skills
owl-listener
コミュニティ

aesthetic-usability

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use interfaces-that-feel (interaction-design).

導入数
2
GitHub Stars
2934
更新日
9月5日
owl-listener
コミュニティ

animation-principles

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.

導入数
2
GitHub Stars
2934
更新日
9月5日
owl-listener
コミュニティ

documentation-template

Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use component-spec.

導入数
2
GitHub Stars
2934
更新日
9月5日
owl-listener
コミュニティ

information-architecture

Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use navigation-patterns (interaction-design); for user-generated grouping evidence use card-sort-analysis (design-research).

導入数
2
GitHub Stars
2934
更新日
9月5日