store-screenshots-panorama

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Store screenshots — panorama

商店截图——全景图

Makes App Store sets from raw app screenshots that read as one surface. The layout was measured from a large marketplace app's set; the 3D objects and the hero come from the app's own content. Details are in

references/style.md

. Read that file end to end before the first set: the decisions the template doesn't make (colours, curves, which part comes forward, which symbols become 3D, the Duo layout) come from there.

The user wants the result, not the process. Don't write plan, spec or measurement files, and don't stop for approval. Make the decisions yourself, produce the sets, check them, deliver. Ask only when an input is really missing and there is no sensible default — for example, ask for larger originals if the raw screenshots are narrower than 1206px.

基于原始 App 截图制作 App Store 截图集，使其看起来像同一个连贯界面。布局参数来自对一个大型商城类 App 截图集的测量；3D 物体和 hero 则来自 App 自身的内容。细节见

references/style.md

。在制作第一组截图前务必从头到尾读完该文件：模板未涵盖的决策（颜色、曲线、哪些部分前移、哪些符号转为 3D、Duo 布局）均以该文件为准。

用户需要的是结果，而不是过程。不要编写计划、规范或测量文件，也不要停下来等待审批。自行作出决策、生成截图集、检查并交付。仅当确实缺少输入且没有合理默认值时才询问——例如，当原始截图宽度不足 1206px 时，要求提供更高分辨率的原图。

Core rules

核心规则

The UI stays pixel-exact. Raw screenshots and crops of them are plain image layers. Don't redraw, regenerate with AI, translate, or change any text on the screen. Cards are only cropped from the raw file with
```
data-crop
```
. A store screenshot has to show the real app; an invented UI costs both trust and App Review.
Each device is shown with its own raw screenshots. On iPhone Duo the tab bar and status bar sit on the side, and split views open on the inner display. Putting an iPhone screenshot in a Duo frame shows the app as something it isn't; don't. If there are no Duo screenshots, make the iPhone sets and tell the user what to capture for Duo (
```
style.md
```
§10).
Dimming is a separate layer. The only thing applied to the screen is the
```
.phone.dim
```
layer; the pixels don't change.
Decoration comes from context. The 3D objects repeat the app's subject. Don't borrow campaign badges, ribbons, discount language, or random plus signs and hearts from shopping sets; they make every app look like a store ad.
AI or 3D generation is only for objects and the hero symbol, never with a phone or UI in it.
Unverified hardware is not drawn. The Duo frame has no camera, hinge or buttons; their positions are not verified.
No other brands' logos or names.
Superiority claims ("the best", "number 1") only with a source. Without one, write a benefit, not a claim.
The status bar stays as it is in the raw screenshot.

UI 保持像素级一致。 原始截图及其裁切图仅作为普通图像图层。不要重绘、使用 AI 重新生成、翻译或修改屏幕上的任何文字。卡片只能通过
```
data-crop
```
从原始文件中裁切。商店截图必须展示真实 App；虚构 UI 既会损害用户信任，也会给 App Review 带来风险。
每台设备都应使用其对应的原始截图展示。 在 iPhone Duo 上，标签栏和状态栏位于侧边，分屏视图在内屏上打开。将 iPhone 截图放入 Duo 框架会让 App 呈现为并非其真实形态的样式，因此不要这样做。如果没有 Duo 截图，则制作 iPhone 截图集，并告知用户需要采集哪些 Duo 截图（
```
style.md
```
§10）。
变暗处理是独立图层。 屏幕中唯一应用的图层是
```
.phone.dim
```
；像素本身不会发生变化。
装饰元素来自 App 语境。 3D 物体应呼应 App 的主题。不要照搬商城类截图集中的活动徽章、绶带、折扣文案，或随意添加加号和爱心；这些元素会让每个 App 都看起来像商店广告。
AI 或 3D 生成仅用于物体和 hero 标志，绝不能用于生成包含手机或 UI 的图像。
不得绘制未经核实的硬件结构。 Duo 框架不包含摄像头、铰链或按键，因为其位置尚未得到验证。
不得出现其他品牌的 logo 或名称。
最高级声明（“最佳”“排名第一”）必须附有来源。没有来源时，应表述为益处，而不是最高级声明。
状态栏保持原始截图中的状态。

Inputs and defaults

输入与默认值

Input	Default
iPhone raw screenshots	`raw/` (1206×2622 or larger), shown in both themes. Or `raw-light/` and `raw-dark/` : the app in light and in dark mode, same file names and sizes; each theme then shows its own ( `style.md` §9).
Duo raw screenshots	`raw-duo-outer/` (outer display) and `raw-duo-inner/` (inner display), same order and file names; per appearance `raw-duo-outer-light/` , `raw-duo-outer-dark/` and so on. Without them, no Duo sets are made.
Output folder	`out/`
Device sets	iPhone 6.9" (1320×2868) and 6.3" (1206×2622): both are needed ( `style.md` §4). With Duo screenshots, Duo outer (1398×2034) and inner (2007×2853).
Language	The raw screenshots' language. Headlines are written per language; crops are measured from that language's screenshots.
Theme	`both` : light and dark. If the user names one, make only that.
Colours	Derived from the raw screenshots ( `style.md` §1, §9)
Messages and 3D symbols	You derive them from the raw screenshots ( `style.md` §6, §8)

Output:

<out>/<lang>/<theme>/<device>/01.png … NN.png

. Theme is

light

dark

; device is

iphone-6.9

iphone-6.3

duo-outer

duo-inner

. The source HTML files and previews stay in

<out>/.src/

; don't delete them, so the user can change the copy and render again. If the output folder already holds another set's files, don't touch them; if anything would clash, pick a new subfolder and say so.

输入	默认值
iPhone 原始截图	`raw/` （1206×2622 或更大），同时以两种主题展示。或者使用 `raw-light/` 和 `raw-dark/` ：分别存放浅色和深色模式下的 App，文件名和尺寸相同；之后每个主题各自展示对应截图（ `style.md` §9）。
Duo 原始截图	`raw-duo-outer/` （外屏）和 `raw-duo-inner/` （内屏），顺序和文件名相同；每种外观分别使用 `raw-duo-outer-light/` 、 `raw-duo-outer-dark/` 等目录。如果没有这些截图，则不制作 Duo 截图集。
输出文件夹	`out/`
设备截图集	iPhone 6.9 英寸（1320×2868）和 6.3 英寸（1206×2622）：两者都必须生成（ `style.md` §4）。提供 Duo 截图时，还需生成 Duo 外屏（1398×2034）和内屏（2007×2853）。
语言	原始截图所使用的语言。标题按语言撰写；裁切位置依据该语言截图进行测量。
主题	`both` ：浅色和深色。如果用户指定其中一种，则只生成该主题。
颜色	从原始截图中提取（ `style.md` §1、§9）
文案和 3D 符号	根据原始截图推导（ `style.md` §6、§8）

输出：

<out>/<lang>/<theme>/<device>/01.png … NN.png

。主题为

light

或

dark

；设备为

iphone-6.9

、

iphone-6.3

、

duo-outer

或

duo-inner

。源 HTML 文件和预览图保留在

<out>/.src/

中；不要删除，以便用户修改文案后重新渲染。如果输出文件夹中已有另一组截图的文件，不要改动；如果发生冲突，则新建一个子文件夹并告知用户。

Files

文件

```
references/style.md
```
: colour roles, background, headline, devices, highlight techniques, 3D objects from context, hero, copy tone, dark theme, iPhone Duo.
```
assets/panorama.html
```
: the template. Device frames (iPhone, Duo outer, Duo inner), headline, crops (pop-out card, spotlight, frame, chip), dimming, puffy 3D objects (
```
.obj
```
: crescent, star, sparkle, bubble, play, note, heart, orb, or your own path), the hero object and per-theme raw folders (
```
RAW
```
) are ready; the layout measurements are fixed. Copy it and edit only the palette, the background shapes, the images and
```
RAW
```
.
```
scripts/render.mjs
```
: slices the panorama into PNGs.
```
node <skill>/scripts/render.mjs <panorama.html> --out <dir> --theme light|dark --device iphone|duo-outer|duo-inner [--size WxH] [--preview <png>] [--only 2,5] [--no-slices]
```
. Each device's default size is one App Store Connect accepts; for iPhone the default is 6.9", pass
```
--size 1206x2622
```
for 6.3". The
```
warnings
```
field of its JSON output lists size, ratio and alpha problems, page errors, and contrast and crop warnings (
```
WARN:
```
).
```
scripts/grid.mjs
```
: draws a labelled pixel grid and trial boxes over a raw screenshot, to measure crops.
```
node <skill>/scripts/grid.mjs raw/02.png --out <png> [--box x,y,w,h]
```
. A crop guessed by eye drifts once it is scaled, so measure every crop on the grid.

Needs Node 18+ and Chrome (or Chromium, Edge, Brave); set

CHROME_PATH

if it isn't found. The headline font is SF Pro Display on macOS and Inter (Google Fonts) elsewhere.

```
references/style.md
```
：色彩角色、背景、标题、设备、亮点突出技巧、源自语境的 3D 物体、hero、文案语气、深色主题和 iPhone Duo。
```
assets/panorama.html
```
：模板。设备框架（iPhone、Duo 外屏、Duo 内屏）、标题、裁切（突出卡片、聚光灯、框架、芯片）、变暗效果、蓬松感 3D 物体（
```
.obj
```
：新月、星星、闪光、对话气泡、播放、便签、心形、球体，或你自己的路径）、hero 物体以及按主题区分的原始截图文件夹（
```
RAW
```
）均已准备就绪；布局测量值固定。复制模板后，只编辑调色板、背景形状、图像和
```
RAW
```
。
```
scripts/render.mjs
```
：将全景图切分为 PNG。
```
node <skill>/scripts/render.mjs <panorama.html> --out <dir> --theme light|dark --device iphone|duo-outer|duo-inner [--size WxH] [--preview <png>] [--only 2,5] [--no-slices]
```
。每个设备的默认尺寸均为 App Store Connect 接受的尺寸；对于 iPhone，默认使用 6.9 英寸，传入
```
--size 1206x2622
```
可用于 6.3 英寸。其 JSON 输出中的
```
warnings
```
字段会列出尺寸、比例和 alpha 通道问题、页面错误，以及对比度和裁切警告（
```
WARN:
```
）。
```
scripts/grid.mjs
```
：在原始截图上绘制带标签的像素网格和试验框，以测量裁切范围。
```
node <skill>/scripts/grid.mjs raw/02.png --out <png> [--box x,y,w,h]
```
。裁切框如果靠肉眼猜测，缩放后会产生偏移，因此必须在网格上测量每个裁切框。

需要 Node 18+ 和 Chrome（或 Chromium、Edge、Brave）；如果未找到 Chrome，请设置

CHROME_PATH

。标题字体在 macOS 上使用 SF Pro Display，在其他平台使用 Inter（Google Fonts）。

Workflow

工作流

Inspect the raw screenshots. Check each file's pixel size, what each screen is for, and the text on it. Note the app's subject and symbols: icon, tab icons, illustrations on the screens. The 3D objects and the hero symbol are picked from these. Pick the accent (A): the colour of buttons, the selected tab or the logo. Derive the palette from A as in
```
style.md
```
§1. To sample colours, use
```
magick <png> -format "%[hex:p{x,y}]" info:
```
or the grid image. Check whether the Duo folders exist and have the right sizes (
```
style.md
```
§10). Check which raw folders exist and pick each theme's folder (
```
style.md
```
§9). With light and dark folders, check that they hold the same file names at the same pixel sizes and show the same state (content, scroll position, time).
Plan the set in your head; don't write it down. Order: the hero, then the screens in order of value. For each image, decide: the headline, the colour of the headline zone (A or the second background, in groups of 2–3), the main highlight technique and the part to crop. Whatever part proves the screen's point is the main highlight. Then spread the 3D objects over the seams. The Duo sets tell the same story: same order, headlines, palette and symbols.
Measure the crops. Run
```
grid.mjs
```
for each part, look at the image, try the box with
```
--box
```
, and look again. The box should hug the element with a little air, not cut text, and not take in neighbouring UI. Measure the card's corner radius too (
```
data-r
```
). Measure the Duo crops separately, from their own raw files. Measure on the light screenshots. With a dark folder, try the same boxes on the dark ones too (
```
grid.mjs raw-dark/02.png --box …
```
): the crops are shared, so they must hug the same element in both.
Build the iPhone panorama. Copy
```
assets/panorama.html
```
to
```
<out>/.src/panorama.html
```
:
- Change the palette in
```
:root
```
  .
- Set
```
RAW
```
  in the script:
```
{ light: 'raw-light', dark: 'raw-dark' }
```
  with two folders,
```
{ light: 'raw', dark: 'raw' }
```
  with one. Write every path with the light folder; the dark render swaps it.
- Write a
```
<section class="shot">
```
  for each image. Give
```
data-raw
```
  for the crops; paths are relative to the
```
.src
```
  folder the HTML is in (
```
../../raw/…
```
  when the output is
```
out/
```
  ,
```
../../../raw/…
```
  for
```
out/x/
```
  ). The crop and colour values in the template are only examples; measure all of them for this app.
- Draw the background shapes in
```
svg.bg
```
  , in panorama coordinates: decide the colour sequence of the headline zones first, then route the shapes to match it.
- Put the 3D objects on the seams as direct children of
```
.pano
```
  . Put the hero object in the first section.
- Delete the example sections and objects.
Build the Duo panoramas (if there are Duo screenshots). Copy the iPhone panorama to
```
.src/panorama-duo-outer.html
```
and
```
.src/panorama-duo-inner.html
```
and adapt them as in
```
style.md
```
§10: the same headlines, palette and symbols; new crops; cards, objects and background shapes laid out again for the design height;
```
RAW
```
set to the Duo folders (e.g.
```
{ light: 'raw-duo-outer-light', dark: 'raw-duo-outer-dark' }
```
).

Render. One run per theme and device (for dark,

--theme dark

and

dark

R=<skill>/scripts/render.mjs; S=<out>/.src; O=<out>/<lang>/light
node $R $S/panorama.html          --theme light --device iphone    --out $O/iphone-6.9 --preview $S/preview-light.png
node $R $S/panorama.html          --theme light --device iphone    --out $O/iphone-6.3 --size 1206x2622
node $R $S/panorama-duo-outer.html --theme light --device duo-outer --out $O/duo-outer --preview $S/preview-light-duo-outer.png
node $R $S/panorama-duo-inner.html --theme light --device duo-inner --out $O/duo-inner --preview $S/preview-light-duo-inner.png

Fix every warning; for a contrast warning, adjust the palette. Each image is its own Chrome run (~10 s). While fixing, render only the changed images with

--only 2,5

, or only the preview with

--no-slices --preview …

; render everything from scratch before delivery.

Look and fix. Look at the previews first, then at each image, and go through the checklist. Fix and render again. Don't deliver an image you haven't looked at: a shifted crop, a curve behind a headline or an object covering a card only shows in the picture. The 6.3" set is the 6.9" set scaled down; looking at one is enough, but check the file count and size of both.
Deliver. Briefly give the folders, the device sets, the number of images, each image's headline and which raw folder each theme used. If a dark screenshot showed a different state, name the screens to retake. If no Duo sets were made, say why and what needs to be captured. Mention that changing the copy only takes editing the HTML in
```
.src/
```
and running the commands from step 6.

检查原始截图。 检查每个文件的像素尺寸、每个画面的用途及其中的文字。记录 App 的主题和符号：图标、标签图标、屏幕中的插图。3D 物体和 hero 符号均从中选取。选择强调色（A）：按钮、选中标签或 logo 的颜色。按照
```
style.md
```
§1 的方法从 A 推导调色板。可使用
```
magick <png> -format "%[hex:p{x,y}]" info:
```
或网格图采样颜色。检查 Duo 文件夹是否存在且尺寸正确（
```
style.md
```
§10）。检查存在哪些原始截图文件夹，并按
```
style.md
```
§9 为每个主题选择对应文件夹。对于浅色和深色文件夹，检查其文件名是否相同、像素尺寸是否一致，以及是否显示相同状态（内容、滚动位置、时间）。
在脑中规划截图集；不要写下来。 顺序：先 hero，再按价值排序展示各屏幕。为每张图决定：标题、标题区域颜色（A 或第二种背景色，按 2–3 张分组）、主要亮点技巧及要裁切的部位。无论哪个部分最能证明该屏幕的用途，就将其作为主要亮点。然后把 3D 物体分散到接缝处。Duo 截图集讲述相同的故事：使用相同顺序、标题、调色板和符号。
测量裁切范围。 运行
```
grid.mjs
```
检查每个部分，查看图像，使用
```
--box
```
尝试裁切框，然后再次查看。裁切框应紧贴目标元素并保留少量空间，不能切掉文字，也不能带入相邻 UI。使用
```
data-r
```
测量卡片圆角。Duo 裁切需分别从其对应的原始文件中测量。在浅色截图上测量。如果存在深色文件夹，也要在深色截图中尝试相同的裁切框（
```
grid.mjs raw-dark/02.png --box …
```
）：裁切范围是共享的，因此必须在两种主题中都紧贴同一元素。
构建 iPhone 全景图。 将
```
assets/panorama.html
```
复制到
```
<out>/.src/panorama.html
```
：
- 修改
```
:root
```
  中的调色板。
- 设置脚本中的
```
RAW
```
  ：使用两个文件夹时为
```
{ light: 'raw-light', dark: 'raw-dark' }
```
  ，使用一个文件夹时为
```
{ light: 'raw', dark: 'raw' }
```
  。所有路径都写浅色文件夹路径；深色渲染时会自动替换。
- 为每张图编写一个
```
<section class="shot">
```
  。使用
```
data-raw
```
  指定裁切来源；路径相对于 HTML 所在的
```
.src
```
  文件夹（输出为
```
out/
```
  时使用
```
../../raw/…
```
  ，输出为
```
out/x/
```
  时使用
```
../../../raw/…
```
  ）。模板中的裁切和颜色值仅为示例；必须针对此 App 逐一测量。
- 在全景图坐标系中绘制
```
svg.bg
```
  背景形状：先确定标题区域的颜色顺序，再据此安排形状走向。
- 将 3D 物体作为
```
.pano
```
  的直接子元素放在接缝处。将 hero 物体放在第一个 section 中。
- 删除示例 section 和物体。
构建 Duo 全景图（如果提供 Duo 截图）。将 iPhone 全景图复制到
```
.src/panorama-duo-outer.html
```
和
```
.src/panorama-duo-inner.html
```
，并按照
```
style.md
```
§10 进行调整：使用相同的标题、调色板和符号；采用新的裁切范围；根据设计高度重新排列卡片、物体和背景形状；将
```
RAW
```
设置为 Duo 文件夹（例如
```
{ light: 'raw-duo-outer-light', dark: 'raw-duo-outer-dark' }
```
）。

渲染。 每个主题和设备运行一次（深色使用

--theme dark

和

dark

）：

R=<skill>/scripts/render.mjs; S=<out>/.src; O=<out>/<lang>/light
node $R $S/panorama.html          --theme light --device iphone    --out $O/iphone-6.9 --preview $S/preview-light.png
node $R $S/panorama.html          --theme light --device iphone    --out $O/iphone-6.3 --size 1206x2622
node $R $S/panorama-duo-outer.html --theme light --device duo-outer --out $O/duo-outer --preview $S/preview-light-duo-outer.png
node $R $S/panorama-duo-inner.html --theme light --device duo-inner --out $O/duo-inner --preview $S/preview-light-duo-inner.png

修复所有警告；遇到对比度警告时，调整调色板。每张图会单独启动一次 Chrome（约 10 秒）。修复过程中，可使用

--only 2,5

仅重新渲染变更的图片，或使用

--no-slices --preview …

仅生成预览；交付前应从头重新渲染全部内容。

查看并修复。 先查看预览，再逐张查看图片，并按检查清单核对。发现问题后修复并重新渲染。不要交付任何未经查看的图片：裁切偏移、标题后方出现曲线，或物体遮挡卡片等问题只有在实际图片中才能看出来。6.3 英寸截图集是 6.9 英寸截图集的缩小版；查看其中一套即可，但必须检查两套的文件数量和尺寸。
交付。 简要说明文件夹、设备截图集、图片数量、每张图的标题，以及每个主题使用了哪个原始截图文件夹。如果某个深色截图显示了不同状态，请指出需要重新采集的屏幕。如果没有制作 Duo 截图集，说明原因以及需要采集的内容。提醒用户，只需编辑
```
.src/
```
中的 HTML 并运行第 6 步中的命令，即可修改文案。

If a reference set is given

如果提供了参考截图集

If the user gives another app's store screenshots as a reference, replace the layout values in

style.md

with measurements of that set:

Look at the images one by one, then side by side, and measure them at full resolution: background and continuity, headline, device, highlight techniques, decoration, special images, rhythm and tone.
Don't add anything the reference doesn't have.
If the reference's aspect ratio differs from the output's, carry measurements over relative to the width. Pin elements at the top to the top and elements cut off at the bottom to the bottom.
Take only style and layout from the reference. Never copy its logo, brand name, mascot, photos or text. Translate its decoration into the app's own context too.
Don't write files for the measurements either.

如果用户提供了另一个 App 的商店截图作为参考，则用该截图集的测量值替换

style.md

中的布局参数：

逐张查看图片，然后并排比较，并按全分辨率测量：背景与连续性、标题、设备、亮点突出技巧、装饰元素、特殊图片、节奏和语气。
不要添加参考集中不存在的元素。
如果参考图与输出图的宽高比不同，则按相对于宽度的方式换算测量值。将顶部对齐的元素固定在顶部，将底部被裁切的元素固定在底部。
只参考其风格和布局。绝不复制其 logo、品牌名称、吉祥物、照片或文字。还要将装饰元素转换为 App 自身的语境。
同样不要为测量结果编写文件。

Checklist

检查清单

Are
```
warnings
```
empty for every theme and device? Is every file the right size, without an alpha channel? Does every device set have the same number of images?
In the previews, do background shapes and seam objects continue across every seam?
Is there a curve in the headline zone (y 0–650)? Do headline colours match their background and change in groups of 2–3?
Is the headline the same size in every image? Does any headline other than the hero's run past 2 lines?
Is the device in the same place in every image? Is any important part of the UI under the rounded corners or the Dynamic Island?
Does each crop show exactly what it should? Any cut-off text, or slivers of neighbouring UI at its edges? Is the card sharp?
Does a pop-out card's edge cut a line of text in the dimmed screen below it in half? Does text show through the gaps of a card grid?
If the hero object spills into image 2, does it touch a card or text there? Do the hero's cards tuck behind the rim, or do they look like they are dissolving?
Do the 3D objects come from the app's subject? Do they cover the headline, a card or important UI text? At most 2 objects per image?
Is the symbol recognisable on the hero? Do the cards sit inside it or in front of it?
Is the dark theme dark-dominant (no large flat A area; A only in headlines, objects and frames)? Do the device rim, cards and objects stand out from the background? Is the layout the same in both themes?
With dark-mode screenshots: does the dark set show the dark UI in the device and in every crop, and the light set the light UI? Does each shared crop show the same element in both?
In the Duo sets, does every screen come from a Duo raw screenshot? Do the cards, objects and background shapes fit the short Duo canvas; is the bottom of the device or any card cut off? Does the side tab and status bar survive the crops correctly?
Are language-specific characters right (e.g. Turkish İ, ı, ş, ğ)? (
```
<html lang>
```
must match the language.)

每个主题和设备的
```
warnings
```
是否为空？每个文件尺寸是否正确且不含 alpha 通道？每个设备截图集的图片数量是否相同？
在预览中，背景形状和接缝物体是否贯穿每一条接缝？
标题区域（y 0–650）中是否有曲线？标题颜色是否与背景匹配，并按 2–3 张一组变化？
每张图中的标题尺寸是否一致？除 hero 外，是否有标题超过 2 行？
设备是否在每张图中都处于相同位置？是否有重要 UI 被圆角或 Dynamic Island 遮挡？
每个裁切是否准确展示了目标内容？边缘是否切掉了文字，或带入相邻 UI 的细碎部分？卡片是否清晰锐利？
突出卡片的边缘是否将下方变暗屏幕中的某行文字切成两半？卡片网格的间隙中是否透出了文字？
如果 hero 物体延伸到第 2 张图，它是否碰到该图中的卡片或文字？hero 的卡片是否藏在边缘下方，还是看起来正在消融？
3D 物体是否来自 App 的主题？是否遮挡了标题、卡片或重要 UI 文字？每张图是否最多放置 2 个物体？
hero 中的符号是否易于辨认？卡片是位于符号内部还是前方？
深色主题是否以深色为主（不存在大面积单一 A 色区域；A 色仅用于标题、物体和框架）？设备边缘、卡片和物体是否从背景中突出？两种主题的布局是否一致？
使用深色模式截图时，深色截图集是否在设备和每个裁切中都显示深色 UI，浅色截图集是否都显示浅色 UI？每个共享裁切是否在两种主题中都展示同一元素？
在 Duo 截图集中，每个画面是否都来自 Duo 原始截图？卡片、物体和背景形状是否适合较短的 Duo 画布？设备或卡片底部是否被裁掉？侧边标签栏和状态栏是否在裁切后仍保持正确？
与语言相关的字符是否正确（例如土耳其语的 İ、ı、ş、ğ）？（
```
<html lang>
```
必须与语言匹配。）