Agent Skills
› Owl-Listener/designer-skills
› feedback-patterns
feedback-patterns
GitHub设计系统反馈机制，包括即时确认、状态更新和通知，确保用户感知操作结果。涵盖视觉、文本等渠道及层级规范。
Trigger Scenarios
需要设计成功提示或错误反馈
优化加载状态与进度指示
Install
npx skills add Owl-Listener/designer-skills --skill feedback-patterns -g -y
SKILL.md
Frontmatter
{
"name": "feedback-patterns",
"description": "Design confirmations, status updates, and notifications that tell users an action registered. Use when the system must acknowledge success or change. For waiting states use `loading-states`; for failures use `error-handling-ux`."
}
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
- Inline/contextual — closest to the action (preferred)
- Component-level — within the current component
- Page-level — banner or toast at page level
- 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
Version History
-
20e34c4
Current 2026-08-19 23:21
强化了技能描述的使用场景触发词和边界定义，解决了与其他技能（如颜色系统、无障碍审计）的重叠冲突，并规范了跨插件引用格式。
- acc3e57 2026-07-25 05:15
