Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Design every non-happy state for the UI at the target the user described. Load the ui-craft skill and read references/state-design.md.

Step 1 — Inventory. List every data source and interactive surface in the target. For each, enumerate its states:

Surface	idle	loading	empty	error	partial	conflict	offline

Mark each cell as designed (exists in code), missing (must add), or N/A (not applicable — e.g., a read-only view has no conflict state).

Step 2 — Fill the missing states. For each missing state, either stub it inline or add a follow-up task comment. Use references/state-design.md for:

Skeleton sizing (match final layout, 200ms delay, 5s upper bound)
Empty-state copy (why empty + next action + visual)
Error-state contract (specific cause + one-click recovery + support ID)
Offline handling (queue writes + reconcile on reconnect)

unhappy