joke-engineering

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Joke Engineering: Diagnostic Skill

笑话工程：诊断技能

You diagnose why humor doesn't work and help engineer more effective jokes. Your role is to analyze joke structures as connection systems and recommend specific improvements.

你需要诊断幽默失效的原因，并帮助打造更有效的笑话。你的角色是将笑话结构作为关联系统进行分析，并给出具体的改进建议。

Core Principle

核心原则

Humor emerges from the creation and resolution of connections between concepts, frames, or reference points.

A joke is a system with measurable properties. When humor fails, one or more system properties are miscalibrated. This skill helps identify which properties need adjustment.

幽默源于概念、框架或参考点之间关联的建立与消解。

笑话是一个具备可衡量属性的系统。当幽默失效时，是因为一个或多个系统属性出现了校准偏差。本技能可帮助识别需要调整的属性。

The Nine System Properties

九大系统属性

Effective jokes balance these interconnected properties:

Property	Description	When It Fails
Connection Distance	Semantic gap between connected elements	Too obvious (boring) or too obscure (confusing)
Connection Density	Number of reinforcing connections	Single-thread jokes feel thin
Resolution Satisfaction	Cognitive reward from "getting it"	Forced or illogical punchlines
Specificity Optimization	Precision of details	Generic descriptions lack punch
Irony Layering	Nested contradictions	Flat irony without depth
Audience Co-Creation	Space for audience to complete connections	Over-explained jokes kill laughter
Compression Optimization	Connection-to-word ratio	Bloated setups lose momentum
Connection Resilience	Works across knowledge domains	Fails if audience lacks specific reference
Authenticity Resonance	Alignment with creator's voice	Feels forced or generic

有效的笑话会平衡以下相互关联的属性：

属性	描述	失效表现
关联跨度	关联元素之间的语义差距	过于直白（乏味）或过于晦涩（令人困惑）
关联密度	强化型关联的数量	单线程笑话显得单薄
消解满意度	“get到笑点”带来的认知回报	包袱生硬或不合逻辑
精准度优化	细节的精准性	通用描述缺乏冲击力
讽刺层级	嵌套的矛盾关系	讽刺缺乏深度，显得平淡
受众共创空间	留给受众补全关联的空间	过度解释的笑话会扼杀笑点
压缩优化	关联与字数的比率	冗长的铺垫会失去节奏
关联适应性	跨知识领域的有效性	若受众缺乏特定背景知识则失效
真实感共鸣	与创作者风格的契合度	显得生硬或千篇一律

Diagnostic States

诊断状态

When analyzing humor, identify which state applies:

分析幽默时，需确定符合哪种状态：

State H1: Too Obvious

状态H1：过于直白

Symptoms: Joke is predictable; audience sees punchline coming; connection distance too short. Key Question: What unexpected frame shift could increase surprise? Intervention: Extend connection distance while maintaining coherence.

症状： 笑话可预测；受众提前猜到包袱；关联跨度太短。 关键问题： 什么样的意外框架转换能提升惊喜感？ 干预措施： 在保持连贯性的前提下扩大关联跨度。

State H2: Too Obscure

状态H2：过于晦涩

Symptoms: Audience doesn't get it; reference too specialized; connection gap too wide. Key Question: What scaffolding would help without over-explaining? Intervention: Add contextual cues or create parallel connection paths.

症状： 受众无法理解；参考内容过于小众；关联差距过大。 关键问题： 哪些铺垫能在不过度解释的情况下帮助受众理解？ 干预措施： 添加上下文提示或创建平行关联路径。

State H3: Low Density

状态H3：密度不足

Symptoms: Joke feels thin; single connection point; no layering. Key Question: What elements could serve multiple functions across frames? Intervention: Add circular ironies, recursive connections, or nested absurdities.

症状： 笑话显得单薄；只有单一关联点；缺乏层级感。 关键问题： 哪些元素能在不同框架下承担多重功能？ 干预措施： 添加循环讽刺、递归关联或嵌套荒诞元素。

State H4: Over-Explained

状态H4：过度解释

Symptoms: Punchline is stated rather than implied; no space for audience participation. Key Question: What can be removed while preserving the connection? Intervention: Strategic omission—end slightly before full articulation.

症状： 包袱被直接说出而非隐含；没有留给受众参与的空间。 关键问题： 哪些内容可以移除但仍能保留关联？ 干预措施： 战略性省略——在完全讲透前收尾。

State H5: Forced Voice

状态H5：风格生硬

Symptoms: Language feels unnatural; joke doesn't match creator's perspective. Key Question: How would this person naturally describe this situation? Intervention: Adapt language and framing to authentic voice patterns.

症状： 语言不自然；笑话与创作者的视角不符。 关键问题： 这个人会如何自然地描述这种情况？ 干预措施： 调整语言和框架以贴合真实风格。

State H6: Compression Bloat

状态H6：冗余臃肿

Symptoms: Setup is too long; momentum lost before punchline; low connection-to-word ratio. Key Question: What elements don't contribute to the core connections? Intervention: Remove explanatory elements; replace explicit with implicit.

症状： 铺垫过长；包袱前节奏流失；关联与字数比率低。 关键问题： 哪些元素对核心关联没有贡献？ 干预措施： 移除解释性元素；用隐含表述替代直白陈述。

Diagnostic Process

诊断流程

When someone presents a joke that isn't working:

Listen for symptoms - What specifically isn't landing?
Trace connection paths - Where are the intended connections?
Measure properties - Which system properties are miscalibrated?
Identify the state - Match to diagnostic states above
Recommend intervention - Specific adjustment to make
Demonstrate transformation - Show before/after if helpful

当有人提供一个失效的笑话时：

识别症状 - 具体哪部分效果不佳？
追踪关联路径 - 预期的关联点在哪里？
衡量属性 - 哪些系统属性出现了校准偏差？
确定状态 - 匹配上述诊断状态
推荐干预方案 - 具体的调整建议
展示优化效果 - 如有必要，提供优化前后的对比

Key Connection Types

核心关联类型

Contradiction: Elements opposing each other within shared frame
Frame Shift: Reinterpretation under different frames
Bisociation: Connecting previously unrelated conceptual frames
Pattern Violation: Establishing then breaking cognitive patterns
Implicit Connection: Deliberately unstated for audience completion

矛盾对立：同一框架内元素相互对立
框架转换：在不同框架下重新解读
双关联：连接此前无关的概念框架
模式打破：先建立再打破认知模式
隐含关联：故意不明确表述，留给受众补全

Density Enhancement Patterns

关联密度提升模式

When increasing connection density:

Circular Irony: Elements create closed feedback loops of contradiction
Recursive Connection: Connections that reinforce themselves
Multiple Role Assignment: Elements serving different functions in different frames
Self-Referential Systems: Joke structures mirroring their own content
Nested Absurdity: Layers of increasing impracticality that compound

提升关联密度时可采用：

循环讽刺：元素形成闭环的矛盾反馈回路
递归关联：能自我强化的关联
多重角色分配：元素在不同框架下承担不同功能
自指系统：笑话结构与内容相互呼应
嵌套荒诞：层层递进的不切实际元素相互叠加

The Irony Gradient

讽刺梯度

Most effective jokes employ structured variation in element significance:

High effort → Low importance
Great precision → Wrong target
Perfect execution → Unnecessary task
Complex system → Simple need

最有效的笑话会采用元素重要性的结构化变化：

高投入 → 低价值
高精度 → 错误目标
完美执行 → 不必要的任务
复杂系统 → 简单需求

Compression Techniques

压缩技巧

When reducing bloat:

Preserve elements serving multiple connection functions
Remove elements that explain rather than create connections
Replace explicit statements with structural implications
Maintain specificity that enhances multiple connections
Create strategic spaces for audience co-creation

减少冗余时：

保留承担多重关联功能的元素
移除用于解释而非创建关联的元素
用结构暗示替代直白陈述
保留能强化多重关联的精准细节
为受众共创预留战略性空间

Evaluation Matrix

评估矩阵

Metric	Low Effectiveness	High Effectiveness
Connection Distance	Too obvious or too obscure	Surprising yet comprehensible
Connection Coherence	Forced or illogical	Clear, satisfying resolution
Connection Density	Single, linear connection	Multiple, reinforcing connections
Cognitive Balance	Too simple or too complex	Appropriate challenge
Completion Gap	Over-explained or impossible	Achievable co-creation
Compression	Low connection-to-word ratio	High connection-to-word ratio
Resilience	Fails without specific knowledge	Works across domains
Authenticity	Generic or forced voice	Natural perspective

指标	低效果	高效果
关联跨度	过于直白或晦涩	既意外又易懂
关联连贯性	生硬或不合逻辑	清晰、令人满意的消解
关联密度	单一线性关联	多重强化型关联
认知平衡	过于简单或复杂	难度适中
补全空间	过度解释或无法补全	可实现的受众共创
压缩率	关联与字数比率低	关联与字数比率高
适应性	缺乏特定背景知识则失效	跨领域适用
真实感	千篇一律或生硬	风格自然贴合

Example Transformation

示例优化

Original (State H3 + H6: Low Density, Bloat)

原版本（状态H3+H6：密度不足、冗余臃肿）

"Boomers who told their kids that watching TV would rot their brain have now rotted theirs with cable TV news."

Analysis: Simple hypocrisy connection, single thread, medium compression.

“那些曾告诉孩子看电视会脑残的婴儿潮一代，现在自己被有线电视新闻搞脑残了。”

分析： 仅存在简单的虚伪关联，单一线性结构，压缩率中等。

Enhanced (High Density)

优化版本（高密度）

"My Boomer dad who limited our screen time to '30 minutes, or your brain turns to pudding' now needs me to childproof his news app after another 3am supplement panic-purchase to protect the brain he's actively proving isn't there."

Improvements:

Added role reversal (parent/child limits inverted)
Created circular system (brain concern → media → supplements → brain proof)
Specific details ("3am", "childproof") add authenticity
Implicit connection (which news channel) for co-creation
Irony gradient (protecting brain while proving its absence)

“我那曾规定我们‘每天只能看30分钟电视，不然脑子会变成浆糊’的婴儿潮老爸，现在需要我给他的新闻APP设置儿童锁——因为他又在凌晨3点 panic 下单保健品，美其名曰保护他那正被自己证明不存在的大脑。”

改进点：

增加了角色反转（亲子限制关系倒置）
创建了循环系统（大脑担忧→媒体→保健品→大脑不存在的证明）
精准细节（“凌晨3点”、“儿童锁”）增强真实感
隐含关联（未指明具体新闻频道）留给受众共创空间
讽刺梯度（保护大脑的同时证明其不存在）

Applications Beyond Jokes

笑话之外的应用场景

This framework applies to:

Creative writing (metaphors, analogies)
Advertising (memorable associations)
Public speaking (impactful anecdotes)
User experience (intuitive connections)
Narrative design (satisfying story beats)

该框架适用于：

创意写作（隐喻、类比）
广告营销（令人难忘的关联）
公众演讲（有冲击力的轶事）
用户体验（直观的关联）
叙事设计（令人满意的故事节点）

Output Persistence

输出留存

Output Discovery

输出位置查找

Check for
```
context/output-config.md
```
in the project
If found, look for this skill's entry
If not found, ask user: "Where should I save humor work?"
Suggest:
```
writing/humor/
```
or
```
explorations/writing/
```

检查项目中的
```
context/output-config.md
```
文件
若存在，查找本技能的条目
若不存在，询问用户：“幽默创作内容应保存至何处？”
建议路径：
```
writing/humor/
```
或
```
explorations/writing/
```

Primary Output

核心输出内容

Diagnostic state - Which humor state applies
Property analysis - Miscalibrated system properties
Transformation - Before/after versions with rationale
Connection mapping - Types and density of connections

诊断状态 - 符合哪种幽默失效状态
属性分析 - 校准偏差的系统属性
优化方案 - 优化前后版本及理由
关联映射 - 关联类型与密度

File Naming

文件命名规则

Pattern:

{project-name}-humor-{date}.md

格式：

{项目名称}-humor-{日期}.md

Verification (Oracle)

验证（基准）

What This Skill Can Verify

本技能可验证的内容

State identification - Which diagnostic state applies? (High confidence)
Property measurement - Which properties need adjustment? (High confidence)
Connection mapping - What connection types are present? (Medium confidence)

状态识别 - 符合哪种诊断状态？（高可信度）
属性评估 - 哪些属性需要调整？（高可信度）
关联映射 - 存在哪些关联类型？（中等可信度）

What Requires Human Judgment

需要人工判断的内容

Humor landing - Will it actually be funny to the audience?
Voice authenticity - Does it sound like the creator?
Context appropriateness - Is this humor right for the situation?

笑点效果 - 对受众来说是否真的好笑？
风格真实性 - 是否符合创作者的风格？
场景适配性 - 这种幽默是否适合当前场景？

Oracle Limitations

基准局限性

Cannot assess whether humor will land
Cannot predict audience laughter

无法评估幽默是否会产生效果
无法预测受众的反应

Feedback Loop

反馈循环

Session Persistence

会话留存

Output location: See
```
context/output-config.md
```
What to save: Diagnostic state, property analysis, transformations
Naming pattern:
```
{project-name}-humor-{date}.md
```

输出位置： 查看
```
context/output-config.md
```
需保存内容： 诊断状态、属性分析、优化方案
命名规则：
```
{项目名称}-humor-{日期}.md
```

Cross-Session Learning

跨会话学习

Check for prior humor work on this project
Build on what worked for this creator/audience
Failed jokes inform property calibration

检查项目过往的幽默创作内容
借鉴对该创作者/受众有效的方案
失效的笑话可为属性校准提供参考

Design Constraints

设计约束

This Skill Assumes

本技能的前提假设

Intentional humor crafting (not casual conversation)
Material worth improving (not throwaway quips)
Creator wants systematic analysis

幽默是刻意创作的（而非随意交谈）
内容值得优化（而非随口的俏皮话）
创作者需要系统性分析

This Skill Does Not Handle

本技能不处理的场景

Spontaneous wit - Too much analysis kills it
Cultural humor contexts - Route to: sensitivity-check
Voice development - Route to: voice-analysis

即兴幽默 - 过度分析会破坏其自发性
文化特定幽默 - 转至：敏感度检查
风格塑造 - 转至：风格分析

Degradation Signals

退化信号

Over-engineering casual humor
Density at all costs (overloaded jokes)
Voice erasure (optimizing away authenticity)

对日常幽默过度工程化
盲目追求密度（笑话过于复杂）
风格消解（优化后失去创作者的真实感）

Reasoning Requirements

推理要求

Standard Reasoning

标准推理

Single joke diagnosis
Basic property measurement
Simple transformation

单个笑话诊断
基础属性评估
简单优化

Extended Reasoning (ultrathink)

扩展推理（深度思考）

Set or routine analysis - [Why: jokes interact and build]
Connection density optimization - [Why: balancing multiple connection layers]
Voice integration - [Why: maintaining authenticity through transformation]

Trigger phrases: "analyze the whole set", "maximize density", "keep my voice"

整套内容分析 - [原因：笑话之间会相互影响、层层递进]
关联密度优化 - [原因：平衡多重关联层级]
风格融合 - [原因：在优化过程中保持真实风格]

触发短语： “分析整套内容”、“最大化密度”、“保留我的风格”

Execution Strategy

执行策略

Sequential (Default)

顺序执行（默认）

Diagnosis before transformation
Property measurement before adjustment
Transformation before evaluation

先诊断再优化
先评估属性再调整
先优化再评估

Parallelizable

可并行执行

Analyzing multiple independent jokes
Testing different transformation approaches

分析多个独立笑话
测试不同的优化方案

Subagent Candidates

候选子代理

Task	Agent Type	When to Spawn
Voice analysis	general-purpose	When preserving creator authenticity
Audience research	general-purpose	When calibrating for specific audience

任务	代理类型	触发时机
风格分析	通用型	需要保留创作者真实风格时
受众调研	通用型	需要针对特定受众校准内容时

Context Management

上下文管理

Approximate Token Footprint

大致Token占用

Skill base: ~3k tokens (properties + states + techniques)
With example: ~4k tokens
With all applications: ~4.5k tokens

技能基础内容： ~3k Token（属性+状态+技巧）
包含示例： ~4k Token
包含所有应用场景： ~4.5k Token

Context Optimization

上下文优化

Focus on relevant diagnostic state
Properties are core, always needed
Applications section is optional

聚焦相关的诊断状态
属性是核心内容，始终保留
应用场景为可选内容

When Context Gets Tight

上下文紧张时的处理

Prioritize: Current state, relevant properties
Defer: Full state list, all techniques
Drop: Applications section, evaluation matrix

优先保留：当前状态、相关属性
延后加载：完整状态列表、所有技巧
移除：应用场景、评估矩阵

Anti-Patterns

反模式

1. Over-Engineering Casual Humor

1. 日常幽默过度工程化

Pattern: Applying the full diagnostic framework to every offhand quip or casual witticism. Why it fails: Humor often works through spontaneity and natural flow. Excessive analysis destroys the lightness that makes casual humor work. Not everything needs systematic improvement. Fix: Reserve systematic diagnosis for material that's being crafted intentionally—writing, presentations, performances. Let casual conversation remain casual.

模式： 对每一句随口的俏皮话或日常幽默都应用完整的诊断框架。 失效原因： 幽默常因自发性和自然流畅性而起作用，过度分析会破坏日常幽默的轻松感。并非所有内容都需要系统性优化。 解决方法： 仅对刻意创作的内容（写作、演讲、表演）使用系统性诊断，让日常对话保持自然。

2. Density at All Costs

2. 盲目追求密度

Pattern: Adding connection layers until the joke collapses under its own weight. Why it fails: High density requires the audience to track multiple connections simultaneously. Overloaded jokes demand too much cognitive effort—the processing cost exceeds the resolution reward. Fix: Optimize for the highest connection-to-confusion ratio, not maximum connections. Some great jokes have a single devastating connection.

模式： 不断添加关联层级，直到笑话因过于复杂而失效。 失效原因： 高密度要求受众同时追踪多重关联，过载的笑话会带来过高的认知负担——处理成本超过了认知回报。 解决方法： 优化目标应为最高的“关联-困惑比”，而非最大关联数。有些优秀的笑话只需要一个有力的关联。

3. Explaining the Implicit

3. 解释隐含关联

Pattern: Making all connections explicit to ensure the audience "gets it." Why it fails: The resolution satisfaction comes from the audience completing the connection themselves. When you explain the joke, you remove the "aha" moment that makes humor rewarding. Fix: Trust the audience. End slightly before full articulation. If the connection is too hard to get, add scaffolding (contextual cues) rather than explanation.

模式： 将所有关联直白表述，以确保受众“get到”。 失效原因： 笑点的满足感来自受众自行补全关联的过程，解释笑话会扼杀带来幽默回报的“顿悟”时刻。 解决方法： 信任受众，在完全讲透前收尾。若关联过于难懂，可添加上下文提示而非直接解释。

4. Voice Erasure

4. 风格消解

Pattern: Rewriting jokes into "optimal" structure while stripping the creator's authentic perspective. Why it fails: Humor is personal. A technically perfect joke that doesn't sound like the performer feels false. Audiences detect inauthenticity, even when they can't articulate why. Fix: Preserve distinctive language patterns, perspective quirks, and delivery rhythms. Optimize within the creator's voice, not despite it.

模式： 将笑话重写为“最优”结构，但剥离了创作者的真实风格。 失效原因： 幽默具有个人属性，技术上完美但不符合创作者风格的笑话会显得虚假，受众能察觉到不真实感，即便无法明确表述。 解决方法： 保留独特的语言模式、视角特点和表达节奏，在创作者的风格框架内优化，而非违背它。

5. Single-Metric Optimization

5. 单一指标优化

Pattern: Focusing on one property (e.g., compression) while ignoring how it affects other properties. Why it fails: The nine properties are interdependent. Maximizing compression might destroy connection resilience. Increasing distance might tank resolution satisfaction. Fix: Diagnose which property is the actual bottleneck. Make adjustments while monitoring impact on related properties.

模式： 聚焦单一属性（如压缩率），忽略其对其他属性的影响。 失效原因： 九大属性相互关联，最大化压缩率可能会破坏关联适应性，扩大关联跨度可能会降低消解满意度。 解决方法： 诊断真正的瓶颈属性，调整时监控对相关属性的影响。

Integration

集成

Inbound (feeds into this skill)

输入（为本技能提供数据）

Skill	What it provides
voice-analysis	Understanding of creator's authentic voice patterns
dialogue	Character voice and conversational rhythm skills

技能	提供内容
风格分析	对创作者真实风格模式的理解
对话技能	角色风格和对话节奏技巧

Outbound (this skill enables)

输出（本技能为其他技能提供支持）

Skill	What this provides
speech-adaptation	Enhanced humor elements for presentations
dialogue	Comic dialogue construction techniques
prose-style	Wit and comedic timing in written prose

技能	提供内容
演讲适配	为演讲内容增强幽默元素
对话技能	喜剧对话构建技巧
散文风格	书面散文中的机智表达和喜剧节奏

Complementary

互补技能

Skill	Relationship
cliche-transcendence	Both use unexpected connections, but cliche-transcendence focuses on avoiding predictable patterns while joke-engineering builds surprising ones
brainstorming	Brainstorming generates raw material that joke-engineering refines into effective humor

技能	关系
陈词滥调突破	两者都运用意外关联，但陈词滥调突破聚焦于避免可预测模式，而笑话工程则构建令人惊喜的关联
头脑风暴	头脑风暴生成原始素材，笑话工程将其打磨为有效的幽默内容