Back to Details

negative-contrastive-framing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Negative Contrastive Framing

负面对比框架

Table of Contents

目录

Purpose

用途

Define concepts, quality criteria, and boundaries by showing what they're NOT—using anti-goals, near-miss examples, and failure patterns to create crisp decision criteria where positive definitions alone are ambiguous.
通过展示事物的反面——利用反目标、近失案例和失败模式，来定义概念、质量标准和边界，从而在仅靠正面定义存在歧义的情况下，创建清晰的决策标准。

When to Use

适用场景

Clarifying Fuzzy Boundaries:
  • Positive definition exists but edges are unclear
  • Multiple interpretations cause confusion
  • Team debates what "counts" as meeting criteria
  • Need to distinguish similar concepts
Teaching & Communication:
  • Explaining concepts to learners who need counterexamples
  • Training teams to recognize anti-patterns
  • Creating style guides with do's and don'ts
  • Onboarding with common mistake prevention
Setting Standards:
  • Defining code quality (show bad patterns)
  • Establishing design principles (show violations)
  • Creating evaluation rubrics (clarify failure modes)
  • Building decision criteria (identify disqualifiers)
Preventing Errors:
  • Near-miss incidents revealing risk patterns
  • Common mistakes that need explicit guards
  • Edge cases that almost pass but shouldn't
  • Subtle failures that look like successes
模糊边界澄清：
  • 已有正面定义，但边界模糊
  • 多种解读引发混淆
  • 团队对“符合标准”的定义存在争议
  • 需要区分相似概念
教学与沟通：
  • 向需要反例的学习者解释概念
  • 培训团队识别反模式
  • 创建包含“可做/不可做”的风格指南
  • 通过预防常见错误完成新员工入职培训
标准设定：
  • 定义代码质量（展示不良模式）
  • 确立设计原则（展示违规案例）
  • 创建评估准则（明确失败模式）
  • 制定决策标准（识别直接淘汰的条件）
错误预防：
  • 揭示风险模式的近失事件
  • 需要明确防范的常见错误
  • 几乎符合要求但实际不应通过的边缘案例
  • 看似成功实则存在隐患的细微失败

What Is It

是什么

Negative contrastive framing defines something by showing what it's NOT:
Types of Negative Examples:
  1. Anti-goals: Opposite of desired outcome ("not slow" → define fast)
  2. Near-misses: Examples that almost qualify but fail on key dimension
  3. Failure patterns: Common mistakes that violate criteria
  4. Boundary cases: Edge examples clarifying where line is drawn
Example: Defining "good UX":
  • Positive: "Intuitive, efficient, delightful"
  • Negative contrast:
    • ❌ Near-miss: Fast but confusing (speed without clarity)
    • ❌ Anti-pattern: Dark patterns (manipulative design)
    • ❌ Failure: Requires manual to understand basic tasks
负面对比框架通过展示事物的反面来定义其内涵：
负面示例类型：
  1. 反目标： 与预期结果完全相反（如“不慢”→ 定义“快速”）
  2. 近失案例： 几乎符合要求，但在关键维度上未达标的示例
  3. 失败模式： 违反标准的常见错误
  4. 边界案例： 明确界限的边缘示例
示例： 定义“优质UX”：
  • 正面描述： “直观、高效、愉悦”
  • 负面对比：
    • ❌ 近失案例：速度快但易混淆（有速度无清晰度）
    • ❌ 反模式：暗黑模式（操纵性设计）
    • ❌ 失败案例：理解基础操作需要查阅手册

Workflow

工作流程

Copy this checklist and track your progress:
Negative Contrastive Framing Progress:
- [ ] Step 1: Define positive concept
- [ ] Step 2: Identify negative examples
- [ ] Step 3: Analyze contrasts
- [ ] Step 4: Validate quality
- [ ] Step 5: Deliver framework
Step 1: Define positive concept
Start with initial positive definition, identify why it's ambiguous or fuzzy (multiple interpretations, edge cases unclear), and clarify purpose (teaching, decision-making, quality control). See Common Patterns for typical applications.
Step 2: Identify negative examples
For simple cases with clear anti-patterns → Use resources/template.md to structure anti-goals, near-misses, and failure patterns. For complex cases with subtle boundaries → Study resources/methodology.md for techniques like contrast matrices and boundary mapping.
Step 3: Analyze contrasts
Create 
negative-contrastive-framing.md
with: positive definition, 3-5 anti-goals, 5-10 near-miss examples with explanations, common failure patterns, clear decision criteria ("passes if..." / "fails if..."), and boundary cases. Ensure contrasts reveal the why behind criteria.
Step 4: Validate quality
Self-assess using resources/evaluators/rubric_negative_contrastive_framing.json. Check: negative examples span the boundary space, near-misses are genuinely close calls, contrasts clarify criteria better than positive definition alone, failure patterns are actionable guards. Minimum standard: Average score ≥ 3.5.
Step 5: Deliver framework
Present completed framework with positive definition sharpened by negatives, most instructive near-misses highlighted, decision criteria operationalized as checklist, common mistakes identified for prevention.
复制以下清单并跟踪进度：
Negative Contrastive Framing Progress:
- [ ] Step 1: Define positive concept
- [ ] Step 2: Identify negative examples
- [ ] Step 3: Analyze contrasts
- [ ] Step 4: Validate quality
- [ ] Step 5: Deliver framework
步骤1：定义正面概念
从初始正面定义入手，找出其存在歧义或模糊的原因（多种解读、边界案例不明确），并明确目标（教学、决策制定、质量控制）。具体应用可参考常见模式。
步骤2：收集负面示例
对于反模式清晰的简单场景 → 使用resources/template.md来梳理反目标、近失案例和失败模式。对于边界模糊的复杂场景 → 学习resources/methodology.md中的技巧，如对比矩阵和边界映射。
步骤3：分析对比内容
创建
negative-contrastive-framing.md
文件，包含：正面定义、3-5个反目标、5-10个带解释的近失案例、常见失败模式、明确的决策标准（“符合条件当……”/“不符合条件当……”）以及边界案例。确保对比内容能揭示标准背后的“原因”。
步骤4：验证质量
使用resources/evaluators/rubric_negative_contrastive_framing.json进行自我评估。检查：负面示例覆盖所有边界场景、近失案例确实是接近达标的情况、对比内容比单纯正面定义更清晰地解释了标准、失败模式可作为可执行的约束。最低标准：平均得分≥3.5。
步骤5：交付框架
提交最终框架，其中正面定义通过负面案例得到细化，突出最具指导性的近失案例，将决策标准转化为可操作的清单，明确需要预防的常见错误。

Common Patterns

常见模式

By Domain

按领域划分

Engineering (Code Quality):
  • Positive: "Maintainable code"
  • Negative: God objects, tight coupling, unclear names, magic numbers, exception swallowing
  • Near-miss: Well-commented spaghetti code (documentation without structure)
Design (UX):
  • Positive: "Intuitive interface"
  • Negative: Hidden actions, inconsistent patterns, cryptic error messages
  • Near-miss: Beautiful but unusable (form over function)
Communication (Clear Writing):
  • Positive: "Clear documentation"
  • Negative: Jargon-heavy, assuming context, no examples, passive voice
  • Near-miss: Technically accurate but incomprehensible to target audience
Strategy (Market Positioning):
  • Positive: "Premium brand"
  • Negative: Overpriced without differentiation, luxury signaling without substance
  • Near-miss: High price without service quality to match
工程（代码质量）：
  • 正面描述：“可维护代码”
  • 负面示例：上帝对象、紧耦合、命名模糊、魔法数字、异常吞噬
  • 近失案例：注释完善的面条代码（有文档但无结构）
设计（UX）：
  • 正面描述：“直观界面”
  • 负面示例：隐藏操作、模式不一致、晦涩的错误提示
  • 近失案例：美观但不实用（形式大于功能）
沟通（清晰写作）：
  • 正面描述：“清晰文档”
  • 负面示例：术语堆砌、预设读者具备背景知识、无示例、被动语态
  • 近失案例：技术准确但目标受众无法理解
策略（市场定位）：
  • 正面描述：“高端品牌”
  • 负面示例：定价过高却无差异化、仅做奢侈营销却无实质内容
  • 近失案例：价格高昂但服务质量不匹配

By Application

按应用场景划分

Teaching:
  • Show common mistakes students make
  • Provide near-miss solutions revealing misconceptions
  • Identify "looks right but is wrong" patterns
Decision Criteria:
  • Define disqualifiers (automatic rejection criteria)
  • Show edge cases that almost pass
  • Clarify ambiguous middle ground
Quality Control:
  • Identify anti-patterns to avoid
  • Show subtle defects that might pass inspection
  • Define clear pass/fail boundaries
教学：
  • 展示学生常犯的错误
  • 提供能揭示误解的近失解决方案
  • 识别“看似正确实则错误”的模式
决策标准：
  • 定义淘汰条件（直接拒绝的标准）
  • 展示几乎符合要求的边缘案例
  • 澄清模糊的中间地带
质量控制：
  • 识别需要避免的反模式
  • 展示可能通过检查的细微缺陷
  • 明确清晰的合格/不合格边界

Guardrails

规则约束

Near-Miss Selection:
  • Near-misses must be genuinely close to positive examples
  • Should reveal specific dimension that fails (not globally bad)
  • Avoid trivial failures—focus on subtle distinctions
Contrast Quality:
  • Explain why each negative example fails
  • Show what dimension violates criteria
  • Make contrasts instructive, not just lists
Completeness:
  • Cover failure modes across key dimensions
  • Don't cherry-pick—include hard-to-classify cases
  • Show spectrum from clear pass to clear fail
Actionability:
  • Translate insights into decision rules
  • Provide guards/checks to prevent failures
  • Make criteria operationally testable
Avoid:
  • Strawman negatives (unrealistically bad examples)
  • Negatives without explanation (show what's wrong and why)
  • Missing the "close call" zone (all examples clearly pass or fail)
近失案例选择：
  • 近失案例必须与正面示例高度接近
  • 应明确指出未达标的具体维度（而非整体糟糕）
  • 避免无关紧要的失败，专注于细微差异
对比内容质量：
  • 解释每个负面示例未达标的原因
  • 指出违反标准的具体维度
  • 对比内容需具备指导性，而非单纯罗列
完整性：
  • 覆盖关键维度的所有失败模式
  • 避免选择性案例——纳入难以分类的情况
  • 展示从完全合格到完全不合格的完整范围
可操作性：
  • 将洞察转化为决策规则
  • 提供预防失败的约束/检查项
  • 使标准可进行实际测试
需避免的情况：
  • 稻草人式负面案例（不切实际的糟糕示例）
  • 无解释的负面案例（仅指出错误却不说明原因）
  • 缺失“接近达标”的区间（所有示例要么完全合格要么完全不合格）

Quick Reference

快速参考

Resources:
  • resources/template.md
    - Structured format for anti-goals, near-misses, failure patterns
  • resources/methodology.md
    - Advanced techniques (contrast matrices, boundary mapping, failure taxonomies)
  • resources/evaluators/rubric_negative_contrastive_framing.json
    - Quality criteria
Output: 
negative-contrastive-framing.md
with positive definition, anti-goals, near-misses with analysis, failure patterns, decision criteria
Success Criteria:
  • Negative examples span boundary space (not just extremes)
  • Near-misses are instructive close calls
  • Contrasts clarify ambiguous criteria
  • Failure patterns are actionable guards
  • Decision criteria operationalized
  • Score ≥ 3.5 on rubric
Quick Decisions:
  • Clear anti-patterns? → Template only
  • Subtle boundaries? → Use methodology for contrast matrices
  • Teaching application? → Emphasize near-misses revealing misconceptions
  • Quality control? → Focus on failure pattern taxonomy
Common Mistakes:
  1. Only showing extreme negatives (not instructive near-misses)
  2. Lists without analysis (not explaining why examples fail)
  3. Cherry-picking easy cases (avoiding hard boundary calls)
  4. Strawman negatives (unrealistically bad)
  5. No operationalization (criteria remain fuzzy despite contrasts)
Key Insight: Negative examples are most valuable when they're almost positive—close calls that force articulation of subtle criteria invisible in positive definition alone.
资源：
  • resources/template.md
    - 用于梳理反目标、近失案例、失败模式的结构化模板
  • resources/methodology.md
    - 高级技巧（对比矩阵、边界映射、失败分类法）
  • resources/evaluators/rubric_negative_contrastive_framing.json
    - 质量评估标准
输出： 
negative-contrastive-framing.md
，包含正面定义、反目标、带分析的近失案例、失败模式、决策标准
成功标准：
  • 负面示例覆盖所有边界场景（而非仅极端情况）
  • 近失案例具有指导性且是接近达标的情况
  • 对比内容澄清了模糊的标准
  • 失败模式可作为可执行的约束
  • 决策标准可落地执行
  • 评估得分≥3.5
快速决策指南：
  • 有明确反模式？ → 仅使用模板
  • 边界模糊？ → 使用方法论中的对比矩阵
  • 用于教学场景？ → 重点展示能揭示误解的近失案例
  • 用于质量控制？ → 专注于失败模式分类法
常见错误：
  1. 仅展示极端负面案例（无指导性的近失案例）
  2. 仅罗列案例无分析（未解释示例未达标的原因）
  3. 选择性纳入简单案例（回避难以界定的边界情况）
  4. 稻草人式负面案例（不切实际的糟糕示例）
  5. 未落地执行（尽管有对比，标准仍模糊不清）
核心洞察： 负面示例的最大价值在于它们“几乎”是正面示例——这些接近达标的情况，能迫使人们明确正面定义中隐藏的细微标准。