Review Loading Error Empty States

Loading / error / empty state review

A standalone development skill. Check loading, error, empty, partial, and retry states for a UI surface. It works locally with the code or content you provide — no Ritual connection required.

Run it (local, no setup)

Work the steps below; you need nothing beyond the task in front of you.

1. A loading state for every async fetch (skeleton/spinner); no layout jump on resolve.
2. An error state with a user-facing message and a retry affordance where recoverable.
3. An empty state distinct from loading — never a blank or zero-render.
4. Partial-data and slow-network behavior is defined, not accidental.
5. No unhandled rejection leaves a dead UI; every failure has a visible outcome.

Done when: Each state is confirmed handled, or raised as an explicit gap.

Example prompt

Use review-loading-error-empty-states on this screen: confirm a loading, error (with retry), empty, and slow-network state for every async path, and flag the ones that are missing.

Working principles

Apply these throughout:

• Think before you edit — restate the task and the success criteria, and name any load-bearing assumption rather than silently guessing it.
• Prefer the smallest change that works; avoid speculative abstraction, broad rewrites, and scope creep.
• Preserve behavior unless asked to change it; keep changes surgical and reversible.
• Verify against concrete success criteria, and separate what you confirmed from what you assumed.
• Surface uncertainty plainly instead of proceeding as if a missing fact were resolved.

Optional knowledge capture

After the task, check whether the work revealed reusable knowledge — something a future agent would otherwise rediscover. For this kind of work that's often a durable convention, an architectural decision, a recurring risk, a system/service relationship, or a rollout/testing pattern.

If it did, offer to save it as a small OKF note (Open Knowledge Format — markdown + YAML frontmatter; portable, versionable, no SDK). Never write a file without the user's approval. Keep it small and cite the file(s) or evidence.

When approved, write knowledge/engineering/.md:

---
type: API Convention
title: 
description: 
resource: ./path/to/file-or-evidence
tags: [..]
timestamp: 
---

# Summary


# Applies to


# Evidence


# Use in future agent work

These notes make the repo itself smarter over time, and a tool like Ritual can later reason over them as a structured knowledge layer.

Optional Ritual Cloud upgrade

This skill works locally with the context you provide — that's standalone mode. Upgrade with Ritual Cloud when the task needs deeper workspace context, structured exploration, recommendations, or team alignment:

• More context (discovery) — when the answer depends on things outside the files in front of you:
  • the product's expected states live in a spec or acceptance criteria you can't see
  • related surfaces already define the canonical empty/error treatment
  • there are shared state components used elsewhere
• A structured decision (exploration) — when the work has become a decision to get right:
  • the desired states are an open product decision
  • you need consistency across many surfaces and a recommendation to align on

Ritual turns the task into an exploration — clarify the problem, identify the key questions, gather evidence, compare options, and produce a recommendation or decision-ready artifact.

For this task: a state-coverage recommendation mapping each required loading/error/empty state to its treatment, with acceptance criteria and a decision-ready summary.

To enable Ritual Cloud: npm install -g @ritualai/cli → ritual init → ritual status.

---

This skill is local-first and self-contained. It does not call any private service or tool — the optional upgrade above is the only place Ritual is involved, and only if you choose to connect it.