show-me-artifact

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Publish the report as one artifact page the user reads in a browser, instead of a long chat message or a local HTML file. It needs Claude's

Artifact

tool. Without it, write one focused HTML file with

/show-me

instead.

将报告发布为一个 artifact 页面，供用户在浏览器中阅读，而不是冗长的聊天消息或本地 HTML 文件。该页面需要 Claude 的

Artifact

工具。如果没有该工具，则改为编写一个聚焦的 HTML 文件，并使用

/show-me

。

Flow

流程

Load
/show-me
for its views and principles, and publish them as one artifact page in place of the local HTML file it opens.
Make one page per report or decision set. When the user asks about a different subject, start a new page instead of adding a section. Open with what the reader needs first: where things stand and how many decisions wait on them. Then pick a view per point:
- progress as a meter with a checkpoint list, each checkpoint marked done, running or waiting;
- the state of many items as a tree grouped by status, each leaf with a one-line reason;
- runs, options or versions side by side as a table;
- each open decision as a decision card.
Put on the page only what helps the reader understand or decide, and link to a file for the detail behind a point.
Write each decision card so the reader can decide from the card alone, without opening a file or scrolling back: what is being decided, why it matters, the evidence as the smallest visual that makes the point, the options, and the recommended one marked. Give each card a short id (
```
D1
```
,
```
D2
```
) and each option a letter (A, B, C), so the reader can answer in one line, such as "D3: B".
Build the page and publish it with the
```
Artifact
```
tool. Give the user the link with one line on what the page holds.
- When the page will change, such as a report updated at each checkpoint: keep the content in a data file (
```
data.json
```
  ) and the page in a generator (
```
build.py
```
  ) that turns it into HTML, both in the project's
```
.scratch/
```
  , since the session's scratchpad is deleted with the session and a later session must rebuild from them. Load
```
artifact-design
```
  before writing
```
build.py
```
  , so every rebuild carries its theming and phone-width rules. Make every change in
```
data.json
```
  or
```
build.py
```
  , since a rebuild overwrites the HTML, and republish from the same file path, so the link the user already has shows the new version.
- When work is handed over or a pull request links the page, write the page's URL and where its data file is there. A later session reads the page with the
```
Artifact
```
  tool's
```
read
```
  action on that URL, then rebuilds and publishes with
```
url
```
  set to it, instead of making a new page.
When the user answers a card, act on the answer, then mark that card decided on the page at the next republish, so the page never asks again what is settled.
- When the answer is a page comment, read it with the
```
ArtifactComments
```
  tool and treat it like an answer in chat.

**加载
```
/show-me
```
以获取其视图和原则，**并将它们发布为一个 artifact 页面，以替代它打开的本地 HTML 文件。
**每份报告或每组决策单独创建一个页面。**当用户询问不同主题时，新建页面，而不是添加章节。页面开头先呈现读者最需要的信息：当前进展如何，以及有多少决策正等待他们处理。然后为每个要点选择一种视图：
- 以进度条呈现进展，并附上检查点列表；每个检查点标记为已完成、进行中或等待中；
- 以按状态分组的树形结构呈现多个项目的状态，每个叶节点附上一行原因说明；
- 将各次运行、选项或版本并排放在表格中；
- 每项未决事项使用一个决策卡片。
页面上只放置有助于读者理解或决策的内容，并链接到相应文件，以查看某个要点背后的详细信息。
**编写每个决策卡片，使读者无需打开文件或回看即可仅凭卡片作出决定：**正在决定什么、为什么重要、以能够说明要点的最小可视化形式呈现证据、选项，以及标出推荐项。为每张卡片设置简短 id（
```
D1
```
、
```
D2
```
），为每个选项设置字母（A、B、C），这样读者只需用一行回答，例如 "D3: B"。
**使用
```
Artifact
```
工具构建并发布页面。**向用户提供链接，并用一行说明页面包含的内容。
- 当页面会发生变化时，例如报告在每个检查点更新：将内容保存在数据文件（
```
data.json
```
  ）中，并将页面保存在生成器（
```
build.py
```
  ）中，由生成器将其转换为 HTML；两者均置于项目的
```
.scratch/
```
  目录中，因为会话的 scratchpad 会随会话一同删除，而后续会话必须基于它们重新构建。编写
```
build.py
```
  前先加载
```
artifact-design
```
  ，这样每次重新构建都会沿用其主题样式和手机宽度规则。所有修改都应在
```
data.json
```
  或
```
build.py
```
  中进行，因为重新构建会覆盖 HTML；从相同的文件路径重新发布，让用户已有的链接显示新版本。
- **当工作需要交接，或某个 pull request 链接到该页面时，**在交接说明或 pull request 中写明页面的 URL 及其数据文件所在位置。后续会话使用
```
Artifact
```
  工具的
```
read
```
  操作读取该 URL 指向的页面，然后重新构建，并在发布时将
```
url
```
  设置为该 URL，而不是新建页面。
**当用户回答某个卡片时，**根据回答执行相应操作，然后在下一次重新发布时将该卡片在页面上标记为已决定，这样页面不会再次询问已经确定的事项。
- **当回答是页面评论时，**使用
```
ArtifactComments
```
  工具读取，并像处理聊天中的回答一样处理。