Skill / UX
State continuity
Show loading, empty, partial, success, and failure states in the same product language.
Goal
Make each state feel like the same workflow instead of a bolt-on fallback.
Interaction and information-design checks for agent-facing product surfaces.
Checks
1Name the user action available in each state, especially empty and error states.
2Keep layout dimensions stable between loading, loaded, and empty states.
3Use progressive disclosure for diagnostics so the primary next step stays clear.
Avoid
1Generic empty states that describe the app instead of moving the workflow forward.
2Spinners or skeletons that resize the page when real content arrives.