feedback-and-status
Design feedback and status communication that works across senses — visual, auditory, and haptic. Use when designing loading states, success messages, progress indicators, notifications, alerts, or any system response to user action. Triggers on: feedback, status, notification, alert, loading, progress, success message, confirmation, toast, snackbar, screen reader announcement, aria-live, colour alone.
- Installs
- 76
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill feedback-and-status- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads feedback-and-status automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Feedback and Status Design
Design system feedback that reaches every user — regardless of whether they can see the screen, hear audio, or feel vibration. No single sense should be the only channel.
Core Principle
Never communicate status through one sense alone. What happens if the user can't see it? Can't hear it? Can't feel it?
The Multi-Channel Rule
Every piece of feedback should work through at least two channels:
| Feedback type | Visual | Text | Sound | Haptic |
|---|---|---|---|---|
| Success | Green tick | "Saved successfully" | Confirmation tone | Short vibration |
| Error | Red highlight | Specific error message | Alert tone | Double vibration |
| Loading | Spinner/bar | "Loading..." | None (silence) | None |
| Warning | Yellow banner | Warning text | Optional tone | Optional vibration |
Screen readers are a critical third channel — all visual feedback must be announced to assistive technology.
Design Patterns
Don't Rely on Colour Alone
- Red/green is invisible to 8% of men with colour vision deficiency
- Always combine colour with: icon, text label, pattern, or position
- Error states: red + error icon + text description
- Success states: green + tick icon + text confirmation
- Test: does this still communicate the same thing in greyscale?
Immediate Feedback
- Button press: visual change within 100ms (pressed state)
- Form submission: loading indicator within 1 second
- Completion: success message within 2 seconds of finishing
- Error: highlight the specific field, not just a banner at the top
Persistent vs. Transient Feedback
- Transient (toast/snackbar): only for non-critical confirmations. Show for at least 5 seconds. Include a way to review missed messages.
- Persistent (inline): for errors, warnings, and anything the user needs to act on. Never auto-dismiss error messages.
- Screen reader users miss transient messages — use aria-live="polite" for non-urgent updates, aria-live="assertive" for critical alerts.
Progress Communication
- Determinate progress (known duration): show percentage or step count
- Indeterminate progress (unknown duration): show spinner with text like "Loading your results..."
- Long processes (over 10 seconds): add estimated time remaining
- Very long processes: allow background processing with notification on completion
Status Without Vision
- All status changes must be announced to screen readers
- Use aria-live regions for dynamic content updates
- Don't rely on visual position alone to convey status (e.g., a moved item in a kanban board needs a text announcement)
- Error messages must be programmatically associated with their field (aria-describedby)
Assessment Questions
- Is colour ever the only indicator of status?
- Can a screen reader user perceive every status change?
- Are error messages persistent until resolved?
- Do transient messages display long enough to be read?
- Does every user action produce perceivable feedback?
FAQ
What does the feedback-and-status skill do?
Design feedback and status communication that works across senses — visual, auditory, and haptic. Use when designing loading states, success messages, progress indicators, notifications, alerts, or any system response to user action. Triggers on: feedback, status, notification, alert, loading, progress, success message, confirmation, toast, snackbar, screen reader announcement, aria-live, colour alone.
How do I install feedback-and-status?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill feedback-and-status in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/feedback-and-status/ (personal) or .claude/skills/feedback-and-status/ (project).
Which AI agents can use feedback-and-status?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is feedback-and-status safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains feedback-and-status?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 76 recorded installs.
More from owl-listener/inclusive-design-skills
keyboard-navigation
owl-listener/inclusive-design-skills
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Use when designing any interactive interface — forms, menus, modals, tabs, carousels, drag-and-drop, data tables, or custom components. Triggers on: keyboard, focus, tab order, focus trap, skip link, arrow keys, keyboard shortcut, can't use mouse, motor disability, switch access, focus indicator, focus ring.
plain-language-design
owl-listener/inclusive-design-skills
Write and review content for plain language accessibility. Use when writing interface copy, error messages, instructions, onboarding text, help content, legal or medical information, forms, or any user-facing text. Triggers on: plain language, reading level, simplify text, jargon, hard to understand, nobody reads this, unclear copy, rewrite, too complicated, ESL, literacy, readability.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Review responsive and flexible layout for accessibility across devices, zoom levels, and orientations. Chains: responsive-accessibility, flexible-typography, information-density. Use when testing an existing interface across screen sizes and zoom levels for accessibility.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.