design-qa-implementation-parity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design Qa Implementation Parity

设计QA实现一致性检查

Overview

概述

Use this skill to detect and triage design-to-implementation drift with evidence that engineers and designers can both act on.

使用此Skill检测并分类设计与实现之间的偏差，提供工程师和设计师均可据此采取行动的依据。

Scope Boundaries

范围边界

Use this skill when the task matches the trigger condition described in
```
description
```
.
Do not use this skill when the primary task falls outside this skill's domain.

当任务符合
```
description
```
中描述的触发条件时，使用此Skill。
当主要任务超出此Skill的领域范围时，请勿使用。

Shared References

共享参考资料

Severity classification model:
- ```
references/parity-severity-model.md
```

严重性分类模型：
- ```
references/parity-severity-model.md
```

Templates And Assets

模板与资源

Findings log:
- ```
assets/parity-findings-template.csv
```
Sign-off decision document:
- ```
assets/parity-signoff-template.md
```

问题记录日志：
- ```
assets/parity-findings-template.csv
```
签核决策文档：
- ```
assets/parity-signoff-template.md
```

Inputs To Gather

需要收集的输入信息

Approved design source and exact version/snapshot.
Target implementation build, environment, and feature flags.
Scope list of screens, states, breakpoints, and locales to validate.
Existing acceptance criteria or release gates for UI parity.

已批准的设计源文件及其确切版本/快照。
目标实现的构建版本、环境及功能标志。
需要验证的页面、状态、断点和语言区域范围列表。
现有UI一致性验收标准或发布准入条件。

Deliverables

交付成果

Parity findings report with severity, scope, owner, and reproduction steps.
State-level pass/fail checklist for critical flows.
Prioritized remediation plan with release impact notes.
Sign-off decision (approve/conditional/reject) with clear rationale.

包含严重性、范围、负责人和复现步骤的一致性问题报告。
关键流程的状态级通过/失败检查表。
附带发布影响说明的优先级修复计划。
带有明确理由的签核决策（批准/有条件批准/拒绝）。

Quick Example

快速示例

Blocker: CTA button hidden on mobile breakpoint in checkout summary.
Major: loading state typography differs from approved scale and causes truncation.
Minor: icon spacing deviates by 2px without usability impact.
Decision: reject until blocker fixed; allow major/minor with dated follow-up only if policy permits.

阻塞问题：结账摘要页面的CTA按钮在移动端断点处被隐藏。
主要问题：加载状态的字体与批准的规格不符，导致文本截断。
次要问题：图标间距偏差2px，但不影响可用性。
决策：修复阻塞问题前拒绝签核；若政策允许，可批准主要/次要问题，但需记录后续跟进日期。

Quality Standard

质量标准

Source versions are locked so comparisons are deterministic.
Coverage includes critical states: loading, empty, error, success.
Every mismatch includes reproducible evidence and ownership.
Severity rules are consistent and tied to user/business impact.

锁定源文件版本，确保对比结果可确定。
覆盖关键状态：加载、空状态、错误、成功。
每个偏差均包含可复现的证据和负责人。
严重性规则保持一致，并与用户/业务影响挂钩。

Workflow

工作流程

Freeze source design and implementation versions for the review window.
Compare critical flows first, then secondary and edge states.
Classify mismatches by severity and release impact using
```
references/parity-severity-model.md
```
.
Record findings in
```
assets/parity-findings-template.csv
```
, assign owners, and define remediation order.
Publish sign-off outcome in
```
assets/parity-signoff-template.md
```
with unresolved risk explicitly documented.

在评审周期内冻结源设计和实现版本。
先对比关键流程，再对比次要流程和边缘状态。
使用
```
references/parity-severity-model.md
```
对偏差按严重性和发布影响进行分类。
将问题记录在
```
assets/parity-findings-template.csv
```
中，分配负责人并确定修复顺序。
在
```
assets/parity-signoff-template.md
```
中发布签核结果，并明确记录未解决的风险。

Failure Conditions

终止条件

Stop sign-off when source versions are not locked.
Stop when critical flows are missing parity coverage.
Escalate when blocker-level mismatches remain unresolved near release.

当源文件版本未锁定时，停止签核。
当关键流程未覆盖一致性检查时，停止签核。
当临近发布仍存在未解决的阻塞级偏差时，升级处理。