Back to Details

research-ui-prototyping

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Research UI Prototyping

研究UI原型设计

Research UIs are working tools, not landing pages. Favor dense, inspectable, task-focused interfaces that expose evidence and uncertainty.

研究UI是实用工具，而非着陆页。优先选择密集、可检查、以任务为核心的界面，展示证据与不确定性。

Read First

必读文档

```
references/repository-contract.md
```
```
references/output-contracts.md
```

```
references/repository-contract.md
```
```
references/output-contracts.md
```

When To Use

适用场景

dashboard for experiment metrics
source or paper browser
annotation or coding interface
SOTA matrix explorer
reproducibility report viewer
demo for a method or dataset

实验指标仪表板
文献或论文浏览器
标注或编码界面
SOTA矩阵探索器
可复现性报告查看器
方法或数据集演示

Design Rules

设计规则

Start with the core workflow, not a hero section.
Show identifiers, provenance, filters, and export controls.
Make uncertainty and missing evidence visible.
Prefer tables, facets, timelines, charts, and diff views over marketing cards.
Keep visual style restrained and domain-appropriate.
Use the existing
```
frontend-design
```
skill when available for polish and UI craft.
Verify with screenshots and interaction checks before claiming completion.

从核心工作流程入手，而非英雄板块。
展示标识符、来源、筛选器和导出控件。
清晰呈现不确定性和缺失的证据。
优先使用表格、分面、时间线、图表和差异视图，而非营销卡片。
保持视觉风格克制且符合领域需求。
若有现成的
```
frontend-design
```
技能，可用于优化UI细节。
在完成前通过截图和交互检查进行验证。

Data Rules

数据规则

Do not hardcode research results into the UI unless it is a static report.
Keep data loading paths documented.
Export tables/figures back to
```
outputs/
```
when they support the paper.

除非是静态报告，否则不要将研究结果硬编码到UI中。
记录数据加载路径。
当表格/图表用于支撑论文时，将其导出至
```
outputs/
```
目录。

Output

输出要求

Record UI purpose, run command, and data dependencies in

docs/agent/

or

docs/reproducibility/commands.md

.

在

docs/agent/

或

docs/reproducibility/commands.md

中记录UI用途、运行命令和数据依赖。