Feedback And Status logo

Feedback And Status

Community
Owl-Listener
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.

Overview

PublisherOwl-Listener
Repositoryinclusive-design-skills
Skill namefeedback-and-status
Stars
108
Forks
28
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Feedback And Status AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/feedback-and-status
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/inclusive-interaction/skills/feedback-and-status .claude/skills/feedback-and-status
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Feedback And Status in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Feedback And Status on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Feedback And Status is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 typeVisualTextSoundHaptic
SuccessGreen tick"Saved successfully"Confirmation toneShort vibration
ErrorRed highlightSpecific error messageAlert toneDouble vibration
LoadingSpinner/bar"Loading..."None (silence)None
WarningYellow bannerWarning textOptional toneOptional 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

  1. Is colour ever the only indicator of status?
  2. Can a screen reader user perceive every status change?
  3. Are error messages persistent until resolved?
  4. Do transient messages display long enough to be read?
  5. Does every user action produce perceivable feedback?

Frequently asked questions

What does the Feedback And Status AI 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.

Why use Feedback And Status on TypingMind?

Because you install it once and use it with any model. Feedback And Status is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Feedback And Status in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/feedback-and-status. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Feedback And Status?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Feedback And Status?

As many as you like. As long as a model supports skills, you can use Feedback And Status with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Feedback And Status AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇