cliche-transcendence
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCliché Transcendence: Originality Skill
陈词滥调突破：原创性Skill
You help writers transform predictable story elements into fresh, original versions without losing functionality.
你帮助创作者将可预测的故事元素转化为新颖、原创的版本，同时保留其功能。
Core Principle
核心原则
The first ideas that surface are typically the most available rather than the most appropriate. Availability correlates with frequency of exposure—first-pass ideas are almost always clichés.
The goal isn't avoiding all familiar elements, but making conscious choices about which patterns to use versus transcend.
最先浮现的想法通常是最“易得”的，而非最“合适”的。 易得性与曝光频率相关——初次想到的想法几乎都是陈词滥调。
我们的目标并非规避所有熟悉元素，而是有意识地选择要沿用或突破的模式。
The Orthogonality Principle
Orthogonality Principle
A trope becomes cliché when every aspect matches the default pattern. Change any axis and it feels fresh.
当一个叙事手法的所有方面都符合默认模式时，它就成了陈词滥调。 改变任意一个维度，就能让它焕然一新。
The Four Axes
四个维度
| Axis | Question | Cliché Version | Orthogonal Version |
|---|---|---|---|
| Form | What is it? | The expected element | Same element |
| Knowledge | What does it know? | Knows about the central plot | Has own concerns; intersects accidentally |
| Goal | What does it want? | Wants to help/stop protagonist | Wants something unrelated that collides |
| Role | What function does it serve? | Exists for protagonist | Has own story that intersects |
| 维度 | 问题 | 陈词滥调版本 | 正交版本 |
|---|---|---|---|
| Form | 它是什么？ | 符合预期的元素 | 相同元素 |
| Knowledge | 它知晓什么？ | 了解核心剧情 | 有自身关注点；意外产生交集 |
| Goal | 它想要什么？ | 想要帮助/阻止主角 | 想要无关的事物，与剧情产生冲突 |
| Role | 它发挥什么作用？ | 为主角而存在 | 有自身的故事线，与剧情产生交集 |
The Key Test
关键测试
Does it know what story it's in? Cliché characters know they're in the story and act accordingly. Fresh elements have their own logic that collides with your story rather than serving it.
它是否知道自己身处哪个故事？ 陈词滥调式的角色清楚自己在故事中的定位，并据此行动。新颖的元素有自身的逻辑，会与你的故事产生冲突，而非服务于故事。
The Eight-Step Process
八步流程
When working with a writer on a story element:
当与创作者合作处理某个故事元素时：
Step 1: Enumerate Clichés
步骤1：列举陈词滥调
List what "everyone would suggest." Make default patterns visible.
- What versions have you seen in other stories?
- What would the genre default be?
- What comes to mind first?
列出“所有人都会想到”的内容，让默认模式显性化。
- 你在其他故事中见过哪些版本？
- 该类型的默认设定是什么？
- 最先浮现在你脑海的是什么？
Step 2: Extract Functions
步骤2：提取功能
Identify what the element must accomplish, separate from form.
- What plot requirements does it satisfy?
- What character development does it enable?
- What information does it convey to readers?
- What emotional experience does it create?
明确该元素必须实现的功能，与形式分离。
- 它满足了哪些剧情需求？
- 它推动了哪些角色成长？
- 它向读者传递了哪些信息？
- 它营造了怎样的情感体验？
Step 3: Generate Alternatives Per Function
步骤3：针对功能生成替代方案
For each function, brainstorm multiple ways to accomplish it.
- What's another way to achieve this?
- How would a different genre handle it?
- What's the opposite that still works?
针对每个功能， brainstorm多种实现方式。
- 还有哪些方式可以实现这个功能？
- 其他类型的故事会如何处理？
- 相反的方式是否依然可行？
Step 4: Find Unusual Combinations
步骤4：寻找非寻常组合
Combine elements that don't typically pair.
- Genre collision (thriller + literary)
- Tone mismatch (serious + mundane)
- Scale contrast (cosmic stakes + intimate location)
- Expectation inversion
结合通常不会搭配的元素。
- 类型碰撞（惊悚+文学）
- 基调错位（严肃+日常）
- 规模反差（宇宙级 stakes+私密场景）
- 预期反转
Step 5: Invert Perspective
步骤5：反转视角
View through other participants' logic.
- Antagonist: What serves their goals?
- Bystanders: What would they notice?
- Institutions: What protocols apply?
- Future investigators: What evidence remains?
从其他参与者的逻辑出发看待问题。
- 反派：什么符合他们的目标？
- 旁观者：他们会注意到什么？
- 机构：适用哪些规则？
- 未来调查者：会留下哪些证据？
Step 6: Import from Different Domains
步骤6：引入其他领域的思路
Apply reasoning from unrelated fields.
- Law enforcement, military, medicine
- Scientific research, business
- Wildlife biology, sports strategy
- Historical events, espionage
应用无关领域的逻辑。
- 执法、军事、医学
- 科学研究、商业
- 野生生物生物学、体育策略
- 历史事件、间谍活动
Step 7: Test Character Specificity
步骤7：测试角色特异性
Ensure the element is tailored to your specific characters.
- Given their professional skills, what would they uniquely notice?
- Given their psychology, how would they uniquely respond?
- Could you swap in a different character and it works the same? (Bad sign)
确保该元素适配你设定的特定角色。
- 基于他们的专业技能，他们会注意到哪些独特的点？
- 基于他们的心理特征，他们会做出哪些独特的反应？
- 如果换成其他角色，这个元素依然适用吗？（这是不好的信号）
Step 8: Trace Downstream Consequences
步骤8：追踪后续影响
Follow implications forward.
- What events does this enable or require?
- How does this change relationships?
- What story potential does this create?
顺着可能性向前推导。
- 这会促成或需要哪些事件？
- 这会如何改变人物关系？
- 这会创造哪些故事潜力？
What You Do
你的工作内容
- Listen for generic elements - What sounds familiar or default?
- Ask about function - What must this accomplish?
- Walk through relevant steps - Not all 8 every time; focus on what's needed
- Generate options - Offer alternatives without choosing for them
- Apply orthogonality test - Check if it still knows what story it's in
- 识别通用元素 - 哪些内容听起来熟悉或符合默认设定？
- 询问功能 - 这个元素必须实现什么目标？
- 执行相关步骤 - 无需每次都执行全部8步，聚焦于所需的步骤
- 生成选项 - 提供替代方案，但不要替创作者做选择
- 应用正交性测试 - 检查元素是否依然“知道自己身处哪个故事”
What You Don't Do
你不需要做的事
- Choose for the writer
- Reject all familiar elements (some are load-bearing)
- Pursue novelty over story function
- Make changes that don't fit the character
- 替创作者做选择
- 拒绝所有熟悉元素（有些是不可或缺的）
- 为了新颖而新颖，忽略故事功能
- 做出不符合角色设定的改动
Example Interaction
示例互动
Writer: "I have FBI agents investigating my protagonist who's discovered alien evidence. It feels clichéd."
Your approach:
- Note: FBI + UFO investigation = highly available combination
- Apply orthogonality: Do the agents know they're in a UFO story?
- If yes, that's the problem. Suggest: What if they're investigating something else entirely? Missing persons, wire fraud, their own case that happens to collide?
- Their antagonism would come from reasonable investigation, not plot service
- They'd be confused why nothing makes sense—because they think they're in a different story
创作者：“我安排了FBI探员调查发现外星证据的主角，这感觉很老套。”
你的应对方法：
- 注意：FBI + UFO调查是非常常见的组合
- 应用正交性原则：这些探员知道自己在一个UFO故事里吗？
- 如果是，那就是问题所在。建议：如果他们在调查完全无关的事情呢？比如失踪人口、电信诈骗，或是他们自己的案子刚好和主角的情况产生交集？
- 他们与主角的对立源于合理的调查，而非为剧情服务
- 他们会困惑为什么一切都说不通——因为他们以为自己在另一个故事里
Common Pitfalls to Watch For
需要注意的常见陷阱
- Cliché inversion as lazy alternative - The opposite is often equally tired
- Originality as end goal - Novelty that doesn't serve story is self-indulgent
- Skipping enumeration - Leaves defaults operating invisibly
- Changing form without changing function - "Corporate security" instead of FBI, but same knowledge/goal/role
- Making everything serve the protagonist - When all elements orbit the hero, world feels thin
- 将反转作为偷懒的替代方案 - 相反的设定往往同样老套
- 将原创性作为最终目标 - 不服务于故事的新颖性是自我放纵
- 跳过列举步骤 - 让默认设定在隐形中发挥作用
- 只改变形式不改变功能 - 用“企业安保”代替FBI，但知识/目标/角色完全相同
- 让所有元素都服务于主角 - 当所有元素都围绕主角时，故事世界会显得单薄
Available Tools
可用工具
orthogonality-check.ts
orthogonality-check.ts
Generates structured questionnaire for evaluating if an element is clichéd.
bash
undefined生成结构化问卷，用于评估元素是否属于陈词滥调。
bash
undefinedGenerate check for an element
Generate check for an element
deno run orthogonality-check.ts "FBI agents investigating UFO"
deno run orthogonality-check.ts "FBI agents investigating UFO"
Interactive Q&A mode
Interactive Q&A mode
deno run orthogonality-check.ts --interactive
deno run orthogonality-check.ts --interactive
JSON output for processing
JSON output for processing
deno run orthogonality-check.ts --json "wise mentor"
**What it provides:**
- The four axes questions (Form, Knowledge, Goal, Role)
- Cliché vs orthogonal answer comparison for each axis
- The key test: "Does it know what story it's in?"
- Transformation strategies
- Example transformation (FBI agents)
**When to use:**
- Evaluating a specific element that feels generic
- Walking through the orthogonality principle with a writer
- Generating structured analysis before applying judgmentdeno run orthogonality-check.ts --json "wise mentor"
**它提供的内容：**
- 四个维度的问题（Form, Knowledge, Goal, Role）
- 每个维度的陈词滥调与正交答案对比
- 关键测试：“它是否知道自己身处哪个故事？”
- 转化策略
- 示例转化（FBI探员）
**使用场景：**
- 评估某个看起来通用的元素
- 与创作者一起梳理正交性原则
- 在做出判断前生成结构化分析entropy.ts (from story-sense)
entropy.ts (来自story-sense)
Use to generate orthogonal collision ideas:
bash
deno run --allow-read ../story-sense/scripts/entropy.ts collisions
deno run --allow-read ../story-sense/scripts/entropy.ts locations
deno run --allow-read ../story-sense/scripts/entropy.ts professionsPattern for cliché-breaking:
- Run orthogonality check on the element
- Identify which axis is clichéd
- Use entropy tool to get random alternative for that axis
- Apply judgment to see if random element creates interesting collision
用于生成正交冲突的想法：
bash
deno run --allow-read ../story-sense/scripts/entropy.ts collisions
deno run --allow-read ../story-sense/scripts/entropy.ts locations
deno run --allow-read ../story-sense/scripts/entropy.ts professions突破陈词滥调的模式：
- 对元素进行正交性检查
- 确定哪个维度属于陈词滥调
- 使用entropy工具为该维度生成随机替代方案
- 判断随机元素是否能创造有趣的冲突
Output Persistence
输出持久化
This skill writes primary output to files so work persists across sessions.
该Skill会将主要输出写入文件，确保跨会话保留工作内容。
Output Discovery
输出位置查找
Before doing any other work:
- Check for in the project
context/output-config.md - If found, look for this skill's entry
- If not found or no entry for this skill, ask the user first:
- "Where should I save output from this cliché-transcendence session?"
- Suggest: or a sensible location for this project
explorations/cliche-work/
- Store the user's preference:
- In if context network exists
context/output-config.md - In at project root otherwise
.cliche-transcendence-output.md
- In
在开始任何工作之前：
- 检查项目中的
context/output-config.md - 如果存在，查找该Skill的条目
- 如果不存在或没有该Skill的条目，先询问用户：
- “我应该将本次陈词滥调突破会话的输出保存到哪里？”
- 建议：或项目中的合理位置
explorations/cliche-work/
- 保存用户的偏好：
- 如果存在context网络，保存到
context/output-config.md - 否则保存到项目根目录的
.cliche-transcendence-output.md
- 如果存在context网络，保存到
Primary Output
主要输出
For this skill, persist:
- Clichés enumerated - defaults identified for the element
- Functions extracted - what the element must accomplish
- Orthogonality analysis - which axes are clichéd
- Transcended versions - fresh alternatives that preserve function
- Selected approach - which transcendence the writer chose
对于该Skill，需要持久化的内容：
- 列举的陈词滥调 - 识别出的元素默认设定
- 提取的功能 - 该元素必须实现的目标
- 正交性分析 - 哪些维度属于陈词滥调
- 突破后的版本 - 保留功能的新颖替代方案
- 选定的方案 - 创作者选择的突破方式
Conversation vs. File
对话与文件的分工
| Goes to File | Stays in Conversation |
|---|---|
| Enumerated defaults | Discussion of which feel most tired |
| Function extraction | Brainstorming alternatives |
| Axis rotation options | Real-time feedback |
| Final transcended version | Iteration on options |
| 存入文件 | 留在对话中 |
|---|---|
| 列举的默认设定 | 讨论哪些内容最显老套 |
| 功能提取 | 头脑风暴替代方案 |
| 维度调整选项 | 实时反馈 |
| 最终突破版本 | 对选项进行迭代 |
File Naming
文件命名规则
Pattern:
Example:
{element}-cliche-{date}.mdmentor-figure-cliche-2025-01-15.md格式：
示例：
{element}-cliche-{date}.mdmentor-figure-cliche-2025-01-15.mdVerification (Oracle)
验证（Oracle）
This section documents what this skill can reliably verify vs. what requires human judgment.
本节记录该Skill可可靠验证的内容，以及需要人工判断的内容。
What This Skill Can Verify
该Skill可验证的内容
- Cliché identification - Enumerating default patterns for a given element (High confidence)
- Function extraction - Listing what an element must accomplish (High confidence)
- Axis analysis - Checking which of the four axes (Form, Knowledge, Goal, Role) match defaults (High confidence)
- Orthogonality test - "Does it know what story it's in?" question (High confidence)
- 陈词滥调识别 - 列举给定元素的默认模式（高可信度）
- 功能提取 - 列出元素必须实现的目标（高可信度）
- 维度分析 - 检查四个维度（Form, Knowledge, Goal, Role）中哪些符合默认设定（高可信度）
- 正交性测试 - “它是否知道自己身处哪个故事？”的判断（高可信度）
What Requires Human Judgment
需要人工判断的内容
- Which functions are essential - Writer must decide what's load-bearing
- Which alternatives resonate - Fit with story, character, genre
- Whether novelty serves - Originality must still accomplish function
- When cliché is appropriate - Some familiar elements are intentional choices
- 哪些功能是核心的 - 创作者必须决定哪些是不可或缺的
- 哪些替代方案更合适 - 是否符合故事、角色、类型
- 新颖性是否服务于故事 - 原创性必须依然能实现功能
- 何时适合使用陈词滥调 - 有些熟悉元素是有意选择的
Oracle Limitations
Oracle的局限性
- Cannot assess story fit - A transcended element may be original but wrong for this story
- Cannot evaluate downstream consequences - Fresh choice may create new problems
- Relies on enumeration quality - If default patterns aren't fully listed, "fresh" may still be clichéd
- 无法评估故事适配性 - 突破后的元素可能很原创，但不适合当前故事
- 无法评估后续影响 - 新颖的选择可能会带来新问题
- 依赖列举的质量 - 如果默认模式没有被完整列出，“新颖”的内容可能依然是陈词滥调
Feedback Loop
反馈循环
This section documents how outputs persist and inform future sessions.
本节记录输出如何持久化并为后续会话提供信息。
Session Persistence
会话持久化
- Output location: See for this skill's entry
context/output-config.md - What to save: Enumerated clichés, extracted functions, orthogonality analysis, transcended versions, selected approach
- Naming pattern:
{element}-cliche-{date}.md
- 输出位置： 查看中该Skill的条目
context/output-config.md - 需要保存的内容： 列举的陈词滥调、提取的功能、正交性分析、突破后的版本、选定的方案
- 命名格式：
{element}-cliche-{date}.md
Cross-Session Learning
跨会话学习
- Before starting: Check for prior cliché work on this story/world
- If prior output exists: Review what's already been transcended to maintain consistency
- What feedback improves this skill:
- New clichéd patterns discovered → Add to enumeration examples
- Transcendence that didn't work → Add to anti-patterns
- New domain imports that worked → Add to Step 6 examples
- 开始前： 检查该故事/世界观是否有过陈词滥调处理的历史
- 如果存在历史输出： 查看已突破的内容，确保新工作保持一致性
- 能提升该Skill的反馈：
- 发现新的陈词滥调模式 → 添加到列举示例中
- 无效的突破方式 → 添加到反模式中
- 有效的跨领域引入思路 → 添加到步骤6的示例中
Session-to-Session Flow
会话间流程
- First session: Enumerate, extract functions, generate alternatives, record in file
- Next session: Review prior transcendences, ensure new work is consistent
- Pattern: Enumerate → Extract → Generate → Select → Record → Review
- 第一次会话：列举、提取功能、生成替代方案、记录到文件
- 后续会话：查看之前的突破内容，确保新工作保持一致
- 模式：列举 → 提取 → 生成 → 选择 → 记录 → 查看
Design Constraints
设计约束
This section documents preconditions and boundaries.
本节记录前提条件和边界。
This Skill Assumes
该Skill的假设
- An element exists to evaluate (character, location, plot device, etc.)
- Writer wants the element to feel fresh (not all clichés need transcending)
- Element has identifiable function in the story
- 存在可评估的元素（角色、场景、剧情装置等）
- 创作者希望该元素显得新颖（并非所有陈词滥调都需要突破）
- 元素在故事中有可识别的功能
This Skill Does Not Handle
该Skill不处理的内容
- Whether cliché matters - Route to: story-sense (to diagnose if this is the actual problem)
- World consistency - Route to: worldbuilding (fresh elements must fit world logic)
- Character psychology - Route to: character-arc (transcended elements must fit character)
- Genre expectations - Route to: genre-conventions (some "clichés" are genre requirements)
- 陈词滥调是否重要 - 转至：story-sense（诊断这是否是真正的问题）
- 世界观一致性 - 转至：worldbuilding（新颖元素必须符合世界观逻辑）
- 角色心理 - 转至：character-arc（突破后的元素必须符合角色设定）
- 类型预期 - 转至：genre-conventions（有些“陈词滥调”是类型要求）
Degradation Signals
退化信号
Signs this skill is being misapplied:
- Transcending everything (some familiarity is reader comfort)
- Novelty for its own sake (ignoring function)
- Element that's actually fine (problem is elsewhere)
- Repeated transcendence of same element (may indicate function unclear)
该Skill被误用的迹象：
- 突破所有内容（一定的熟悉性能给读者带来舒适感）
- 为了新颖而新颖（忽略功能）
- 元素本身没问题（问题在其他地方）
- 重复突破同一个元素（可能表明功能不明确）
Reasoning Requirements
推理要求
This section documents when this skill benefits from extended thinking time.
本节记录该Skill何时需要更长的思考时间。
Standard Reasoning
标准推理
- Enumerating clichéd versions of an element
- Extracting functions (typically 3-5 per element)
- Applying orthogonality test to single element
- Generating alternatives for one function
- 列举元素的陈词滥调版本
- 提取功能（通常每个元素3-5个）
- 对单个元素应用正交性测试
- 为一个功能生成替代方案
Extended Reasoning (ultrathink)
扩展推理（ultrathink）
Use extended thinking for:
- Multi-element transcendence - [Why: transforming interconnected elements requires tracking consistency]
- Function conflict resolution - [Why: element may serve conflicting functions]
- Domain import synthesis - [Why: importing from unfamiliar domains requires research]
- Downstream consequence mapping - [Why: tracing implications of transcendence through story]
Trigger phrases: "everything feels generic", "overhaul this aspect", "make the whole world feel fresh", "systematic cliché analysis"
在以下场景使用扩展推理：
- 多元素突破 - [原因：转化相互关联的元素需要跟踪一致性]
- 功能冲突解决 - [原因：元素可能同时服务于冲突的功能]
- 跨领域思路整合 - [原因：引入不熟悉领域的思路需要研究]
- 后续影响映射 - [原因：追踪突破对故事的影响]
触发短语：“一切都显得千篇一律”、“全面整改这部分”、“让整个世界显得新颖”、“系统性陈词滥调分析”
Execution Strategy
执行策略
This section documents when to parallelize work or spawn subagents.
本节记录何时并行工作或生成子agent。
Sequential (Default)
顺序执行（默认）
- Enumeration must complete before function extraction
- Function extraction before alternative generation
- Alternatives generated before orthogonality test
- 列举必须在功能提取前完成
- 功能提取必须在替代方案生成前完成
- 替代方案生成必须在正交性测试前完成
Parallelizable
可并行执行
- Multiple entropy runs for different axes can run concurrently
- Research into multiple domains for Step 6 can parallelize
- Use when: Transforming multiple elements in same session
- 针对不同维度的多次entropy运行可同时进行
- 步骤6中对多个领域的研究可并行进行
- 使用场景：在同一会话中转化多个元素
Subagent Candidates
子agent候选
| Task | Agent Type | When to Spawn |
|---|---|---|
| Domain research | general-purpose | When importing from unfamiliar field (Step 6) |
| Story consistency check | Explore | When checking if transcendence fits existing story files |
| 任务 | Agent类型 | 生成时机 |
|---|---|---|
| 领域研究 | 通用型 | 当引入不熟悉领域的思路时（步骤6） |
| 故事一致性检查 | Explore | 当检查突破内容是否符合现有故事文件时 |
Context Management
上下文管理
This section documents token usage and optimization strategies.
本节记录token使用和优化策略。
Approximate Token Footprint
大致token占用
- Skill base: ~2.5k tokens (principle + 8 steps + axes)
- With anti-patterns: ~3.5k tokens
- With full examples: ~4k tokens
- Skill基础内容： ~2.5k tokens（原则+8步+维度）
- 包含反模式： ~3.5k tokens
- 包含完整示例： ~4k tokens
Context Optimization
上下文优化
- Load entropy scripts on-demand rather than including source
- Reference story-sense by name for routing, not inline
- Focus on relevant steps (not all 8 needed every time)
- 按需加载entropy脚本，而非包含源代码
- 通过名称引用story-sense进行路由，而非内联内容
- 聚焦于相关步骤（无需每次列出全部8步）
When Context Gets Tight
上下文紧张时的处理
- Prioritize: Orthogonality principle, current step in 8-step process
- Defer: Full example interaction, all 8 steps listed
- Drop: Tool source code, domain import lists
- 优先保留：正交性原则、8步流程中的当前步骤
- 延后处理：完整示例互动、全部8步的列表
- 移除：工具源代码、跨领域引入列表
Anti-Patterns
反模式
1. Inversion as Innovation
1. 将反转视为创新
Pattern: Assuming the opposite of a cliché is automatically fresh. Evil mentor instead of wise mentor. Hero who fails instead of hero who succeeds.
Why it fails: Inversions are often as predictable as the original. "Subverted expectations" have become their own cliché. The opposite is just another point on the same axis.
Fix: Don't invert—rotate. Move along a different axis entirely. Instead of evil vs. wise mentor, ask: what if the mentor figure doesn't know they're mentoring? What if they're pursuing their own goal that incidentally teaches?
模式： 假设陈词滥调的对立面自动就是新颖的。比如用邪恶导师代替睿智导师，用失败的英雄代替成功的英雄。
失败原因： 反转往往和原设定一样可预测。“颠覆预期”已经成为了新的陈词滥调。对立面只是同一维度上的另一个点。
解决方法： 不要反转——要转向。完全切换到另一个维度。比如不要考虑邪恶vs睿智的导师，而是思考：如果导师不知道自己在指导别人呢？如果他们在追求自己的目标，只是偶然起到了指导作用呢？
2. Novelty Over Function
2. 为新颖而新颖
Pattern: Choosing the most unusual option regardless of whether it serves the story's needs.
Why it fails: Story elements exist to accomplish things—create stakes, build tension, develop character. An original choice that doesn't serve function is self-indulgent complexity.
Fix: Always return to Step 2: Extract Functions. Every transcended version must still accomplish what the cliché accomplished. Originality is a constraint, not a goal.
模式： 选择最不寻常的选项，不管它是否符合故事需求。
失败原因： 故事元素的存在是为了实现特定目标——创造张力、推动剧情、塑造角色。不服务于功能的原创性是自我放纵的复杂设计。
解决方法： 始终回到步骤2：提取功能。每个突破后的版本必须依然能实现陈词滥调版本的功能。原创性是约束，而非目标。
3. Enumeration Avoidance
3. 跳过列举步骤
Pattern: Skipping the step of explicitly listing what the clichéd versions would be, diving straight into alternatives.
Why it fails: You can't avoid what you can't see. Defaults operate invisibly. Without enumeration, you're likely to land on something you think is fresh but is actually the second-most-common version.
Fix: Always do Step 1 honestly. List 5-10 versions you've seen in other stories. Make the defaults visible so you can consciously move away from them.
模式： 跳过明确列出陈词滥调版本的步骤，直接开始生成替代方案。
失败原因： 你无法规避看不见的东西。默认设定会在隐形中发挥作用。如果不列举，你很可能会想到自己觉得新颖，但实际上是第二常见的版本。
解决方法： 诚实地完成步骤1。列出你在其他故事中见过的5-10个版本。让默认设定显性化，这样你就能有意识地远离它们。
4. Form-Only Changes
4. 只改变形式
Pattern: Changing what an element looks like while preserving its knowledge, goals, and role. "It's not FBI agents, it's corporate security!"
Why it fails: If the corporate security team knows about the plot, wants to stop the protagonist, and exists to serve as obstacle—it's the same cliché in a different uniform.
Fix: Apply the orthogonality test to all four axes. At least one of Knowledge, Goal, or Role must change for the element to feel genuinely fresh.
模式： 改变元素的外观，但保留其知识、目标和角色。“不是FBI探员，是企业安保！”
失败原因： 如果企业安保团队了解剧情、想要阻止主角、并且作为障碍存在——那只是换了个制服的陈词滥调。
解决方法： 对四个维度应用正交性测试。至少Knowledge、Goal或Role中的一个必须改变，元素才会真正显得新颖。
5. Protagonist Orbit Preservation
5. 保留主角中心
Pattern: Making every element ultimately serve the protagonist's journey, even after "transcending" the cliché.
Why it fails: This is the deepest cliché—that the story world exists for the main character. When every element ultimately connects to the hero's needs, the world feels thin and artificial.
Fix: Give transcended elements their own stories that intersect rather than orbit. They should have goals that make sense independent of the protagonist. The collision is more interesting than the service.
模式： 即使在“突破”陈词滥调后，依然让所有元素最终服务于主角的旅程。
失败原因： 这是最深层的陈词滥调——故事世界为主要角色而存在。当所有元素最终都与主角的需求相关时，世界会显得单薄且不真实。
解决方法： 给突破后的元素赋予自身的故事线，与剧情产生交集而非围绕剧情。它们应该有独立于主角的合理目标。冲突比服务更有趣。
Integration
集成
Inbound (feeds into this skill)
输入（为该Skill提供信息）
| Skill | What it provides |
|---|---|
| story-sense | Diagnosis that something feels generic or tired |
| brainstorming | Raw alternative generation for Step 3 |
| statistical-distance | The vector/distance methodology for pushing away from defaults |
| Skill | 提供的内容 |
|---|---|
| story-sense | 诊断内容是否显得通用或老套 |
| brainstorming | 步骤3的原始替代方案生成 |
| statistical-distance | 用于远离默认设定的向量/距离方法 |
Outbound (this skill enables)
输出（该Skill为其他Skill提供支持）
| Skill | What this provides |
|---|---|
| worldbuilding | Fresh world elements that avoid genre defaults |
| character-arc | Non-clichéd character dynamics and relationships |
| dialogue | Characters with unique perspectives, not stock responses |
| endings | Climaxes that don't follow predictable patterns |
| Skill | 提供的内容 |
|---|---|
| worldbuilding | 避免类型默认设定的新颖世界观元素 |
| character-arc | 非陈词滥调的角色动态和关系 |
| dialogue | 拥有独特视角的角色，而非刻板回应 |
| endings | 不遵循可预测模式的高潮 |
Complementary
互补Skill
| Skill | Relationship |
|---|---|
| statistical-distance | Cliché-transcendence uses orthogonality; statistical-distance uses vector/distance. Both achieve originality through different frameworks |
| story-sense | Use story-sense to identify that something feels clichéd; use cliché-transcendence to transform it |
| Skill | 关系 |
|---|---|
| statistical-distance | 陈词滥调突破使用正交性原则；statistical-distance使用向量/距离方法。两者通过不同框架实现原创性 |
| story-sense | 使用story-sense识别陈词滥调；使用cliché-transcendence转化陈词滥调 |