product-design-and-ux

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Product Design and UX

产品设计与UX

Turn validated evidence and chosen scope into observable behavior people can complete and recover from. Design the interaction, not the brand, pixels, CSS, component implementation, or a particular tool.

基于验证后的证据和选定的范围，设计用户可完成操作并能从异常中恢复的可观测行为。专注于交互设计，而非品牌、像素、CSS、组件实现或特定工具。

Entry Check

准入检查

Confirm the approved scope, outcome, users or roles, evidence links, constraints, measurable experience goals, and open product decisions. Record missing inputs rather than inventing them.

Need stakeholder evidence, validation, or raw research? Use product-discovery.
Need prioritization, scope, or why a feature is being built? Use product-methodology.
Need WCAG, ARIA, native semantics, or accessibility testing depth? Use web-accessibility.
Need an approved interaction contract translated into a software specification and delivery gates? Use spec-driven-development.

确认已批准的范围、预期成果、用户或角色、证据链接、约束条件、可衡量的体验目标以及待决策的产品事项。记录缺失的输入信息，而非自行编造。

需要利益相关者的证据、验证或原始研究？请使用product-discovery。
需要优先级排序、范围界定或了解功能开发的原因？请使用product-methodology。
需要WCAG、ARIA、原生语义或深度可访问性测试？请使用web-accessibility。
需要将已批准的交互契约转化为软件规格说明和交付关卡？请使用spec-driven-development。

Workflow

工作流程

Trace each outcome and design decision to evidence with
```
templates/outcomes-to-design.md
```
. Optional personas or jobs must change a decision and cite evidence; do not create decorative demographics.
Establish information architecture from goals, content objects, terminology, permissions, findability, and service context. Read
```
references/information-architecture.md
```
.
Define consequential labels, instructions, status, errors, and completion content; review the task's memory, choice, switching, interruption, and recovery demands. Use heuristics to generate testable questions, not verdicts. Read
```
references/content-and-cognitive-demand.md
```
.
Model important tasks, including forces that create decisions, alternatives, interruption, re-entry, cancellation, recovery, irreversible actions, side effects, permission changes, and completion evidence. Read
```
references/task-flows-and-state-models.md
```
and use
```
templates/task-flow-state-model.md
```
.
Inventory only states forced by the flow, data, permissions, connectivity, and risk. Record risky omissions. Use
```
templates/screen-state-inventory.md
```
.
Write framework-neutral contracts for content, controls, accessible interaction requirements, actions, transitions, persistence, permissions, responsive/reflow behavior, telemetry, and open decisions. Read
```
references/interface-contracts-and-responsive-behavior.md
```
and use
```
templates/interface-contract.md
```
.
Treat patterns as hypotheses. Compare alternatives, tradeoffs, evidence, and disconfirming conditions with
```
references/interaction-pattern-selection.md
```
.
Plan or synthesize only authorized usability work. Read
```
references/usability-testing-and-privacy.md
```
; use
```
templates/usability-study.md
```
. Never invent participants, consent, observations, quotes, or results.
Produce an engineering handoff with observable acceptance evidence, dependencies, owners, gates, and deployed-boundary verification. Read
```
references/engineering-handoff.md
```
; use
```
templates/engineering-handoff.md
```
. Hand approved behavior to spec-driven-development.

使用
```
templates/outcomes-to-design.md
```
将每个预期成果和设计决策与证据关联起来。可选的用户角色或任务必须能改变决策并引用证据；请勿创建无实际作用的人口统计信息。
根据目标、内容对象、术语、权限、可查找性和服务上下文建立信息架构。请阅读
```
references/information-architecture.md
```
。
定义关键的标签、说明、状态、错误信息和完成提示；评估任务的记忆负担、选择难度、切换成本、中断影响和恢复需求。使用启发式方法生成可测试的问题，而非直接给出结论。请阅读
```
references/content-and-cognitive-demand.md
```
。
对重要任务进行建模，包括影响决策的因素、备选方案、中断、重新进入、取消、恢复、不可逆操作、副作用、权限变更和完成证据。请阅读
```
references/task-flows-and-state-models.md
```
并使用
```
templates/task-flow-state-model.md
```
。
仅梳理由流程、数据、权限、连接性和风险所决定的状态。记录存在风险的遗漏项。使用
```
templates/screen-state-inventory.md
```
。
编写与框架无关的契约，涵盖内容、控件、无障碍交互要求、操作、过渡、持久化、权限、响应式/回流行为、遥测和待决策事项。请阅读
```
references/interface-contracts-and-responsive-behavior.md
```
并使用
```
templates/interface-contract.md
```
。
将交互模式视为假设。使用
```
references/interaction-pattern-selection.md
```
对比备选方案、权衡因素、证据和否定条件。
仅规划或整合经授权的可用性工作。请阅读
```
references/usability-testing-and-privacy.md
```
；使用
```
templates/usability-study.md
```
。切勿虚构参与者、同意书、观察结果、引用或测试结果。
生成包含可观测验收证据、依赖项、负责人、关卡和部署边界验证的工程交接文档。请阅读
```
references/engineering-handoff.md
```
；使用
```
templates/engineering-handoff.md
```
。将已批准的行为交付给spec-driven-development。

Load On Demand

按需加载

Need	Load
Scope boundary, traceability, or adjacent-skill routing	`references/boundaries-and-traceability.md`
Goals, labels, navigation, findability, permissions	`references/information-architecture.md`
Plain-language content, heuristic review, cognitive demand	`references/content-and-cognitive-demand.md`
Task paths, state applicability, recovery, side effects	`references/task-flows-and-state-models.md`
Interaction contract or inclusive responsive behavior	`references/interface-contracts-and-responsive-behavior.md`
Pattern alternatives and decision evidence	`references/interaction-pattern-selection.md`
Usability protocol, synthesis, consent, or privacy	`references/usability-testing-and-privacy.md`
Handoff, acceptance criteria, or deployed verification	`references/engineering-handoff.md`
Methodology self-check with synthetic fixtures	`references/scenario-probes.md`
Source authority, status, and examples	`references/source-index.md`

需求	加载资源
范围边界、可追溯性或相关技能路由	`references/boundaries-and-traceability.md`
目标、标签、导航、可查找性、权限	`references/information-architecture.md`
简明语言内容、启发式评审、认知负担	`references/content-and-cognitive-demand.md`
任务路径、状态适用性、恢复、副作用	`references/task-flows-and-state-models.md`
交互契约或包容性响应式行为	`references/interface-contracts-and-responsive-behavior.md`
模式备选方案和决策证据	`references/interaction-pattern-selection.md`
可用性测试协议、整合、同意书或隐私	`references/usability-testing-and-privacy.md`
交接文档、验收标准或部署验证	`references/engineering-handoff.md`
使用合成场景进行方法自查	`references/scenario-probes.md`
来源权威、状态和示例	`references/source-index.md`

Guardrails

约束规则

Accessibility is designed throughout, but WCAG/ARIA/native-semantics and testing depth remain with
```
web-accessibility
```
.
Specify behavior under relevant width, zoom/reflow, text expansion/localization, orientation, input modes, reduced motion, degraded connectivity, interruption, and re-entry. Do not use device breakpoints as the model.
Use synthetic fixtures such as
```
sample-user@example.test
```
and
```
INV-DEMO-042
```
; never request real credentials, payments, financial access, or secrets for an unsafe prototype.
A finding from usability work is bounded evidence, not accessibility conformance, population prevalence, analytics, or outcome proof.

可访问性需贯穿设计全过程，但WCAG/ARIA/原生语义及深度测试仍由
```
web-accessibility
```
负责。
指定在相关宽度、缩放/回流、文本放大/本地化、方向、输入模式、减少动画、连接降级、中断和重新进入等场景下的行为。请勿以设备断点作为模型依据。
使用合成测试数据，如
```
sample-user@example.test
```
和
```
INV-DEMO-042
```
；切勿为不安全的原型请求真实凭证、支付信息、财务访问权限或机密信息。
可用性研究的发现是有限的证据，而非可访问性合规证明、群体普遍性、分析数据或成果验证。

Completion

完成标准

Stop when every in-scope behavior has traceable evidence, an applicable state/recovery model, observable acceptance criteria, and either a resolved decision or an owner and resolution gate. Report limitations and untested risks rather than filling gaps with assumptions.

当所有范围内的行为都有可追溯的证据、适用的状态/恢复模型、可观测的验收标准，且每个决策要么已解决，要么已明确负责人和解决关卡时，即可停止工作。需报告局限性和未测试的风险，而非用假设填补空白。