Back to Details

absence-audit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Absence Audit

缺失审计

The hardest things to notice are the things that aren't there.
最难察觉的恰恰是那些不存在的事物。

How to use

使用方法

  • /absence-audit
    Apply absence analysis to any design in this conversation.
  • /absence-audit
    对本次对话中的任意设计进行缺失分析。

Constraints

约束条件

What to Look For

关注要点

  • MUST list 5-10 things that are conspicuously absent from the design
  • MUST hypothesize for each: intentional removal or never considered?
  • MUST evaluate: does the absence strengthen or weaken the experience?
  • SHOULD note what the absence reveals about the design philosophy
  • 必须列出5-10个设计中明显缺失的元素
  • 必须针对每个缺失元素假设：是刻意移除还是从未考虑过？
  • 必须评估：这种缺失是增强了还是削弱了用户体验？
  • 应注明这种缺失反映了怎样的设计理念

Categories of Absence

缺失类别

  • Missing UI elements (no breadcrumbs, no tooltips, no onboarding tutorial)
  • Missing content (no testimonials, no feature comparison, no pricing)
  • Missing states (no loading skeleton, no empty state, no error recovery)
  • Missing interaction (no animation, no hover effects, no sound)
  • 缺失的UI元素（无面包屑、无提示框、无入门教程）
  • 缺失的内容（无客户评价、无功能对比、无定价信息）
  • 缺失的状态（无加载骨架屏、无空状态提示、无错误恢复机制）
  • 缺失的交互（无动画、无悬停效果、无音效）

The Restraint Signal

克制信号

  • Intentional absence is a strong taste signal. It says "we thought about this and decided it wasn't needed."
  • Accidental absence (missing error states, broken edge cases) signals the opposite.
  • MUST distinguish between the two.
  • 刻意的缺失是强烈的品味信号，它传达的是“我们考虑过这个，但认为它并非必需”。
  • 意外的缺失（如缺失错误状态、未处理边缘情况）则传达相反的信号。
  • 必须区分这两种情况。

Anti-Patterns

反模式

  • Treating every absence as a problem to fix
  • Assuming absence equals minimalism (it might just be incomplete)
  • Missing obvious gaps because you're focused on what IS there
  • 将每一处缺失都视为需要修复的问题
  • 假设缺失就等于极简主义（它可能只是设计不完整）
  • 因专注于已存在的元素而忽略明显的漏洞