ss-feedback

Implements loading, empty, error, and success feedback states in React components.

Updated May 26, 2026
One-click install
npx skills add https://github.com/rmethodm/resumegen --skill ss-feedback-rmethodm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-feedback
Source: https://github.com/rmethodm/resumegen/tree/main/.agents/skills/ss-feedback
Command: npx skills add https://github.com/rmethodm/resumegen --skill ss-feedback-rmethodm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Components that fetch or mutate data often ship without proper feedback states, leaving users staring at blank screens, sudden layout jumps, or silent failures. This Skill audits a target file and adds all four essential UX states—loading skeleton, empty state, error state, and success toast—following a consistent design language. ## Core Features & Use Cases - Skeleton Loading States: Generates layout-matched skeletons with animate-pulse, 300ms delay/minimum display rules, and prefers-reduced-motion support. - Empty, Error, and Success States: Adds centered empty states with next-action prompts, partial/full error states with retry buttons, and toast notifications with undo for destructive actions. - Use Case: You have a dashboard card that fetches user activity. Run this Skill on the file to get a DataCardSkeleton, DataCardEmpty, DataCardError with retry, and toast confirmations wired into a clean conditional rendering pattern. ## Quick Start Ask the AI to add loading, empty, error, and success feedback states to a specific component file such as src/components/ActivityCard.tsx.

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 to a React component?▼

Create a skeleton variant that mirrors the final layout's dimensions using placeholder divs with animate-pulse. Delay its display by 300ms and keep it visible for at least 300ms to avoid flashing on fast loads.

What UX states should a data-driven component have?▼

A data-driven component needs four states: loading (skeleton matching final layout), empty (icon, message, and next action), error (plain-language message with retry button), and success (toast confirmation, with undo for destructive actions).

Should I use spinners or skeletons for loading states?▼

Use skeletons shaped like the final content inside cards rather than spinners. Skeletons preserve layout stability and set accurate expectations, while spinners cause layout shifts and give no sense of incoming structure.

How do I handle partial data loading failures in a dashboard?▼

Show the error state only in the affected card while the rest of the dashboard loads normally. Reserve full-screen error states with retry for complete page failures, and always include a retry action.

When should I not use this feedback states Skill?▼

Skip it when you only need copywriting for state text, accessibility fixes on existing states, or brand-new component creation—those belong to dedicated copy, accessibility, and component-generation skills. It also excludes analytics or error-logging plumbing.