ss-feedback

Add loading, empty, error, and success states to data-driven UI components.

22|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill ss-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-feedback
Source: https://github.com/izzoa/polyrouter/tree/main/.agents/skills/ss-feedback
Command: npx skills add https://github.com/izzoa/polyrouter --skill ss-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn plain, data-driven components into polished user experiences by adding the right feedback states for loading, empty results, failures, and successful actions.

Core Features & Use Cases

  • Loading states: Add skeleton placeholders that match final layout and respect reduced-motion preferences.
  • Empty states: Show centered guidance when no data is available, including a clear next action.
  • Error states: Present plain-language failures with retry actions so partial and full-page errors are handled gracefully.
  • Success feedback: Use toasts for confirmations and undo support after user actions.
  • Use case: Ideal for dashboards, lists, cards, and forms that depend on async data or user-triggered updates.

Quick Start

Apply the ss-feedback skill to the target component file and implement loading, empty, error, and success states for each data-dependent area.

Frequently Asked Questions about ss-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add loading skeletons and empty states to async data components?

You add loading skeletons and empty states by applying layout-matched placeholders for loading and centered guidance with next actions for empty results, ensuring reduced-motion-safe animations throughout the interface.

What is the best way to handle error recovery in data-driven UI pages?

The best way to handle error recovery in data-driven UI pages is to present plain-language failure messages with retry actions, managing both partial and full-page errors gracefully so users can recover without leaving the page.

How do I show success feedback and undo support after user actions in a dashboard?

To show success feedback and undo support after user actions in a dashboard, use confirmation toasts that appear after asynchronous updates, allowing users to immediately react to or reverse their triggered actions.

Can I use toast notifications and skeleton loaders for forms that depend on async data?

Yes, you can use toast notifications and skeleton loaders for forms that depend on async data. This approach covers loading, empty, error, and success states specifically tailored for asynchronous interfaces and user-triggered updates.

Why do my loading states need to respect reduced-motion preferences?

Loading states need to respect reduced-motion preferences to ensure accessibility. Skeleton placeholders must be designed with reduced-motion-safe animations so users with motion sensitivities are not negatively impacted during data fetching.

Do I need existing layout components to implement matching skeleton placeholders?

Yes, you need existing layout components to implement matching skeleton placeholders. The feedback states require layout-matched placeholders, meaning your final UI structure must exist to generate accurate loading skeletons for the data-driven areas.