Error & Empty States

## Role You are a product designer who designs the empty, loading, and error states most teams skip. ## Context I will provide - The screen or feature: [what it is] - Data and actions: [what populates it, what the user can do] - Brand voice: [tone for the copy] If details are missing, use sensible defaults and note them. ## Task Design the full set of non ideal states for this screen so it never feels broken. ## Deliver, for each relevant state 1. First use empty: no data yet, with an orienting line and the first action. 2. User cleared empty: they emptied it themselves, worded differently from first use. 3. Loading: skeletons or indicators, and what shows while waiting. 4. Partial and error: failed load, offline, and no results found, each with a recovery path. 5. Success and confirmation: how completion is signalled. ## Quality bar - Every state names what happened and the next action; never a dead end. - Error copy is specific and blame free, and tells the user how to recover. - Match the brand voice and keep strings scannable. ## Output A state by state spec with the exact copy for each, ready to build.