ds-design-audit
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseScore a UI from what is on the screen, fix the worst problems, and show that the fixes work.
根据屏幕上呈现的内容为 UI 评分,修复最严重的问题,并证明修复效果。
Steps
步骤
- Identify the target file or URL and render it. If it does not render, report this and stop. Do not audit from the source code alone.
- Take screenshots of the first viewport and the full page at about 1440px and 390px wide. Also capture the hover, focus, empty, loading, and error states where you can.
- Read the target's code: tokens, fonts, colors, focus styles, media queries, and copy.
- Give each area a score from 1 to 5. Give one line of evidence for each score: something visible or a line of code.
- Hierarchy: the main message and action are clear within 3 seconds, and there is one focal point.
- Typography: the fonts are paired on purpose, the scale is consistent, and the line length and leading are correct.
- Color: there is one dominant color and one accent, the colors are tokens and not scattered hex values, and there are no decorative gradients.
- Spacing: the spacing follows a scale, the rhythm is consistent, and the mobile alignment is correct.
- States: hover, focus, empty, loading, error, and long-content states all exist.
- Accessibility: the contrast is 4.5:1 or higher, the focus rings are visible, the fields have labels, the touch targets are 44px, and reduced motion is respected.
- Copy: the copy is specific to the product, with no stock phrases and no placeholder data.
- Record each banned default that you see: purple-blue gradients, a default font used for display, emoji used as icons, a centered hero with three identical cards, glassmorphism everywhere, gray text on gray, and generic copy.
- Rank the fixes by their impact on users. Put broken accessibility and an unclear main action first. Put decoration last. For each fix, give the file, the change, and the score that it raises.
- Apply the top 3 to 5 fixes. Fix the cause in the tokens or in the shared components, not in each instance. Keep the identity, content, and behavior of the product.
- Take new screenshots at the same widths and in the same states as in step 2. Score each area again and show the before and after scores side by side.
- If an area still has a score of 2 or lower, or a banned default remains, repeat steps 6 to 8 once. Do not do more than two passes.
- 确定目标文件或 URL 并进行渲染。如果无法渲染,请报告此情况并停止。不得仅根据源代码进行审查。
- 在约 1440px 和 390px 宽度下,分别截取首个视口和完整页面的截图。同时尽可能捕获 hover、focus、empty、loading 和 error 状态。
- 阅读目标代码:tokens、字体、颜色、focus 样式、媒体查询和文案。
- 为每个领域给出 1 到 5 分的评分。每个评分附上一行证据:可见的内容或一行代码。
- 信息层级:主要信息和操作应在 3 秒内清晰呈现,并且只有一个视觉焦点。
- 字体排版:字体经过有目的的搭配,比例保持一致,行长和行距正确。
- 颜色:使用一种主色和一种强调色;颜色通过 tokens 管理,而不是散落的十六进制值;不使用装饰性渐变。
- 间距:间距遵循统一的尺度,节奏保持一致,移动端对齐正确。
- 状态:具备 hover、focus、empty、loading、error 和长内容状态。
- 无障碍:对比度不低于 4.5:1,focus 轮廓清晰可见,表单字段有标签,触摸目标尺寸为 44px,并尊重减少动态效果设置。
- 文案:文案与具体产品相关,不使用通用套话或占位数据。
- 记录看到的每一种禁止默认项:紫蓝渐变、使用默认字体作为展示字体、使用 emoji 作为图标、以三张相同卡片组成的居中 hero、到处使用 glassmorphism、灰色文字搭配灰色背景,以及通用文案。
- 按修复对用户的影响排序。将无障碍功能损坏和主要操作不清晰放在首位,将装饰性修改放在最后。对于每项修复,说明文件、具体修改以及预计提升的评分。
- 应用影响最大的 3 到 5 项修复。应从根源修复 tokens 或共享组件中的问题,而不是逐个实例修改。保持产品的身份、内容和行为不变。
- 在与步骤 2 相同的宽度和状态下拍摄新截图。再次为每个领域评分,并并排展示修改前后的评分。
- 如果某个领域的评分仍为 2 分或更低,或者仍存在禁止默认项,则重复步骤 6 到 8 一次。最多执行两轮。
Stop when
停止条件
- Two passes are complete, or every area has a score of 3 or higher and no banned default remains.
- The report shows the before and after scores, the evidence, the fixes that you applied, and the fixes that you did not apply, each with a reason.
- 已完成两轮审查,或者所有领域的评分均达到 3 分及以上,且不存在禁止默认项。
- 报告展示修改前后的评分、证据、已应用的修复以及未应用的修复,并为每项未应用的修复说明原因。
Rules
规则
- Do not give a score without evidence. If you could not see an area, mark it "not checked" and give the reason.
- Do not change factual copy, prices, claims, or feature behavior without asking.
- If the brief requires a style that this skill would flag, it is not a fault.
- If the UI needs a full rebuild, recommend /ds-design. Do not rebuild it in this skill.
- 没有证据时不得评分。如果无法看到某个领域,请标记为“未检查”,并说明原因。
- 未经确认,不得修改事实性文案、价格、声明或功能行为。
- 如果任务简报要求的风格会被此 skill 标记,则不应视为问题。
- 如果 UI 需要完全重建,请建议使用 /ds-design。不要在此 skill 中重建。