Back to Details

to-artifact

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
The deliverable is an Artifact, published in the house style.
Load 
artifact-design
and 
humanize
before designing, and 
dataviz
before writing any chart. references/design.md carries the house style: the voice, the type and color it is built from, the stylesheet that sets them, and the reflexes it leaves out. Every word of page copy follows 
humanize
.
交付物为符合品牌统一风格的Artifact。
设计前需加载
artifact-design
和
humanize
，编写任何图表前需加载
dataviz
。references/design.md 包含品牌统一风格规范：语气、所用字体与配色、定义这些样式的样式表，以及需要摒弃的惯性设计。页面文案的每一个字都需遵循
humanize
规范。

1. Fix the subject

1. 确定主题

Take the subject from the first source that has one: what the invocation names; the subject under discussion this session; a PR or issue related to the current task. If every source is empty, ask.
Done when the subject is one written line and the material it rests on is in hand.
从首个包含主题的信息源中提取主题：调用名称、本次会话讨论的主题、与当前任务相关的PR或issue。若所有信息源均为空，需向用户询问。
当主题可整理为一行文字，且支撑主题的素材已准备齐全时，本步骤完成。

2. Frame the reader's job

2. 明确读者需求

Inspect all available material before designing. Privately establish:
  • Who opens this, in what context, to decide or understand what?
  • What is the strongest supported answer?
  • What evidence makes that answer credible?
  • What tradeoff, uncertainty, or limit changes its interpretation?
  • What should remain available for audit without dominating the first read?
Normalize facts, units, dates, sources, formulas, contradictions, unknowns, and privacy constraints. Distinguish observation, derivation, projection, recommendation, and causation. Never invent intent, ownership, urgency, certainty, deadlines, approvals, future behavior, or confidentiality.
Order by reader need rather than source order, and support two reading speeds: an executive path where title, headings, decisive values, captions, and conclusion carry the argument quickly, and an audit path where exact tables, assumptions, methodology, caveats, and sources preserve the record.
Done when the argument is written down — the reader's question, the strongest supported answer, and the evidence that makes that answer credible — every section answers a reader question no other section answers, and every claim has one evidence home: a later table may preserve exact lookup, but no second summary, chart, or conclusion restates the same answer at equal prominence.
设计前需检查所有可用素材，私下明确以下几点：
  • 谁会打开这份内容？在什么场景下？想要决策或理解什么内容？
  • 最有依据的核心答案是什么？
  • 哪些证据能支撑该答案的可信度？
  • 哪些权衡、不确定性或限制会影响对答案的解读？
  • 哪些内容需要保留以供审计，但不应在首次阅读时占据主要篇幅？
统一事实、单位、日期、来源、公式、矛盾点、未知项和隐私约束。区分观察结果、推导结论、预测内容、建议方案和因果关系。绝不可虚构意图、归属权、紧迫性、确定性、截止日期、审批情况、未来行为或保密要求。
内容需按读者需求排序，而非按信息源顺序排列，同时支持两种阅读节奏：高管速读路径（通过标题、小标题、关键决策值、图注和结论快速传递核心论点），以及审计详读路径（通过精确表格、假设前提、方法论、注意事项和信息源保留完整记录）。
当核心论点（即读者的问题、最有依据的答案，以及支撑答案可信度的证据）整理完成，且每个章节都回答了其他章节未覆盖的读者问题，每个论断都有唯一的证据归属时，本步骤完成：后续表格可保留精确的查询数据，但不应有第二个摘要、图表或结论以同等重要性重复表述同一答案。

3. Build and check

3. 构建与校验

Let the argument choose the structure. The first viewport is the argument rather than a masthead and setup; past that, compose whatever the material warrants. Take type, color, and voice from references/design.md, publish assets/style.css beside the page as it sets out, and ship none of the reflexes it lists.
Render the published page and read it in both themes and at narrow width:
  1. First read: would a reader who saw only the first viewport remember the central relationship, decision, or tool rather than the title or mood?
  2. Restraint: can any surface, border, pill, icon, label, color, paragraph, or section go without losing meaning, affordance, or rhythm? If yes, remove it.
  3. Themes and reflow: do light and dark carry equivalent hierarchy and contrast, and does the page recompose without overflow or character-level wrapping?
Fix the highest-impact defect, render again, and repeat.
Done when the page is published with the stylesheet beside it, a render clears all three checks, and the user holds the page itself: this review stays internal, so deliver no score, process diary, or self-critique.
让核心论点决定页面结构。首屏应展示核心论点，而非页眉和说明内容；首屏之后，可根据素材需求灵活组织内容。字体、配色和语气需遵循references/design.md的规范，页面发布时需将assets/style.css放在页面同级目录下，且不得使用规范中列出的任何惯性设计。
渲染已发布的页面，在两种主题下和窄屏宽度下进行阅读检查：
  1. 首次阅读效果：仅看过首屏的读者是否能记住核心关系、决策或工具，而非只记住标题或氛围？
  2. 精简性：是否有任何表面、边框、胶囊按钮、图标、标签、颜色、段落或章节可以移除，且不影响含义、可供性或节奏？如果是，就移除它。
  3. 主题与重排：浅色和深色模式下的层级与对比度是否一致？页面重排时是否不会出现溢出或字符级换行？
修复影响最大的缺陷，重新渲染，重复此过程。
当页面已发布且样式表位于同级目录，渲染结果通过全部三项检查，且用户可直接访问页面时，本步骤完成：此评审为内部流程，因此无需交付评分、过程日志或自我批评内容。