presentation-creator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Presentation Creator

演示文稿创建工具

Bold, minimal slide decks with a story underneath: spine to final QA.

IS: slide decks end to end: story spine, slide sequence, slide copy, visual system, speaker notes, investor pitch decks, and decks built as a web app; output as Marp markdown (default), Slidev or reveal.js markdown, or a Next.js deck app.
IS NOT: producing or editing the
```
.pptx
```
/
```
.potx
```
file itself (external
```
pptx
```
skill where installed; hand it the finished outline, copy, and notes from this skill), charts inside a slide (external
```
dataviz
```
where installed), long-form prose (external
```
ghostwriter
```
with platform
```
blog
```
), marketing copy outside slides (
```
copywriting
```
), or product UI (
```
ui-design
```
).

打造兼具大胆极简风格与内在故事线的幻灯片组：从故事主线到最终质检全流程覆盖。

可完成： 端到端幻灯片组制作：故事主线、幻灯片序列、幻灯片文案、视觉系统、演讲备注、投资人Pitch Deck，以及制作为Web应用的幻灯片组；输出格式默认为Marp markdown，也支持Slidev或reveal.js markdown，或Next.js幻灯片应用。
不可完成： 生成或编辑.pptx/.potx文件本身（已安装外部
```
pptx
```
技能时可交由其处理；需将本技能生成的最终大纲、文案和备注提供给该技能）、幻灯片内的图表（已安装外部
```
dataviz
```
技能时可交由其处理）、长篇散文（需使用搭配platform
```
blog
```
的外部
```
ghostwriter
```
技能）、幻灯片以外的营销文案（使用
```
copywriting
```
技能）、产品UI设计（使用
```
ui-design
```
技能）。

Workflow

工作流程

Track this checklist:

text

Presentation progress:
- [ ] Step 1: Gather context (audience, setting, venue, three messages, output format)
- [ ] Step 2: Write the story spine and the ending (references/story-structure.md)
- [ ] Step 3: Outline the slide sequence (references/outline-structure.md)
- [ ] Step 4: Write slide copy (references/writing-slides.md; pitch decks: references/pitch-decks.md instead)
- [ ] Step 5: Design colour, type, and layout (references/visual-design.md)
- [ ] Step 6: Write speaker notes (references/speaker-notes.md); skip for a deck sent without a presenter
- [ ] Step 7: Emit the deck in the chosen format (references/output-formats.md or references/web-deck.md)
- [ ] Step 8: QA pass, output the slide-by-slide review table

遵循以下检查清单：

text

演示文稿进度：
- [ ] 步骤1：收集背景信息（受众、场景、场地、核心三要点、输出格式）
- [ ] 步骤2：撰写故事主线与结尾（参考references/story-structure.md）
- [ ] 步骤3：规划幻灯片序列（参考references/outline-structure.md）
- [ ] 步骤4：撰写幻灯片文案（参考references/writing-slides.md；Pitch Deck请替换为参考references/pitch-decks.md）
- [ ] 步骤5：设计色彩、字体与布局（参考references/visual-design.md）
- [ ] 步骤6：撰写演讲备注（参考references/speaker-notes.md；若为无需演讲者的异步演示文稿可跳过此步骤）
- [ ] 步骤7：以选定格式输出幻灯片组（参考references/output-formats.md或references/web-deck.md）
- [ ] 步骤8：质检环节，输出逐幻灯片审查表格

Step 1: Gather context

步骤1：收集背景信息

Establish these, asking only for what the brief does not answer:

Audience: internal (shared context, be direct) vs. external (build credibility, define terms).
Setting: live talk, recorded/async, or a pitch deck sent to investors and read without you.
Venue: a dark room or a large hall takes the dark system; a bright meeting room, daylight, or a deck that doubles as a handout takes a light palette. Ask when unknown, because it decides Step 5.
The three messages: what the audience must remember after the deck.
Output format: Marp markdown unless there is a reason otherwise. A web app when the deck should run a live demo or live at a URL. A
```
.pptx
```
when the user names the file or a house template, produced by the external
```
pptx
```
skill from this skill's outline, copy, and notes. Decide now, not at Step 7: the format sets the type and notes mechanics in Steps 5 and 6.

Route by setting:

Live talk, internal, or recorded deck → Steps 2-8 in order.
Investor pitch deck sent to be read → references/pitch-decks.md first. Its 10-slide framework replaces Step 3's outline, and its async copy rules replace
```
writing-slides.md
```
at Step 4 (do not load both: their density rules contradict). Step 2 still applies in compressed form; the spine is what stops a pitch reading as a feature list. Skip Step 6. The same company pitching live on a demo-day stage is a presented deck: use the standard path with the pitch framework as its outline.

确认以下信息，仅询问需求中未明确的内容：

受众： 内部员工（共享背景信息，表述直接） vs 外部人员（需建立可信度、定义术语）。
场景： 现场演讲、录播/异步演示，或发送给投资人自行阅读的Pitch Deck。
场地： 暗室或大型会场采用深色视觉系统；明亮会议室、自然光环境，或需同时作为讲义的幻灯片组采用浅色配色方案。未知时需询问，此信息将决定步骤5的设计方向。
核心三要点： 受众看完幻灯片组后必须记住的三个关键信息。
输出格式： 默认为Marp markdown，除非有特殊理由。若幻灯片组需运行实时演示或可通过URL访问，采用Web应用格式；若用户指定文件或公司模板，需使用外部
```
pptx
```
技能，将本技能生成的大纲、文案和备注提供给该技能以生成.pptx文件。需在步骤1确定格式，而非步骤7：格式将决定步骤5和6中的字体与备注机制。

根据场景分流：

现场演讲、内部分享或录播演示文稿 → 按步骤2-8依次执行。
发送给投资人自行阅读的Pitch Deck → 优先参考references/pitch-decks.md。其10页框架将替代步骤3的大纲，异步文案规则将替代步骤4的
```
writing-slides.md
```
（请勿同时参考两者：两者的内容密度规则相互矛盾）。步骤2仍需简化执行；故事主线是避免Pitch Deck沦为功能列表的关键。跳过步骤6。若为公司在演示日现场进行的Pitch演讲，则属于有演讲者的演示文稿：采用标准流程，以Pitch框架作为大纲。

Steps 2-7: Build the deck

步骤2-7：制作幻灯片组

Read each step's reference when you reach it:

Step	Reference	Covers
2. Story	references/story-structure.md	The spine template, writing the ending first, taking a position, stakes, the unstick move
3. Outline	references/outline-structure.md	Narrative flow, 12 slide types, section colours, outline output format
4. Write	references/writing-slides.md, replaced by references/pitch-decks.md on the pitch path	Headline patterns, body rules, copy per slide type, before/after examples
5. Design	references/visual-design.md	Two colour systems, contrast thresholds, fluid and fixed type scales, layout patterns, slide type to layout mapping
6. Notes	references/speaker-notes.md	Per-slide note structure, delivery cues, notes by slide type
7. Emit	references/output-formats.md	Marp syntax and export, Slidev and reveal.js equivalents, the `pptx` handoff, where notes live in each
7. Emit (web)	references/web-deck.md	Route-per-slide structure, navigation, layout primitives, motion, live demos
Changing this skill	`evals/evals.json`	Behavioural scenarios with assertions, plus should-trigger and near-miss routing prompts. Never loads during a user task

Read

web-deck.md

only after the copy exists. Primitives designed before the outline get shaped around slide 3 and fight every slide after it.

执行到对应步骤时阅读相关参考文档：

步骤	参考文档	涵盖内容
2. 故事线	references/story-structure.md	故事主线模板、先写结尾、明确立场、核心冲突、破局点
3. 大纲	references/outline-structure.md	叙事流程、12种幻灯片类型、章节色彩、大纲输出格式
4. 文案撰写	references/writing-slides.md，Pitch流程替换为references/pitch-decks.md	标题范式、正文规则、分类型幻灯片文案、前后对比示例
5. 设计	references/visual-design.md	两种色彩系统、对比度阈值、流体与固定字体比例、布局范式、幻灯片类型与布局映射
6. 备注	references/speaker-notes.md	单幻灯片备注结构、演讲提示、分类型幻灯片备注
7. 输出	references/output-formats.md	Marp语法与导出、Slidev和reveal.js等效格式、与pptx技能的交接、各格式中备注的存储位置
7. 输出（Web应用）	references/web-deck.md	单幻灯片对应路由结构、导航、布局基础组件、动效、实时演示
修改本技能	`evals/evals.json`	带断言的行为场景，以及触发条件与近似错误分流提示。用户任务执行期间不会加载此文档

仅在文案完成后阅读

web-deck.md

。先设计基础组件再规划大纲会导致组件仅适配第3页幻灯片，后续幻灯片难以匹配。

Step 8: QA pass (produces evidence)

步骤8：质检环节（产出验证依据）

Review every slide and output a table. This is the deliverable that proves the deck is done, not a "looks good" sign-off:

markdown

| # | Slide | 3-sec test | One message | Spine beat | Layout | Colour | Contrast |
|---|-------|-----------|-------------|------------|--------|--------|----------|
| 1 | Title | pass | pass | once upon a time | full statement | teal | 12.6:1 |

3-sec test: parseable in three seconds at arm's length (Duarte's glance test). Cut copy on any failure until it passes. Pitch decks are read, not glanced: substitute "makes sense forwarded with no context".
One message: exactly one idea per slide; split slides carrying two.
Spine beat: which beat of the Step 2 spine this slide serves. A slide serving none is a fact you found interesting; cut it.
Layout: the layout should change when the slide's job changes. Flag a run of three or more identical layouts and keep it only when the section is deliberately a list.
Colour: the section accent, or the full-bleed palette, matching what Step 5 assigned.
Contrast: the smallest text on the slide against its background. 4.5:1 for body and captions, 3:1 only for text at 24px (18pt) or larger. Record the ratio, not "ok".

Deck-level checks below the table:

Every spine beat has at least one slide, and the ending matches the one written first
The deck states a position a reasonable person could disagree with
One colour system throughout: accents per section, or full-bleed palettes, never both
Recap slide has exactly one line per core section
Speaker notes sit where the output format reads them (Marp and Slidev: an HTML comment at the end of the slide; reveal.js: a
```
Note:
```
line;
```
.pptx
```
: the notes pane)
Pitch decks only: 10 slides plus an appendix at most, explicit ask slide (amount and use of funds), headlines pass the forwardable test

Fix every flagged row and re-output the table before handing over.

逐幻灯片审查并输出表格。此表格是证明幻灯片组已完成的交付物，而非简单的“审核通过”签字：

markdown

| # | 幻灯片 | 3秒测试 | 单一核心信息 | 故事主线节点 | 布局 | 色彩 | 对比度 |
|---|-------|-----------|-------------|------------|--------|--------|----------|
| 1 | 标题页 | 通过 | 通过 | 从前…… | 完整陈述式 | 蓝绿色 | 12.6:1 |

3秒测试： 手臂长度距离下3秒内可理解（Duarte扫视测试）。若未通过则删减文案直至通过。Pitch Deck为阅读型而非扫视型：替换为“无上下文转发后仍清晰易懂”。
单一核心信息： 每张幻灯片仅承载一个核心观点；若承载两个则拆分幻灯片。
故事主线节点： 本幻灯片对应步骤2故事主线中的哪个节点。若未对应任何节点，则为无关事实，需删除。
布局： 幻灯片功能变化时布局应随之调整。若连续3张或更多幻灯片布局相同，需标记，仅当该章节为刻意设计的列表时可保留。
色彩： 符合步骤5指定的章节强调色或全 bleed 配色方案。
对比度： 幻灯片上最小字号文本与背景的对比度。正文和说明文字需达到4.5:1，仅当字号为24px（18pt）及以上时可放宽至3:1。记录具体比值，而非“合格”。

表格下方需进行幻灯片组整体检查：

每个故事主线节点至少对应一张幻灯片，且结尾与最初撰写的一致
幻灯片组明确提出一个合理人士可能持反对意见的立场
全程采用单一色彩系统：按章节使用强调色，或全bleed配色方案，不可同时使用两者
回顾页每个核心章节仅对应一行内容
演讲备注存储位置符合输出格式要求（Marp和Slidev：幻灯片末尾的HTML注释；reveal.js：
```
Note:
```
行；.pptx：备注窗格）
仅针对Pitch Deck：最多10页幻灯片加附录，包含明确的请求页（融资金额与用途），标题符合可转发测试标准

修复所有标记问题后重新输出表格再交付。

Core principles

核心原则

Story before slides: the spine decides which slides exist. Write the ending first.
Take a position: a deck nobody could disagree with has not said anything.
Headlines do the work: the complete claim, not a topic label. "Q3: revenue up 40%. Here's how." beats "Q3 performance overview".
Impact through scale, not weight: large light type beats small bold type.
One colour system, held for the whole deck: full-bleed palettes where a palette owns the entire slide, or dark with one accent per section. Either is the rhythm the audience tracks position by.
Demo it live where you can: a working demo on a web deck, not a screenshot of one; a recording where the demo cannot run offline.

先有故事，后做幻灯片： 故事主线决定幻灯片内容。先写结尾。
明确立场： 无人反对的幻灯片组等于没有传递任何有效信息。
标题承担核心作用： 标题需完整表达观点，而非仅作为主题标签。例如“Q3营收增长40%，以下是实现路径”优于“Q3业绩概览”。
通过比例而非重量实现视觉冲击： 大号浅色字体优于小号加粗字体。
全程采用单一色彩系统： 全bleed配色方案指整页幻灯片使用同一配色，深色系统则按章节使用一种强调色。任一系统均可帮助受众定位当前内容章节。
尽可能实时演示： 在Web幻灯片组中使用可运行的实时演示，而非截图；若无法离线运行则使用录制视频。

Gotchas

常见误区

Dark deck in a bright room: the default dark system relies on the room. Under daylight or a weak projector the black background goes grey and white body text washes out. Ask about the venue in Step 1; take the light "paper" palette or a white background when the answer is bright, and test on the projector, not the laptop.
Contrast checked at headline size only: a saturated full-bleed pair that reads at 100px fails at 20px caption size. Check the smallest text on the slide: 4.5:1 for body and captions, 3:1 for 24px-plus text, from the actual hex values. Record the ratio in the QA table.
Export "PPTX" from Marp or Slidev and call it done: both rasterise each slide into an image inside the
```
.pptx
```
. Text is not selectable or editable, so the deck the client wanted to edit is a stack of pictures. When editable PowerPoint is the deliverable, route to the
```
pptx
```
skill.
Notes and directives both live in HTML comments in Marp:
```

```
is a directive,
```

```
is a presenter note. A note that starts with a
```
key: value
```
line silently becomes a directive.
Fixed pixel type on a web deck: a deck sized for the presenter's laptop is a different deck on the projector and unreadable on the phone it gets forwarded to. Size in
```
clamp()
```
; Marp and
```
.pptx
```
decks are fixed canvases and take pt sizes instead.
Presented-deck density on a pitch deck sent by email: a 3-words-per-slide deck forwarded with no presenter is unreadable. Route to
```
pitch-decks.md
```
at Step 1, not after the deck is built. The inverse also fails: a 60-word slide on a demo-day stage.
Sparse headlines on pitch decks: "Traction" tells a skimming investor nothing. Write the claim: "1,000+ customers, $10M ARR".
Skipping the spine: jumping straight to slides produces a list of facts with no arc, then a rewrite once the missing narrative shows. Spine and ending first.
Speaker notes as a script: a verbatim script gets read aloud and sounds flat. Notes are prompts: key point, talk-track bullets, transition line.
Accents outside the section system: section colours are wayfinding; a random mid-section accent reads as a topic change that never happened. On a full-bleed deck the slide is the accent; the colour changes at the slide boundary, not inside it.
Paragraphs on slides: the audience reads instead of listening and the speaker becomes redundant. Cut until the 3-second test passes.

明亮环境下使用深色幻灯片组： 默认深色系统依赖场地环境。在自然光或投影设备较弱的情况下，黑色背景会发灰，白色正文会模糊。步骤1需询问场地信息；若为明亮环境则采用浅色“纸质”配色或白色背景，并在投影设备上测试，而非仅在笔记本电脑上测试。
仅检查标题字号的对比度： 100px字号下可读的饱和全bleed配色在20px说明文字下可能无法识别。需检查幻灯片上最小字号文本的对比度：正文和说明文字需达到4.5:1，24px及以上字号需达到3:1，需根据实际十六进制颜色值计算。在质检表格中记录具体比值。
从Marp或Slidev导出“PPTX”即视为完成： 两者均将每张幻灯片栅格化为.pptx内的图片。文本无法选中或编辑，因此客户想要编辑的幻灯片组会变成一堆图片。若交付物为可编辑的PowerPoint文件，需分流至
```
pptx
```
技能。
Marp中备注与指令均存储于HTML注释：
```

```
是指令，
```

```
是演讲备注。若备注以
```
key: value
```
行开头，会自动变为指令。
Web幻灯片组使用固定像素字体： 为演讲者笔记本电脑设计的幻灯片组在投影设备上显示效果不同，转发至手机后可能无法阅读。使用
```
clamp()
```
设置字号；Marp和.pptx幻灯片组为固定画布，需使用pt字号。
将现场演示文稿的内容密度用于邮件发送的Pitch Deck： 每页仅3个单词的幻灯片组无演讲者转发后无法阅读。步骤1需分流至
```
pitch-decks.md
```
，而非幻灯片组制作完成后。反之亦然：演示日现场使用60词每页的幻灯片组也会失败。
Pitch Deck标题过于简洁： “用户增长”无法让快速浏览的投资人获取有效信息。需明确表达观点：“1000+客户，ARR达1000万美元”。
跳过故事主线： 直接制作幻灯片会导致内容沦为无逻辑的事实列表，后续因缺失叙事逻辑需重写。需先确定故事主线与结尾。
演讲备注写成逐字稿： 逐字稿会导致演讲者照本宣科，语气生硬。备注应为提示：核心要点、演讲要点列表、过渡语句。
章节系统外随意使用强调色： 章节色彩用于内容导航；中途随机使用强调色会让受众误以为主题发生变化，而实际并未变化。全bleed配色方案中，整页幻灯片即为强调色；色彩仅在幻灯片边界处变化，而非幻灯片内部。
幻灯片上出现段落： 受众会阅读段落而非聆听演讲，导致演讲者失去作用。删减内容直至通过3秒测试。