prototype

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Guide work through the right fidelity level with validation.

指导工作在合适的保真度层级下推进，并配套验证环节。

Read
```
workflows/prototyping.md
```
(5-level fidelity ladder, journey mapping template, usability-testing script, sample data).
Identify the current need and pick the lowest fidelity that answers it — never skip levels:
- Content-first (info needs) → Wireframe (layout/nav) → Low-fi (task completion) → High-fi (visual/a11y) → Code (feasibility/perf).
For flows: produce a user-journey map with decision points, error paths, and edge cases.
For validation: define the usability test (tasks, success criteria, 5-user rule) using the script.
High-fi/code steps pull tokens (
```
tokens/*
```
), components (
```
components/*
```
), taste (
```
taste/*
```
), and a11y (
```
accessibility/*
```
).

阅读
```
workflows/prototyping.md
```
（包含5级保真度阶梯、旅程地图模板、可用性测试脚本、示例数据）。
明确当前需求，选择能够满足需求的最低保真度层级——切勿跳级：
- 内容优先（信息需求）→ 线框图（布局/导航）→ 低保真（任务完成度）→ 高保真（视觉/a11y）→ 代码（可行性/性能）。
针对流程：产出包含决策点、错误路径和边界用例的用户旅程地图。
针对验证：使用脚本定义可用性测试（任务、成功标准、5用户法则）。
高保真/代码步骤会调用 tokens（
```
tokens/*
```
）、组件（
```
components/*
```
）、风格规范（
```
taste/*
```
）和 a11y 规范（
```
accessibility/*
```
）。

The artifact at the chosen fidelity + an explicit "what we validate next" plan.

所选保真度层级的产出物 + 明确的「下一步验证内容」计划。

The fidelity matches the question being answered — no level skipped.
Flows include decision points, error paths, and edge cases (empty/loading/overflow), not just the happy path.
A concrete validation step is named (tasks + success criteria), not "test later".
High-fi/code artifacts pass the same token + a11y bar as
```
design-code
```
(no hardcoded values, contrast, states).