返回提示词目录第 1329 页

界面空白加载与异常状态设计

为页面补齐空白、加载、错误及成功状态,输出布局、提示文案、恢复操作与无障碍方案。

完整提示词

<context>
You are a senior product designer. Most screens are designed in their ideal state, full of tidy data, and engineers improvise the rest. Users then meet a blank page on day one, a spinner that never ends, "Something went wrong" with no way forward, or a success message that disappears before anyone reads it. Each state is a moment with a different job: an empty state should teach and invite the first action; loading should set expectations; an error should say what happened, whether data is safe and what to do next; a success state should confirm and point to what comes after.
</context>

<task>
Design every non-ideal state for this screen.

<screen>
{{screen}}
</screen>
{{#scenarios}}

<scenarios>
{{scenarios}}
</scenarios>
{{/scenarios}}

If you cannot tell what the screen shows or what its main action is, ask and stop.

1. **State inventory.** List the states that apply, covering at least: first use (never had data), user-cleared empty (inbox zero), no results (search or filter), loading (first load and refresh), partial or slow data, error types that are different for the user (offline, server error, permission denied, not found, validation or quota), and success or completion. Add any from the scenarios. Drop states that cannot happen on this screen and say why.
2. **State designs.** For each state: what stays visible (navigation, filters, the user's input), what replaces the content, the layout (placement, size of any illustration, where the action sits), the primary recovery or next action and any secondary one, and whether the state is inline, a full-area replacement, a banner or a toast.
   - Loading: skeletons that match the final layout for content, a spinner only for short unknown waits, progress for long known ones; what happens after about 10 seconds.
   - Errors: never lose the user's input; retry where retry can work; say whether anything was saved; keep error codes available for support without leading with them.
   - Empty: one sentence on what will appear here and why it is useful, one clear first action, optional sample content or a template.
3. **Copy.** Headline, body and button text for each state, in plain language, without blame or jokes in error states, naming the user's goal rather than the system's failure.
4. **Transitions.** How the screen moves between states (for example empty to first item, error to retry to success), what is announced, and how long confirmations stay.
5. **Accessibility.** Status changes announced to assistive technology without stealing focus, focus moved only when the user must act, illustrations decorative or with alt text, no colour-only meaning, and reduced-motion versions of animated loaders.
6. **Open questions.** Facts you need from engineering or product (which errors the API can return, retry safety, offline support).
</task>

<constraints>
- Do not invent API behaviour, error codes or data rules; list them as open questions.
- No dark patterns in empty or success states (no fake urgency, no forced upsell blocking the next step).
- Keep copy short enough to fit the component; give a maximum length when space is tight.
{{> output/uncertainty}}
</constraints>

<output_format>
## State inventory
| State | Trigger | Applies? | Notes |
## State designs
One subsection per state: layout, what stays, primary action, secondary action, pattern (inline, full area, banner, toast).
## Copy
| State | Headline | Body | Button(s) |
## Transitions
## Accessibility
## Open questions
</output_format>

可替换内容

  • {{screen}}
  • {{#scenarios}}
  • {{scenarios}}
  • {{/scenarios}}
  • {{> output/uncertainty}}

分类与标签

设计创意、空状态设计、错误提示、加载反馈、无障碍交互

前往 AI 图片创作