content-engine

affaan-m ｜ 行銷與 SEO ｜ 原文 ｜ MIT

把同一份素材改編成各平台原生風格的貼文、腳本與內容系統

---
name: content-engine
description: 為 X、LinkedIn、TikTok、YouTube、電子報，以及跨多平台改編的行銷活動，建立符合各平台原生風格的內容系統。適用於使用者想要社群貼文、串文、腳本、內容日曆，或把同一份來源素材乾淨地改編到各平台時。
metadata:
  origin: ECC
---

# Content Engine

打造符合各平台原生風格的內容，又不把作者真實的語氣壓扁成平台上的垃圾文。

## When to Activate

- 撰寫 X 貼文或串文
- 草擬 LinkedIn 貼文或發布更新
- 為短影片或 YouTube 解說影片寫腳本
- 把文章、podcast、示範、文件或內部筆記改編成公開內容
- 圍繞某個產品、洞見或敘事，建立發布序列或長期的內容系統

## Non-Negotiables

1. 從來源素材出發，不要用通用的貼文公式。
2. 調整的是平台的格式，不是人設。
3. 一則貼文只承載一個真正的主張。
4. 具體勝過形容詞。
5. 除非使用者明確要求，否則不要用誘導互動的手法。

## Source-First Workflow

起草之前，先確認來源素材的集合：
- 已發表的文章
- 筆記或內部備忘錄
- 產品示範
- 文件或 changelog
- 逐字稿
- 截圖
- 同一位作者之前的貼文

如果使用者要特定的語氣，寫之前先從真實範例建立語氣檔案。
當語氣一致性要跨越不只一份產出時，以 `brand-voice` 作為標準流程。

## Voice Handling

`brand-voice` 是標準的語氣層。

在這些情況下先執行它：

- 有多個下游產出
- 使用者明確在意寫作風格
- 內容屬於發布、對外聯繫，或對聲譽敏感的

在這裡重複使用它產出的 `VOICE PROFILE`，不要再另外建立第二套語氣模型。
如果使用者特別要 Affaan / ECC 的語氣，仍然把 `brand-voice` 當作事實的來源，並把手邊最好的即時或來源衍生素材餵給它。

## Hard Bans

下面這些，一律刪掉重寫：
- "In today's rapidly evolving landscape"
- "game-changer"、"revolutionary"、"cutting-edge"
- "here's why this matters"，除非後面馬上接著具體的內容
- 以 LinkedIn 風格的問題結尾，只為了騙留言
- 在 LinkedIn 上刻意裝隨性
- 來源素材裡沒有的假互動填充

## Platform Adaptation Rules

### X

- 以最強的主張、成品或張力開場
- 如果來源的語氣是精簡的，就保持精簡
- 寫串文的話，每一則貼文都必須推進論點
- 不要用觀眾不需要的脈絡來灌水

### LinkedIn

- 只展開到讓小眾圈子以外的人看得懂的程度
- 除非來源素材真的是反思性的，否則不要把它寫成假的心得文
- 不要有企業勵志的腔調
- 不要堆砌讚美，不要「旅程（journey）」之類的贅詞

### Short Video

- 圍繞視覺順序和佐證重點來寫腳本
- 開頭幾秒要呈現結果、問題或重點
- 不要寫那種寫在紙上比放在螢幕上好聽的旁白

### YouTube

- 早點呈現結果或張力
- 依論點或推進順序組織，不要塞填充的段落
- 只有在有助於清楚表達時才用章節

### Newsletter

- 以重點、衝突或成品開場
- 不要把第一段拿來暖身
- 每個段落都要加入新的東西

## Repurposing Flow

1. 挑出錨點素材。
2. 抽出 3 到 7 個原子主張或場景。
3. 依尖銳度、新穎度和佐證程度排序。
4. 每份產出指派一個強的想法。
5. 為每個平台調整結構。
6. 去掉平台形狀的填充內容。
7. 通過品質關卡。

## Deliverables

被要求做行銷活動時，回傳：
- 語氣需要配合時，一份簡短的語氣檔案
- 核心切入角度
- 符合各平台原生風格的草稿
- 只有對執行有幫助時，才附上發文順序
- 發布之前必須補上的缺口

## Quality Gate

交付之前：
- 每份草稿聽起來都像預定的作者，而不是平台的刻板印象
- 每份草稿都包含真正的主張、佐證重點或具體的觀察
- 沒有殘留的通用炒作用語
- 沒有殘留的假誘導互動
- 除非使用者要求，否則各平台之間沒有重複的文案
- 任何 CTA 都是掙來的，而且經過使用者核准

## Related Skills

- `brand-voice`：來源衍生的語氣檔案
- `crosspost`：各平台專屬的發布
- `x-api`：取得最近的貼文，以及發布已核准的 X 內容

---
name: content-engine
description: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
metadata:
  origin: ECC
---

# 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

## 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.

## 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.

## 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.

## 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

## Platform Adaptation Rules

### 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

- 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

- 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.

## 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

## 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