Components map a name to a group of sub-token properties: ... Valid component properties: backgroundColor, textColor, typography, rounded, padding, size, height, width.
大多数人认为组件应该被定义为完整的、独立的实体，包含所有必要的样式和功能。但作者认为组件应该被定义为对已有设计 tokens 的引用和组合，而不是独立的样式定义。这种方法挑战了传统的组件设计理念，强调了设计系统中的复用性和一致性而非组件独立性。
The tokens are the normative values. The prose provides context for how to apply them.
大多数人认为设计规范应该优先考虑精确的技术规格和约束条件。但作者认为 prose（描述性文本）与 tokens（规范值）同等重要，甚至可能更重要，因为它提供了应用上下文。这挑战了传统设计系统完全由技术规范主导的观念，强调了人文因素在设计系统自动化中的关键作用。
Design tokens are a methodology for expressing design decisions in a platform-agnostic way so that they can be shared across different disciplines, tools, and technologies. They help establish a common vocabulary across organisations.
This is a very concise definition of the term, "design token". It is absent of vendor jargon. However, I think a better way to describe it would be: "Design tokens are shareable generic expressions of design decisions. Their purpose is to help multi-disciplinary teams build, scale and maintain consistent digital experiences."
The middle layer approach pushes designers to explicitly describe the component visual architecture and that translates to its better understanding.
Designers want every part of the app interface and all the elements to have the same look and feel, and design tokens were created to help them achieve that outcome.
Design tokens are platform-agnostic and are the first layer of design decisions in a design system.