principle-experience-first

体验优先

When implementation convenience conflicts with user delight, choose delight.

实现方便与用户愉悦冲突时，选愉悦。

• Every feature, control, and option must be justified

• Ship less, ship better (polished experience with three features beats rough one with ten)

• Prototype before committing (design decisions are cheaper in throwaway HTML than production code)

• Get the details right (transitions, alignment, spacing, feedback, error states)

• Tighten the core loop (every feature should serve the central workflow or get out of the way)

• 每个功能、控件、选项都必须说得通

• 少而精（三个打磨好的功能胜过十个糙的）

• 承诺前先原型（设计决策在一次性 HTML 里比在生产代码里便宜）

• 细节做对（过渡、对齐、间距、反馈、错误态）

• 收紧核心环（每个功能服务中心工作流，否则让开）

The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their perspective.

用户是消费这份工作的人。UI 是最终用户；库或内部 API 是 import 它的同事。下一个维护代码的工程师也是用户。同样权衡他们的体验，并从他们视角解释影响。

Foundations should serve the experience. Foundational thinking governs the sequence of work. This principle governs the target.

基础应服务体验。Foundational thinking 管工作的顺序。本原则管目标。