Back to Details

decision-tracing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Decision Tracing

Decision Tracing

Look at a decision. Figure out why it was made.
观察一项决策，找出其制定原因。

How to use

使用方法

  • /decision-tracing
    Apply decision-tracing analysis to any design in this conversation.
  • /decision-tracing
    对本次对话中的任意设计应用决策追溯分析。

Constraints

约束条件

Trace Structure

追溯结构

  • MUST follow: Observation > Decision > Probable Reason
  • "The primary font is Inter" > "They chose a geometric sans-serif" > "Data-heavy product needing maximum legibility at small sizes with neutral personality"
  • MUST generate at least 5 traces per design screen
  • SHOULD acknowledge uncertainty: "probable reason" not "the reason"
  • NEVER state intent as fact unless you have insider knowledge
  • 必须遵循：观察 > 决策 > 可能原因
  • 示例：“主字体为Inter” > “他们选择了几何无衬线字体” > “数据密集型产品需要在小尺寸下实现最高可读性，同时保持中性风格”
  • 每个设计界面必须生成至少5条追溯记录
  • 应当承认不确定性：使用“可能原因”而非“原因”
  • 除非掌握内部信息，否则绝不能将意图当作事实陈述

What to Trace

追溯范围

  • Typeface selection and type system
  • Color palette and color role assignments
  • Layout structure and grid decisions
  • Spacing and density choices
  • Navigation architecture
  • What's absent (what they chose NOT to include)
  • 字体选择与字体系统
  • 调色板与色彩角色分配
  • 布局结构与网格决策
  • 间距与密度选择
  • 导航架构
  • 缺失内容（他们选择不包含的元素）

Anti-Patterns

反模式

  • Assuming the most flattering interpretation of every decision
  • Tracing only visual decisions and ignoring structural ones
  • Stating reasons as facts without marking them as hypotheses
  • 假设每个决策都是最理想化的解读
  • 仅追溯视觉决策而忽略结构性决策
  • 将原因当作事实陈述，未标记为假设