paper-deck

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Paper Deck — Visual Slide Director

Paper Deck — Visual Slide Director

把论文/知识内容做成看起来真的被设计过的幻灯片。
核心路线不是用 PPT 对象硬摆版式,而是:
  1. 先理解内容,做出 deck brief 和逐页叙事。
  2. 为每一页写清楚“这页要让观众看到什么、感到什么、记住什么”。
  3. 用生图模型生成 16:9 slide image。
  4. 合成 PPTX/PDF,并保留 prompts 作为可返修的源文件。
Turn papers/knowledge content into slides that look professionally designed.
The core approach is not to rigidly arrange layouts using PPT objects, but rather:
  1. First understand the content, create a deck brief and page-by-page narrative.
  2. Clearly define for each page: "What do you want the audience to see, feel, and remember from this page?"
  3. Use an image generation model to produce 16:9 slide images.
  4. Synthesize into PPTX/PDF, and retain prompts as source files for revision.

何时使用

When to Use

适合:
  • 论文组会、答辩、reading group、技术分享
  • 需要“一眼不像模板 PPT”的视觉汇报
  • 用户愿意接受每页是高质感图片,优先追求整体观感和传播效果
  • 需要逐页返修:重做第 N 页、换风格、加真实感、减少 AI 味
不适合:
  • 需要多人在 PowerPoint 里精细编辑每个文本框
  • 大量表格、财务报表、合规材料
  • 需要准确复制已有企业 PPT 母版
如果用户需要完全可编辑的 PPT,说明本 skill 的 V1 是 raster-first;可改用常规 PPTX 工具,或生成“图片背景 + 可编辑文字层”的混合方案。
Suitable for:
  • Paper group meetings, defenses, reading groups, technical sharing
  • Visual presentations that "don't look like template PPT at first glance"
  • Users who prefer high-quality image-based pages and prioritize overall visual impact and dissemination effect
  • Need page-by-page revision: redo page N, change style, increase realism, reduce AI traces
Not suitable for:
  • Need multiple people to edit each text box in PowerPoint with precision
  • Large amounts of tables, financial statements, compliance materials
  • Need to accurately replicate existing corporate PPT masters
If users require fully editable PPT, explain that V1 of this skill is raster-first; they can switch to regular PPTX tools, or use a hybrid solution of "image background + editable text layers".

工作流

Workflow

Step 1: 输入分析

Step 1: Input Analysis

接受:
  • arXiv / DOI / 网页链接
  • PDF 路径
  • Markdown / 文本 / 文章
  • 已有大纲
  • 参考图片或参考 PPT 截图
如果是论文,优先复用
paper-analyzer
的阅读方式:读摘要、方法、实验、图表、结论;必要时搜索代码仓库。目标不是写长文,而是提取适合做 slide 的核心叙事。
输出并保存
analysis.md
  • 主题、受众、汇报场景
  • 论文/内容的 1 句话主张
  • 3-5 个必须讲清楚的核心点
  • 推荐页数、推荐风格、语言
  • 需要生成的图像类型:封面、机制图、流程图、数据页、结论页等
  • 可直接使用的真实素材:论文 Figure/Table、PDF 截图、用户提供的截图、代码截图、实验曲线
Accepts:
  • arXiv / DOI / web links
  • PDF paths
  • Markdown / text / articles
  • Existing outlines
  • Reference images or reference PPT screenshots
For papers, prioritize reusing the reading method of
paper-analyzer
: read abstract, methods, experiments, charts, conclusions; search code repositories if necessary. The goal is not to write long articles, but to extract core narratives suitable for slides.
Output and save
analysis.md
:
  • Topic, audience, presentation scenario
  • 1-sentence thesis of the paper/content
  • 3-5 core points that must be clearly explained
  • Recommended number of pages, recommended style, language
  • Types of images to generate: cover, mechanism diagram, flowchart, data page, conclusion page, etc.
  • Directly usable real materials: paper Figure/Table, PDF screenshots, user-provided screenshots, code screenshots, experimental curves

Step 2: 生成前确认

Step 2: Pre-Generation Confirmation

默认必须确认,不要直接生成图片。除非用户明确说“直接生成/不用确认/按默认来”。
询问时控制在 3 个问题以内:
  1. 页数和用途:组会 / 答辩 / 公开分享 / 商业汇报,需要几页?
  2. 风格:见
    references/style-system.md
  3. 是否插入真实素材:是否允许从 PDF/论文图表中截图,或由用户提供截图/图片?如果允许,说明预计第几页使用哪些真实素材。
推荐话术:
text
我建议做 12 页,风格用 journal-minimal:像 Nature/IEEE 论文图 + 正式学术汇报,清晰、克制、不花哨。
也可以换成 business-research 做商业研究分享,warm-notes 做手记风,或 liquid-glass 做 Apple 式玻璃质感。
这篇论文我建议在第 4 页插入原论文方法图局部截图,第 8 页插入实验曲线/表格截图,再基于这些真实素材做设计化排版。
确认后我会先生成 outline.md 和每页 prompt,再逐页出图并合成 PPTX/PDF。
Confirmation is required by default; do not generate images directly unless the user explicitly says "generate directly/no need to confirm/follow defaults".
Limit questions to 3 or fewer when asking:
  1. Number of pages and purpose: group meeting / defense / public sharing / commercial presentation, how many pages are needed?
  2. Style: see
    references/style-system.md
    .
  3. Insert real materials: allow screenshots from PDF/paper charts, or user-provided screenshots/images? If allowed, specify which real materials are expected to be used on which pages.
Recommended script:
text
I suggest making 12 pages with the journal-minimal style: like Nature/IEEE paper figures + formal academic presentations, clear, restrained, and not flashy.
You can also switch to business-research for commercial research sharing, warm-notes for notebook style, or liquid-glass for Apple-style glass texture.
For this paper, I recommend inserting a partial screenshot of the original paper's method diagram on page 4, and a screenshot of experimental curves/tables on page 8, then doing design-based layout based on these real materials.
After confirmation, I will first generate outline.md and prompts for each page, then produce images page by page and synthesize into PPTX/PDF.

Step 3: Deck Brief

Step 3: Deck Brief

保存
deck-brief.md
。必须包含:
  • style_preset
  • audience
  • slide_count
  • language
  • visual_rules
  • do_not_use
  • reference_images
    (如有)
  • source_visual_plan
    :哪些页使用真实图表/截图,来源和处理方式
风格细节按需读取
references/style-system.md
。 真实素材策略按需读取
references/source-visuals.md
Save as
deck-brief.md
. Must include:
  • style_preset
  • audience
  • slide_count
  • language
  • visual_rules
  • do_not_use
  • reference_images
    (if any)
  • source_visual_plan
    : which pages use real charts/screenshots, sources and processing methods
Read
references/style-system.md
for style details as needed. Read
references/source-visuals.md
for real material strategies as needed.

Step 4: Outline

Step 4: Outline

保存
outline.md
。每页用固定结构:
markdown
undefined
Save as
outline.md
. Each page uses a fixed structure:
markdown
undefined

01. Slide Title

01. Slide Title

  • Role: cover / context / method / mechanism / evidence / result / takeaway
  • Message: 这一页唯一要讲清楚的观点
  • Visual: 画面主视觉和构图
  • Text: 页面上允许出现的短文字
  • Evidence: 引用的论文图表/公式/实验数据/代码位置
  • Source visual: 是否使用真实截图/论文图表;来源、裁剪范围和落位
  • Repair handle: 后续返修时可引用的定位描述

规则:
- 每页只承载一个主观点。
- 页面文字尽量少;复杂解释放 speaker script 或备注里。
- 机制页优先画“输入 → 处理 → 输出”,不要画抽象灵感。
- 数据页只放最有说服力的 1-3 个数字。
- 真实论文图/截图通常比凭空生成更可信;能用真实素材时优先规划真实素材落位。
- 不要过度留白。主视觉、图表或证据区域通常应占画面 60%-80%,除非是封面或章节页。
- 8 页以上必须有节奏变化:封面、问题、方法、机制、证据、结论交替。
  • Role: cover / context / method / mechanism / evidence / result / takeaway
  • Message: The only key point to be clearly explained on this page
  • Visual: Main visual and composition of the page
  • Text: Short text allowed on the page
  • Evidence: Cited paper charts/formulas/experimental data/code locations
  • Source visual: Whether to use real screenshots/paper charts; source, cropping range and placement
  • Repair handle: Position description that can be referenced for subsequent revisions

Rules:
- Each page only carries one main point.
- Minimize text on the page; place complex explanations in speaker scripts or notes.
- For mechanism pages, prioritize drawing "input → processing → output" instead of abstract inspiration.
- For data pages, only include the 1-3 most convincing numbers.
- Real paper figures/screenshots are usually more credible than AI-generated ones; prioritize planning the placement of real materials when available.
- Do not overuse white space. The main visual, chart, or evidence area should usually occupy 60%-80% of the page, except for covers or section pages.
- For decks with more than 8 pages, must have rhythm changes: alternate between cover, problem, method, mechanism, evidence, conclusion.

Step 5: Prompt Files

Step 5: Prompt Files

每页必须先写 prompt 文件,再调用任何生图工具。
路径:
text
paper-deck/{topic-slug}/
├── analysis.md
├── deck-brief.md
├── outline.md
├── prompts/
│   ├── 01-slide-cover.md
│   ├── 02-slide-context.md
│   └── ...
├── images/
│   ├── 01-slide-cover.png
│   ├── 02-slide-context.png
│   └── ...
├── {topic-slug}.pptx
└── {topic-slug}.pdf
Prompt 写法读取
references/prompt-template.md
硬规则:
  • prompt 必须明确 16:9。
  • prompt 里要写清楚风格、构图、文字语言、文字数量限制。
  • 不要让模型生成页码、logo、水印、PPT 外壳。
  • 如果需要精准文字,尽量减少图片内文字;可以后续做混合文字层。
  • 如果本页使用真实素材,prompt 必须说明素材如何作为画面的一部分:嵌入、裁切、玻璃面板承载、旁注、放大框,而不是让模型凭空重画事实。
Must write a prompt file for each page before calling any image generation tool.
Path:
text
paper-deck/{topic-slug}/
├── analysis.md
├── deck-brief.md
├── outline.md
├── prompts/
│   ├── 01-slide-cover.md
│   ├── 02-slide-context.md
│   └── ...
├── images/
│   ├── 01-slide-cover.png
│   ├── 02-slide-context.png
│   └── ...
├── {topic-slug}.pptx
└── {topic-slug}.pdf
Read
references/prompt-template.md
for prompt writing guidelines.
Hard rules:
  • Prompt must explicitly specify 16:9.
  • Prompt must clearly state style, composition, text language, and text quantity limits.
  • Do not let the model generate page numbers, logos, watermarks, or PPT frames.
  • If precise text is needed, minimize text within the image; a hybrid text layer can be added later.
  • If real materials are used on this page, the prompt must explain how the materials are integrated into the page: embedded, cropped, carried by glass panels, annotated, magnified, rather than letting the model redraw facts from scratch.

Step 6: 生成图片

Step 6: Generate Images

图片后端选择:
  1. Codex 环境优先用内置
    imagegen
  2. 如果用户指定
    baoyu-imagine
    、Gemini、OpenAI、Seedream 等后端,按用户指定。
  3. 如果没有可用生图后端,停止并告诉用户需要一个 raster image backend。
生成策略:
  • 先生成第 1 页作为风格锚点。
  • 后续页如果后端支持 reference image,就用第 1 页作为风格参考,降低漂移。
  • 每 3-4 页检查一次缩略图,发现风格漂移就修 prompt 再继续。
  • 保存失败页,不要覆盖成功页。
Image backend options:
  1. Use built-in
    imagegen
    first in Codex environment.
  2. If the user specifies backends like
    baoyu-imagine
    , Gemini, OpenAI, Seedream, follow the user's choice.
  3. If no available image generation backend is present, stop and inform the user that a raster image backend is required.
Generation strategy:
  • First generate page 1 as the style anchor.
  • For subsequent pages, if the backend supports reference images, use page 1 as the style reference to reduce style drift.
  • Check thumbnails every 3-4 pages; if style drift is found, revise the prompt before continuing.
  • Save failed pages; do not overwrite successful ones.

Step 7: 合成 PPTX/PDF

Step 7: Synthesize PPTX/PDF

生成完图片后运行:
bash
python3 <SKILL_ROOT>/scripts/merge_deck.py paper-deck/{topic-slug}
脚本会读取
images/NN-*.png|jpg|webp
,输出同名
.pptx
.pdf
。每张图片铺满一页 16:9。
After generating images, run:
bash
python3 <SKILL_ROOT>/scripts/merge_deck.py paper-deck/{topic-slug}
The script will read
images/NN-*.png|jpg|webp
and output a corresponding
.pptx
and
.pdf
. Each image fills a full 16:9 page.

Step 8: 质量检查

Step 8: Quality Check

交付前按
references/quality-gate.md
检查:
  • 是否一眼像真实设计作品,而不是模板堆砌
  • 每页是否只有一个主观点
  • 是否有过多无意义留白;关键内容是否占据足够画面
  • 真实素材页是否明确记录来源、页码/图号和落位
  • 风格是否一致
  • 图片文字是否清晰、无错别字、无伪字
  • 是否存在 AI 常见问题:假 UI、假 logo、乱码标签、过度赛博、塑料 3D、无意义装饰
  • PPTX/PDF 是否能打开,页数是否正确
Check against
references/quality-gate.md
before delivery:
  • Does it look like a real design work at first glance, rather than a template stack?
  • Does each page only carry one main point?
  • Is there excessive meaningless white space; does key content occupy enough of the page?
  • Are real material pages clearly recorded with source, page number/figure number and placement?
  • Is the style consistent?
  • Is the text in the image clear, free of typos, and not gibberish?
  • Are common AI issues present: fake UI, fake logos, garbled labels, excessive cyberpunk style, plastic 3D, meaningless decorations?
  • Can the PPTX/PDF be opened, and is the number of pages correct?

Step 9: 返修

Step 9: Revision

返修时永远先改源文件:
用户说操作
“第 5 页更学术一点”
prompts/05-*.md
,保留旧图,生成新图
“统一成第 1 页的质感”把第 1 页风格锚点追加到相关 prompts
“第 7 页文字太多”修改 outline 的 Text,再改 prompt
“只重做背景,不动内容”在 prompt 中保留 Message/Text,重写 Visual
“新增一页机制细节”更新 outline,新增 prompt,生成图片,重跑合成脚本
不要用程序在生成图上涂改文字。文字错了就改 prompt 重生成,或切换到混合文字层方案。
Always modify source files first when revising:
User saysAction
"Make page 5 more academic"Revise
prompts/05-*.md
, keep the old image, generate a new one
"Unify the texture to match page 1"Add the style anchor of page 1 to relevant prompts
"Too much text on page 7"Modify the Text section in the outline, then revise the prompt
"Only redo the background, don't change the content"Keep Message/Text in the prompt, rewrite the Visual section
"Add a new page for mechanism details"Update the outline, add a new prompt, generate the image, rerun the synthesis script
Do not use programs to alter text on generated images. If text is incorrect, revise the prompt and regenerate, or switch to the hybrid text layer solution.

参考文件

Reference Files

  • references/style-system.md
    :风格预设和选择规则
  • references/layouts.md
    :常用页面角色与构图
  • references/source-visuals.md
    :PDF 截图、论文图表、用户图片的使用策略
  • references/prompt-template.md
    :逐页生图 prompt 模板
  • references/quality-gate.md
    :交付前检查和返修标准
  • references/style-system.md
    : Style presets and selection rules
  • references/layouts.md
    : Common page roles and compositions
  • references/source-visuals.md
    : Usage strategies for PDF screenshots, paper charts, and user-provided images
  • references/prompt-template.md
    : Page-by-page image generation prompt templates
  • references/quality-gate.md
    : Pre-delivery inspection and revision standards