Skip to content
cccskills
FreePublished on GitHub

loading-empty-error-states

Design the three states every data UI forgets. Use for any component that fetches or lists data.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md830 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Loading / Empty / Error States

AI-built UIs handle the happy path and crash on the other three. Design all four:

  • Loading — skeletons that match the final layout (not a centered spinner that shifts everything).
  • Empty — a real first-run state: what it is, and the one action to fill it. Not a blank box.
  • Error — what failed, in human terms, plus a retry. Never a raw stack trace or silent nothing.
  • Partial — slow/streaming data, optimistic updates that can roll back. For each fetch in the diff, confirm all four exist. The empty and error states are where products feel broken.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.

The English summary is being prepared. Showing the original description.

Archive228/loopkit755Updated Jul 15, 2026

See all skills by Archive228

Report a problem with this skill