Back to Details

content-engine

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Content Engine

内容引擎

Build platform-native content without flattening the author's real voice into platform slop.
打造平台原生内容，避免将作者的真实风格沦为千篇一律的平台模板化内容。

When to Activate

适用场景

  • writing X posts or threads
  • drafting LinkedIn posts or launch updates
  • scripting short-form video or YouTube explainers
  • repurposing articles, podcasts, demos, docs, or internal notes into public content
  • building a launch sequence or ongoing content system around a product, insight, or narrative
  • 撰写X帖子或推文串
  • 起草LinkedIn帖子或发布更新
  • 创作短视频脚本或YouTube讲解视频脚本
  • 将文章、播客、演示、文档或内部笔记改编为公开内容
  • 围绕产品、见解或叙事构建发布序列或持续内容体系

Non-Negotiables

核心准则

  1. Start from source material, not generic post formulas.
  2. Adapt the format for the platform, not the persona.
  3. One post should carry one actual claim.
  4. Specificity beats adjectives.
  5. No engagement bait unless the user explicitly asks for it.
  1. 从源素材出发，而非通用帖子模板。
  2. 适配平台格式，而非刻意塑造人设。
  3. 单篇帖子仅承载一个明确观点。
  4. 具体表述优于空泛形容词。
  5. 除非用户明确要求，否则不得使用引流话术。

Source-First Workflow

源素材优先工作流

Before drafting, identify the source set:
  • published articles
  • notes or internal memos
  • product demos
  • docs or changelogs
  • transcripts
  • screenshots
  • prior posts from the same author
If the user wants a specific voice, build a voice profile from real examples before writing. Use 
brand-voice
as the canonical workflow when voice consistency matters across more than one output.
撰写前，先确定源素材范围：
  • 已发布文章
  • 笔记或内部备忘录
  • 产品演示
  • 文档或更新日志
  • 文字转录稿
  • 截图
  • 同一作者的过往帖子
若用户需要特定风格，先从真实案例构建风格档案再开始撰写。 当多个输出内容需要保持风格一致性时，使用
brand-voice
作为标准工作流。

Voice Handling

风格处理

brand-voice
is the canonical voice layer.
Run it first when:
  • there are multiple downstream outputs
  • the user explicitly cares about writing style
  • the content is launch, outreach, or reputation-sensitive
Reuse the resulting 
VOICE PROFILE
here instead of rebuilding a second voice model. If the user wants Affaan / ECC voice specifically, still treat 
brand-voice
as the source of truth and feed it the best live or source-derived material available.
brand-voice
是标准风格层。
在以下场景中优先使用：
  • 存在多个下游输出内容
  • 用户明确关注写作风格
  • 内容涉及发布、推广或品牌声誉相关场景
在此处复用生成的
VOICE PROFILE
，无需重新构建第二个风格模型。 若用户明确需要Affaan / ECC风格，仍需以
brand-voice
为基准，并提供可用的最佳实时或源素材衍生资料。

Hard Bans

禁用内容

Delete and rewrite any of these:
  • "In today's rapidly evolving landscape"
  • "game-changer", "revolutionary", "cutting-edge"
  • "here's why this matters" unless it is followed immediately by something concrete
  • ending with a LinkedIn-style question just to farm replies
  • forced casualness on LinkedIn
  • fake engagement padding that was not present in the source material
出现以下内容需删除并重写：
  • "In today's rapidly evolving landscape"
  • "game-changer"、"revolutionary"、"cutting-edge"
  • "here's why this matters"（除非紧随其后有具体内容）
  • 以LinkedIn式提问结尾只为获取回复
  • 在LinkedIn上刻意营造随意风格
  • 源素材中不存在的虚假引流内容

Platform Adaptation Rules

平台适配规则

X

X

  • open with the strongest claim, artifact, or tension
  • keep the compression if the source voice is compressed
  • if writing a thread, each post must advance the argument
  • do not pad with context the audience does not need
  • 以最有力的观点、素材或矛盾点开篇
  • 若源素材风格凝练，则保持这种凝练性
  • 若撰写推文串，每一条都需推进论点
  • 不得添加目标受众不需要的背景信息

LinkedIn

LinkedIn

  • expand only enough for people outside the immediate niche to follow
  • do not turn it into a fake lesson post unless the source material actually is reflective
  • no corporate inspiration cadence
  • no praise-stacking, no "journey" filler
  • 仅做必要扩展，确保非细分领域用户也能理解
  • 除非源素材本身具有反思性，否则不得写成虚假经验帖
  • 避免企业励志式语调
  • 不得堆砌赞美之词，不得添加“成长历程”类冗余内容

Short Video

短视频

  • script around the visual sequence and proof points
  • first seconds should show the result, problem, or punch
  • do not write narration that sounds better on paper than on screen
  • 围绕视觉序列和实证要点编写脚本
  • 开头几秒需展示结果、问题或亮点
  • 撰写的旁白需适合屏幕呈现，而非仅适合书面阅读

YouTube

YouTube

  • show the result or tension early
  • organize by argument or progression, not filler sections
  • use chaptering only when it helps clarity
  • 尽早展示结果或矛盾点
  • 按论点或逻辑递进组织内容，而非填充无关章节
  • 仅在有助于提升清晰度时使用章节划分

Newsletter

新闻通讯

  • open with the point, conflict, or artifact
  • do not spend the first paragraph warming up
  • every section needs to add something new
  • 以核心观点、冲突或素材开篇
  • 第一段不得用于暖场铺垫
  • 每个章节都需提供新信息

Repurposing Flow

内容复用流程

  1. Pick the anchor asset.
  2. Extract 3 to 7 atomic claims or scenes.
  3. Rank them by sharpness, novelty, and proof.
  4. Assign one strong idea per output.
  5. Adapt structure for each platform.
  6. Strip platform-shaped filler.
  7. Run the quality gate.
  1. 选定核心素材。
  2. 提取3至7个独立观点或场景。
  3. 按尖锐度、新颖度和实证性排序。
  4. 为每个输出内容分配一个核心观点。
  5. 针对各平台调整结构。
  6. 删除平台模板化冗余内容。
  7. 执行质量审核。

Deliverables

交付成果

When asked for a campaign, return:
  • a short voice profile if voice matching matters
  • the core angle
  • platform-native drafts
  • posting order only if it helps execution
  • gaps that must be filled before publishing
当用户要求提供营销活动方案时，需返回：
  • 若需匹配风格，则提供简短风格档案
  • 核心角度
  • 平台原生内容草稿
  • 发布顺序（仅当有助于执行时提供）
  • 发布前需填补的内容缺口

Quality Gate

质量审核关卡

Before delivering:
  • every draft sounds like the intended author, not the platform stereotype
  • every draft contains a real claim, proof point, or concrete observation
  • no generic hype language remains
  • no fake engagement bait remains
  • no duplicated copy across platforms unless requested
  • any CTA is earned and user-approved
交付前需确认：
  • 每份草稿都符合目标作者的风格，而非平台刻板模板
  • 每份草稿都包含明确观点、实证要点或具体观察
  • 无通用炒作类语言
  • 无虚假引流话术
  • 各平台内容无重复（除非用户要求）
  • 任何行动号召（CTA）均合理且经用户认可

Related Skills

相关技能

  • brand-voice
    for source-derived voice profiles
  • crosspost
    for platform-specific distribution
  • x-api
    for sourcing recent posts and publishing approved X output
  • brand-voice
    ：用于基于源素材构建风格档案
  • crosspost
    ：用于平台特定分发
  • x-api
    ：用于获取最新帖子并发布已获批的X内容