SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsdesign-content-direction

design-content-direction

Design & creation

View repository

Updated 10-16 09:45

About this skill

Direction Design — director design

Entry/Exit

  • Entry: deck : or strongly presentation-oriented content needs defined presentation progression and staging
  • Exit: page transition intent, emotional progression, speech pacing, and presentation arrangement finalized
  • Points to: Script mainline → design-content-script; page implementation → design-content-layout
  • Output path: build-content-writing or build-content-layout(downstream build skill)
  • Prerequisite loading: CANON.md + design-workflow-design

When not to use

  • Ordinary long-form reading material
  • Visual drafts that only do static layout and do not involve narrative progression

Core principles

  1. Sequence Creates Meaning
  2. Reveal Is a Design Decision
  3. Emotion Needs Control
  4. Speaker Load Matters
  5. Every Transition Must Earn Its Keep

Best practice inputs

First read references/design-best-practices.md and references/design-inspiration-catalog.md, and write director-related evidence into 02-design.md 's Design References / Pattern Synthesis / Adopt / Reject。

Scan focus:

  • Enterprise Product Patterns: page order and reveal patterns for pitch decks, launches, product demos, and briefing materials
  • Official Systems / Platform Rules: presentation medium, duration, brand tone, animation/export constraints
  • Methods / Theory / Style Schools: dramatic tension, reveal order, pacing control, speaker load management
  • Anti-patterns / Verification: uniform effort on every page, no turns, animation replacing narrative, multiple functions on one page
  • Local Project Truth: audience task, live/asynchronous reading scenarios, page count limits, speaker capability, and material boundaries; project root DESIGN.md(if present, as director constraint reference)

Direction design must explain why the progression is this way; page order cannot be written as a material list.

Process

Step 1: Define the presentation goal

  • What the audience should feel at each stage
  • When to build tension
  • When to deliver conclusions
  • ✅ Verification point: Does the presentation goal clearly distinguish "the feeling at each stage" rather than a vague "make the audience understand"?

Step 2: Plan the progression

  • How pages relay to one another
  • Which content should be on its own page
  • Which content must appear as a group
  • ✅ Verification point: Does the relay between pages have a clear narrative intent (e.g., "a turn is created here to produce surprise") rather than just content arrangement?

Step 3: Control pacing

  • Fast cuts or pauses
  • Where explanation space is needed
  • Where only conclusions are given without expansion
  • ✅ Verification point: Does the shift between fast and slow pacing have specific purpose annotations (e.g., "fast-cut 3 pages here to create urgency, then pause 1 page to digest")?

Step 4: Record presentation constraints

  • Whether speaker notes carry details
  • Whether pages need animation/progressive disclosure
  • Live reading vs projected speech
  • ✅ Verification point: Are the presentation constraints specific to the scenario (e.g., "projected speech, each page stays 30-60 seconds") rather than "we'll deal with it later"?

Output contract

Write to 02-design.md：

  • Speech pacing
  • Page order / paragraph progression
  • Emotional progression / turning points
  • Adopt / Reject (director mode)
  • Do-not-do list

Validation Failure Handling

Failure Scenario Handling Method
Page order is just laying out information Rewrite the progression logic, add turns and reveal order
Pacing too dense Split pages or let speaker notes carry the details
Pacing too loose Merge pages, strengthen the throughline
Progression pattern has no evidence Supplement with a best-practice scan, clearly write Adopt / Reject
Emotional progression conflicts with the storyline Return to the story spine to align the emotional rhythm, delete turns that do not serve the throughline

Common Excuses

Excuse Reality Consequence
"Once the pages are made, the rhythm will come" A page order without director design is just arranging materials. No director design → page order becomes flat information layout, the audience's attention drops off after 5-8 pages, and key turning points are drowned out
"Animation can wait until later" Whether to progressively disclose affects the narrative structure. Animation not planned in advance → structural reveals require reordering pages, reworking 30-50% of the deck content
"Talk about a little on every page" Evenly distributing information usually equals having no focus. Even effort → a page order with no focus leaves the audience unable to identify the core proposition, and presentation persuasiveness drops by 40%+

Good and Bad Examples

✅ Good: Evidence-driven director decisions

演示目标:
- 前 3 页: 让观众感到"这是我们都知道的痛点"（共鸣）
- 第 4-6 页: 制造张力——"直觉解是错的"（转折）
- 第 7-8 页: 交付结论和行动（收束）

推进逻辑:
- 页 1→2: 快切（痛点堆叠制造紧迫感）
- 页 3→4: 停顿（转折前需要消化空间）
- 页 4→5→6: 快切3页（证据密集，不容犹豫）
- 页 6→7: 停顿（结论前让听众准备接受）
- 页 7→8: 单页行动清单（收束干净）

Adopt: 问题-转折-收束三段推进（来源: Methods / Theory / Style Schools #5）
Reject: 匀速信息排列（与演示目标"制造张力再收束"冲突）

❌ Bad: Abstract templates with no concrete decisions

演示目标: 让观众了解产品
推进逻辑: 按功能列表排列
节奏: 正常速度
呈现约束: (未写)
不做清单: (未写)
→ 没有导演意图，没有情绪推进，没有证据支撑

Output Template

Director design output should be written into 02-design.md with the following structure:

## Direction Design — [内容名称]

### 演示目标
| 阶段 | 期望感受 | 关键动作 |
|------|---------|---------|
| [阶段 1] | [共鸣/紧迫/惊讶...] | [认同痛点/接受转折/决定行动] |

### 页序推进
| 页码 | 内容 | 推进意图 | 节奏 |
|------|------|---------|------|
| [1-3] | [内容概述] | [制造共鸣] | 快切 |
| [4-6] | [内容概述] | [制造转折] | 快切 |
| [7-8] | [内容概述] | [收束行动] | 停顿 |

### 情绪推进 / 转折点
- 共鸣点: [页码和描述]
- 张力点: [页码和描述]
- 转折点: [页码和描述]
- 收束点: [页码和描述]

### 呈现约束
- 场景: [现场投屏 / 异步阅读 / 混合]
- speaker notes 承担: [哪些细节]
- 渐进披露需求: [哪些页面需要动画]

### Adopt / Reject（导演模式）
| 模式 | 来源 | 决定 | 理由 |
|------|------|------|------|
| [模式 A] | [来源层] | Adopt | [具体理由] |
| [模式 B] | [来源层] | Reject | [冲突点] |

### 不做清单
- [不做项 1]: [冲突来源或证据]
- [不做项 2]: [冲突来源或证据]

Red Flags — STOP

  • Start making the deck without a progression logic
  • Missing director best-practice scan or Adopt / Reject
  • Emotional progression and storyline fight each other
  • One page carries multiple stage functions
  • Degrade director design into "add animation or not"

Validation Checklist

  • Presentation goal is clear
  • Page order progression is reasonable
  • Pacing control is clear
  • Presentation constraints are clear
  • Director decisions have been traced back to source evidence or Local Project Truth
  • Written into 02-design.md