Translation, Reframing & Audience Shift

内容翻译、重构与受众适配

Purpose

用途

Adapt content for different audiences while preserving core accuracy—changing tone, depth, emphasis, and framing to match audience expertise, goals, and context.

为不同受众调整内容，同时保留核心准确性——根据受众的专业水平、目标和语境，调整语气、深度、侧重点和框架。

When to Use

适用场景

Invoke this skill when:

Same information needs to reach audiences with different expertise (technical → business, expert → novice)
Content tone/formality needs changing (formal report → casual email, academic → conversational)
Strategic content needs tactical translation (vision → action items, why → how)
Internal content goes external (company docs → customer-facing, jargon → plain language)
Long-form needs compression without losing key points (detailed → summary, comprehensive → highlights)
Medium changes (written → spoken, document → presentation, email → social media)
Cross-cultural or demographic shifts (US → international, industry → industry, generation → generation)
Emphasis needs shifting (highlight different aspects for different stakeholders)

Don't use when:

Content is already appropriate for target audience (no translation needed)
Creating entirely new content (not adapting existing)
Simple copy-editing (grammar, spelling) without audience shift
Translating between human languages (use language translation, not this skill)

调用本技能的场景：

同一信息需要触达不同专业水平的受众（技术→商务、专家→新手）
内容语气/正式程度需要调整（正式报告→随意邮件、学术→口语化）
战略内容需要战术化转换（愿景→行动项、原因→执行方法）
内部内容转为对外内容（公司文档→客户面向内容、行话→平实语言）
长文需要压缩且不丢失核心要点（详细内容→摘要、全面内容→重点提炼）
媒介形式转换（书面→口头、文档→演示文稿、邮件→社交媒体）
跨文化或人群适配（美国→国际、行业→跨行业、代际→代际）
内容侧重点需要调整（为不同利益相关者突出不同内容）

不适用场景：

内容已完全适配目标受众（无需转换）
创作全新内容（而非调整现有内容）
仅需简单文字编辑（语法、拼写修正，无需受众转换）
人类语言间的翻译（请使用语言翻译技能，而非本技能）

What Is It?

技能定义

Translation/reframing adapts content between audiences by preserving semantic accuracy (what is true) while changing presentation (how it's communicated). Four fidelity types:

1. Semantic fidelity (MUST preserve): Core facts, relationships, constraints, implications remain accurate 2. Tonal fidelity (adapt): Formality, emotion, register change to match audience expectations 3. Emphasis fidelity (adapt): What's highlighted vs. backgrounded shifts based on audience priorities 4. Medium fidelity (adapt): Structure, length, format change for different channels/contexts

Example: Technical incident postmortem → Customer status update

Original (Engineers): "Root cause: race condition in distributed lock manager under high concurrency (>5000 req/s). Null pointer dereference when lock timeout occurred before callback registration. Fix: added CAS operation with retry logic, deployed canary to 5% traffic, monitored for 2 hours before full rollout."

Translated (Customers): "What happened: Service slowdown on Jan 15, 2-3pm affecting checkout for some users. Root cause: Timing issue in our system under high traffic. Status: Fixed, monitored, and fully deployed. Prevention: Added safeguards to prevent similar timing issues."

What changed: Technical detail reduced, jargon removed, impact/status emphasized, customer concerns prioritized (what happened, is it fixed, will it happen again). What preserved: Timing, affected functionality, root cause category, resolution status.

Translation/reframing（内容翻译与重构） 指在受众间调整内容时，保留语义准确性（核心事实）同时改变呈现方式（沟通形式）。包含四种保真类型：

1. Semantic fidelity（必须保留）: 核心事实、关联关系、约束条件、隐含信息需保持准确 2. Tonal fidelity（可调整）: 语气、情感、语体需调整以匹配受众预期 3. Emphasis fidelity（可调整）: 内容的突出重点与背景信息需根据受众优先级调整 4. Medium fidelity（可调整）: 内容结构、篇幅、格式需适配不同渠道/语境

示例：技术事件复盘→客户状态更新

原文（面向工程师）： "Root cause: race condition in distributed lock manager under high concurrency (>5000 req/s). Null pointer dereference when lock timeout occurred before callback registration. Fix: added CAS operation with retry logic, deployed canary to 5% traffic, monitored for 2 hours before full rollout."

转换后（面向客户）： "事件说明：1月15日2-3点服务响应缓慢，影响部分用户结账流程。问题根源：高流量下系统出现时序问题。当前状态：问题已修复，且完成全量部署并持续监控。预防措施：已添加防护机制避免同类时序问题再次发生。"

调整点： 移除技术细节与行话，突出影响与状态，优先关注客户关切点（发生了什么、是否已修复、是否会再次发生）。保留点： 事件时间、受影响功能、问题根源类型、解决状态。

Workflow

工作流程

Copy this checklist and track your progress:

Translation & Reframing Progress:
- [ ] Step 1: Analyze source and target audiences
- [ ] Step 2: Identify translation type and constraints
- [ ] Step 3: Apply translation strategy
- [ ] Step 4: Validate fidelity and appropriateness
- [ ] Step 5: Refine and deliver

Step 1: Analyze source and target audiences

Characterize both audiences using Audience Analysis framework (expertise, goals, context, constraints). Identify gap between source and target.

Step 2: Identify translation type and constraints

Classify as: technical↔business, strategic↔tactical, expert↔novice, formal↔informal, long↔short, internal↔external, or cross-cultural. See Common Translation Types for patterns.

Step 3: Apply translation strategy

For simple cases → Use resources/template.md for structured translation. For complex cases (multiple audiences, high stakes, nuanced reframing) → Study resources/methodology.md for advanced techniques.

Step 4: Validate fidelity and appropriateness

Self-assess using resources/evaluators/rubric_translation_reframing_audience_shift.json. Check: semantic accuracy preserved? tone appropriate? emphasis aligned with audience priorities? See Validation section.

Step 5: Refine and deliver

Create

translation-reframing-audience-shift.md

with source, target audience, translated content, and translation rationale. See Delivery Format.

复制以下检查清单并跟踪进度：

Translation & Reframing Progress:
- [ ] Step 1: Analyze source and target audiences
- [ ] Step 2: Identify translation type and constraints
- [ ] Step 3: Apply translation strategy
- [ ] Step 4: Validate fidelity and appropriateness
- [ ] Step 5: Refine and deliver

步骤1：分析源受众与目标受众

使用受众分析框架（专业水平、目标、语境、约束条件）描述源受众与目标受众，识别两者之间的差距。

步骤2：确定转换类型与约束条件

将转换类型归类为：技术↔商务、战略↔战术、专家↔新手、正式↔非正式、长文↔摘要、内部↔外部、跨文化适配。参考常见转换类型中的模式。

步骤3：应用转换策略

简单场景→使用resources/template.md进行结构化转换。复杂场景（多受众、高风险、精细化重构）→学习resources/methodology.md中的高级技巧。

步骤4：验证保真度与适配性

使用resources/evaluators/rubric_translation_reframing_audience_shift.json进行自我评估。检查：语义准确性是否保留？语气是否适配？侧重点是否符合受众优先级？参考验证章节。

步骤5：优化与交付

创建

translation-reframing-audience-shift.md

文档，包含源内容、目标受众、转换后内容及转换依据。参考交付格式。

Audience Analysis

受众分析

Before translating, characterize source and target:

1. Expertise Level

Expert: Domain fluent, comfortable with jargon, wants depth and nuance
Intermediate: Familiar with basics, needs some context, appreciates balance
Novice: No background assumed, needs analogies and plain language, wants practical takeaways

2. Primary Goals

Decision-makers: Want options, trade-offs, recommendations, risks, timelines
Implementers: Want specifics, how-to, constraints, success criteria
Learners: Want understanding, context, mental models, examples
Stakeholders: Want impact, status, next steps, how it affects them

3. Context & Constraints

Time: Busy executives (1-page), deep dives (comprehensive), quick updates (bullets)
Medium: Email (skimmable), presentation (visual + verbal), document (reference)
Familiarity: Internal (shared context) vs. external (assume nothing)
Sensitivity: Public (carefully worded) vs. private (candid)

4. Cultural/Demographic

Language: Native vs. non-native speakers (idiomatic vs. literal)
Generation: Communication norms (emoji use, formality expectations)
Industry: Tech vs. traditional (pacing, references, assumptions)
Geography: US vs. international (date formats, measurement units, cultural references)

Mapping exercise: Source audience is [expertise/goals/context] → Target audience is [expertise/goals/context] → Gap requires [translation strategy].

转换前，先描述源受众与目标受众：

1. 专业水平

Expert（专家）: 精通领域，熟悉行话，需要深度与细节
Intermediate（中级）: 熟悉基础知识，需要一定背景信息，偏好平衡型内容
Novice（新手）: 无前置背景假设，需要类比与平实语言，关注实用要点

2. 核心目标

决策者: 需要选项、权衡、建议、风险、时间线
执行者: 需要具体细节、操作方法、约束条件、成功标准
学习者: 需要理解内容、背景信息、思维模型、示例
利益相关者: 需要影响范围、状态、下一步计划、对自身的影响

3. 语境与约束条件

时间: 忙碌的高管（1页内容）、深度研究（全面内容）、快速更新（要点列表）
媒介: 邮件（易浏览）、演示文稿（视觉+口头）、文档（参考用）
熟悉度: 内部（共享语境） vs 外部（无预设共享信息）
敏感性: 公开（措辞严谨） vs 私有（坦诚直接）

4. 文化/人口统计

语言: 母语 vs 非母语（习语化 vs 直译）
代际: 沟通规范（表情符号使用、正式程度预期）
行业: 科技 vs 传统行业（节奏、参考内容、预设假设）
地域: 美国 vs 国际（日期格式、计量单位、文化参考）

映射练习: 源受众为[专业水平/目标/语境] → 目标受众为[专业水平/目标/语境] → 差距需要[转换策略]。

Common Translation Types

常见转换类型

Technical ↔ Business

技术↔商务内容转换

Technical → Business:

Remove: Implementation details, jargon, code, algorithms
Add: Business value, customer impact, cost/benefit, competitive advantage
Shift emphasis: How it works → Why it matters, Metrics → Outcomes
Example: "Reduced p95 latency from 450ms to 120ms via query optimization" → "Pages load 3x faster, improving customer satisfaction and conversion"

Business → Technical:

Remove: Marketing language, vague goals, buzzwords
Add: Requirements, constraints, acceptance criteria, technical implications
Shift emphasis: Vision → Implementation details, Outcomes → Metrics
Example: "Delight customers with seamless experience" → "Reduce checkout flow to 2 steps, target 95% completion rate, maintain PCI compliance"

技术→商务:

移除: 实现细节、行话、代码、算法
添加: 商业价值、客户影响、成本收益、竞争优势
调整侧重点: 工作原理→重要性、指标→成果
示例: "Reduced p95 latency from 450ms to 120ms via query optimization" → "页面加载速度提升3倍，改善客户满意度与转化率"

商务→技术:

移除: 营销话术、模糊目标、流行术语
添加: 需求、约束条件、验收标准、技术影响
调整侧重点: 愿景→实现细节、成果→指标
示例: "Delight customers with seamless experience" → "将结账流程简化至2步，目标完成率95%，保持PCI合规"

Strategic ↔ Tactical

战略↔战术内容转换

Strategic → Tactical:

Remove: High-level vision, market trends, abstract goals
Add: Specific actions, timelines, owners, dependencies, success metrics
Shift emphasis: Why → What and how, 3-year vision → This quarter's plan
Example: "Become data-driven organization" → "Q1: Instrument 10 key user flows. Q2: Train PMs on analytics. Q3: Establish weekly metrics review."

Tactical → Strategic:

Remove: Granular tasks, individual tickets, daily activities
Add: Themes, rationale, business alignment, cumulative impact
Shift emphasis: Individual work → Portfolio narrative, Tasks → Outcomes
Example: "Fixed 47 bugs, added 12 features, refactored auth" → "Improved product stability and security foundation to support enterprise customers"

战略→战术:

移除: 高层愿景、市场趋势、抽象目标
添加: 具体行动、时间线、负责人、依赖关系、成功指标
调整侧重点: 原因→内容与方法、3年愿景→本季度计划
示例: "Become data-driven organization" → "Q1：为10个关键用户流程埋点。Q2：培训产品经理掌握分析技能。Q3：建立每周指标复盘机制。"

战术→战略:

移除: 细粒度任务、个人工单、日常活动
添加: 主题、依据、业务对齐、累积影响
调整侧重点: 个体工作→整体组合叙事、任务→成果
示例: "Fixed 47 bugs, added 12 features, refactored auth" → "提升产品稳定性与安全基础，为服务企业客户提供支持"

Expert ↔ Novice

专家↔新手内容转换

Expert → Novice:

Remove: Jargon, assumptions of prior knowledge, complex terminology
Add: Analogies, definitions, examples, "why this matters"
Shift emphasis: Nuance → Core concepts, Edge cases → Happy path
Example (Medical): "Idiopathic hypertension, prescribe ACE inhibitor, monitor renal function" → "High blood pressure without clear cause. Medication helps blood vessels relax. Regular kidney checks needed."

Novice → Expert:

Remove: Over-explanations, analogies, hand-holding
Add: Precision, technical terms, caveats, edge cases
Shift emphasis: Simplified model → Accurate complexity
Example: "Make the button easier to click" → "Increase touch target to 44×44pt per iOS HIG, add 8pt padding, ensure 3:1 contrast ratio"

专家→新手:

移除: 行话、前置知识假设、复杂术语
添加: 类比、定义、示例、"内容重要性"
调整侧重点: 细节→核心概念、边缘情况→常规路径
示例（医疗领域）: "Idiopathic hypertension, prescribe ACE inhibitor, monitor renal function" → "特发性高血压（无明确病因的高血压），开具ACE抑制剂药物，需定期检查肾功能"

新手→专家:

移除: 过度解释、类比、引导性内容
添加: 精准表述、技术术语、注意事项、边缘情况
调整侧重点: 简化模型→准确的复杂性
示例: "Make the button easier to click" → "按照iOS HIG标准将触摸目标尺寸提升至44×44pt，添加8pt内边距，确保3:1对比度"

Formal ↔ Informal

正式↔非正式内容转换

Formal → Informal:

Tone: Third person → First person, Passive → Active, Complex → Simple
Structure: Rigid sections → Conversational flow, Citations → Casual mentions
Language: "Furthermore, it is evident" → "Also, you can see"
Example: "The organization has determined that remote work arrangements shall be permitted" → "We're allowing remote work"

Informal → Formal:

Tone: Contractions → Full words ("we're" → "we are"), Casual → Professional
Structure: Loose → Structured sections with clear headers
Language: "Stuff's broken" → "System experiencing degradation"
Example: "Just shipped this cool feature!" → "Released enhanced functionality for improved user experience"

正式→非正式:

语气: 第三人称→第一人称、被动→主动、复杂→简单
结构: 严格分段→对话式流程、引用→随意提及
语言: "Furthermore, it is evident" → "而且你能看到"
示例: "The organization has determined that remote work arrangements shall be permitted" → "我们允许远程办公"

非正式→正式:

语气: 缩写→完整表述（"we're"→"we are"）、随意→专业
结构: 松散→带清晰标题的结构化分段
语言: "Stuff's broken" → "系统出现性能下降"
示例: "Just shipped this cool feature!" → "发布增强功能，提升用户体验"

Long-form ↔ Summary

长文↔摘要转换

Long → Summary:

Structure: Inverted pyramid (most important first), bullet points, highlight key decisions/actions
Remove: Supporting details, full context, exhaustive examples
Preserve: Core findings, recommendations, next steps, critical caveats
Ratios: 50 pages → 1 page (50:1), 1 hour → 5 min (12:1), Comprehensive → Highlights

Summary → Long-form:

Add: Context, methodology, supporting evidence, alternative perspectives
Structure: Introduction → Body → Conclusion, Multiple sections with subheadings
Preserve: Original key points as outline, Expand each with detail

长文→摘要:

结构: 倒金字塔结构（重要内容前置）、要点列表、突出关键决策/行动
移除: 支持细节、完整语境、详尽示例
保留: 核心结论、建议、下一步计划、关键注意事项
比例: 50页→1页（50:1）、1小时→5分钟（12:1）、全面内容→重点提炼

摘要→长文:

添加: 背景信息、方法论、支持证据、不同视角
结构: 引言→正文→结论、带小标题的多分段
保留: 原文核心要点作为大纲，逐一扩展细节

Validation

验证

Delivery Format

交付格式

Create

translation-reframing-audience-shift.md

with:

1. Source Analysis

Original audience: [Expertise, goals, context]
Original content: [Brief excerpt or summary]
Original tone/emphasis: [What was highlighted, how it was framed]

2. Target Analysis

Target audience: [Expertise, goals, context]
Translation type: [Technical→Business, Strategic→Tactical, etc.]
Key constraints: [Length, medium, sensitivity]

3. Translated Content

[Full translated version]
[Formatted for target medium—bullets for emails, sections for docs, etc.]

4. Translation Rationale

What changed: [Jargon removed, emphasis shifted to X, details reduced, analogies added]
What preserved: [Core facts, key implications, critical caveats]
Why: [Audience expertise gap, time constraints, medium requirements, cultural adaptation]

5. Validation Notes

Semantic fidelity: ✓ Core facts accurate
Audience match: ✓ Tone and depth appropriate for [target]
Emphasis: ✓ Highlights [audience priorities]
Limitations: [Any unavoidable compromises, e.g., "Some nuance lost for brevity"]

创建

translation-reframing-audience-shift.md

文档，包含以下内容：

1. 源内容分析

源受众: [专业水平、目标、语境]
源内容: [简短摘录或摘要]
源语气/侧重点: [突出内容、框架方式]

2. 目标受众分析

目标受众: [专业水平、目标、语境]
转换类型: [技术→商务、战略→战术等]
关键约束: [篇幅、媒介、敏感性]

3. 转换后内容

[完整转换后内容]
[适配目标媒介的格式——邮件用要点、文档用分段等]

4. 转换依据

调整内容: [移除行话、突出X内容、简化细节、添加类比等]
保留内容: [核心事实、关键影响、重要注意事项]
原因: [受众专业差距、时间约束、媒介要求、文化适配]

5. 验证说明

语义保真度: ✓ 核心事实准确
受众匹配: ✓ 语气与深度适配[目标受众]
侧重点: ✓ 突出[受众优先级]
局限性: [任何不可避免的妥协，如“为简洁性牺牲部分细节”]

Common Translation Patterns

常见转换模式

"So What?" Test (Technical → Business): Every technical detail answers "so what?" - "Migrated to Kubernetes" → "Auto-scale during traffic spikes, 30% cost reduction" | "OAuth 2.0" → "Enterprise SSO, removes adoption barrier"

"How?" Test (Strategic → Tactical): Every goal answers "how?" - "Improve satisfaction" → "Response <2hr, add help center, NPS survey" | "AI-first company" → "Train PMs (Q1), hire 3 ML engineers (Q2), pilot feature (Q3)"

Analogy Bridge (Expert → Novice): Familiar → Unfamiliar - "Git branching" = essay draft versions | "Microservices" = food trucks not one restaurant | "API rate limiting" = nightclub capacity

Inverted Pyramid (Long → Summary): Most important first - Lede (1-2 sentences) → Key details (2-3 bullets) → Supporting (optional depth)

Code-Switching (Cross-Cultural): Replace cultural references - "Home run" (US) → "Big success" (neutral) | "Fire hose" idiom → "Overwhelming info" (literal) | MM/DD/YYYY → YYYY-MM-DD (ISO)

"那又如何？"测试（技术→商务）: 每个技术细节需回答“那又如何？” - "Migrated to Kubernetes" → "流量高峰时自动扩容，成本降低30%" | "OAuth 2.0" → "企业级单点登录，降低用户使用门槛"

"如何实现？"测试（战略→战术）: 每个目标需回答“如何实现？” - "Improve satisfaction" → "响应时间<2小时、添加帮助中心、NPS调研" | "AI-first company" → "Q1培训产品经理、Q2招聘3名ML工程师、Q3试点AI功能"

类比桥接（专家→新手）: 熟悉事物→陌生事物 - "Git branching" = 论文草稿版本 | "Microservices" = 移动餐车而非单一餐厅 | "API rate limiting" = 夜店容量限制

倒金字塔（长文→摘要）: 重要内容前置 - 导语（1-2句）→关键细节（2-3个要点）→支持内容（可选深度）

语码转换（跨文化）: 替换文化参考内容 - "Home run"（美式）→ "重大成功"（通用） | "Fire hose"习语→ "信息过载"（直译） | MM/DD/YYYY → YYYY-MM-DD（ISO标准）

Quick Reference

快速参考

Resources:

resources/template.md - Structured translation workflow
resources/methodology.md - Advanced techniques for complex/nuanced translation
resources/evaluators/rubric_translation_reframing_audience_shift.json - Quality criteria

Key Principles:

Preserve semantic accuracy - Facts, relationships, implications must remain true
Adapt presentation - Tone, depth, emphasis change for audience
Match audience needs - Expertise level, goals, context, constraints
Test with "would expert confirm?" - Source domain expert validates translation accuracy
Test with "can target act on it?" - Target audience can understand and use it

Red Flags:

Semantic drift (facts become inaccurate through simplification)
Talking down (condescending tone to novices)
Jargon mismatch (too technical or too vague for audience)
Missing "so what?" (technical details without business impact)
Missing "how?" (strategic vision without tactical translation)
Lost nuance (critical caveats omitted for brevity)
Cultural assumptions (idioms, references that exclude target)
Wrong emphasis (highlighting what you find interesting vs. what audience needs)

资源:

resources/template.md - 结构化转换工作流
resources/methodology.md - 复杂/精细化转换的高级技巧
resources/evaluators/rubric_translation_reframing_audience_shift.json - 质量评估标准

核心原则:

保留语义准确性 - 事实、关联关系、隐含信息必须真实
调整呈现方式 - 语气、深度、侧重点需适配受众
匹配受众需求 - 专业水平、目标、语境、约束条件
专家验证测试 - 源领域专家可确认转换内容准确
受众行动测试 - 目标受众可理解并使用转换后的内容

红色警示:

语义偏差（简化导致事实不准确）
居高临下（对新手使用 condescending 语气）
行话不匹配（对受众而言过于专业或过于模糊）
缺失“那又如何？”（技术细节未关联商业价值）
缺失“如何实现？”（战略愿景未转换为战术内容）
丢失细节（为简洁性遗漏关键注意事项）
文化假设（使用目标受众无法理解的习语/参考内容）
侧重点错误（突出自身关注内容而非受众需求）",