Enhance UI with Robust Feedback States

UX Feedback is part of StyleSeed and ensures data-dependent UI does not stop at the happy path, adding the four core feedback states every serious product needs: loading, empty, error, and success. For Loading, it uses skeletons that match the final layout, avoids spinners inside cards unless the pattern genuinely requires them, and delays skeletons slightly to avoid flashes on fast responses. For Empty, it provides a friendly explanation and a next action, so zero values render meaningfully instead of the section just disappearing. For Error, it uses plain-language failure messages, always offers recovery where possible, and localizes failures to the affected card or section if the rest of the page can still work. For Success, it uses toasts or an equivalent lightweight confirmation for completed actions, adding undo for reversible destructive changes.

Use it when a component or page fetches, mutates, or depends on async data, when a flow currently renders only the success path, when a card, list, or page needs better state communication, or when the product needs clearer recovery and confirmation behavior. It's specifically about state coverage for data-dependent UI, not general visual design or copy tone (those are separate StyleSeed skills).

Output is: the data-dependent areas identified in the target, the loading/empty/error/success states added for each one, any reusable empty-state or toast patterns created along the way, and follow-up work flagged for analytics, retries, or accessibility that falls outside this skill's scope. Best practices baked in: match loading placeholders to the real layout rather than a generic spinner, keep partial failures isolated to the affected section whenever possible instead of failing the whole page, make recovery actions visible in the UI rather than hidden in logs or dev tools, and use success feedback sparingly but clearly so it doesn't become noise.

Built for the StyleSeed design system's Toss seed (bitjaru/styleseed), and complements other StyleSeed skills covering UI review, accessibility, and copy tone - this one is scoped specifically to the presence and quality of the four data states.

Frontend developers building async, data-dependent UI in a StyleSeed Toss-based codebase who need to systematically cover loading/empty/error/success states rather than shipping only the happy path and discovering gaps in production.