ian-handdrawn-ppt

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Ian Handdrawn PPT

Ian 手绘PPT

Turn source material into a Chinese handdrawn technical PPT-style image deck. Optimize for commercial delivery: clear narrative, semantic page archetypes, exact short Chinese text, refined handdrawn diagrams, and deck-level visual consistency.

将源素材转换为中文手绘风格的技术PPT式图像幻灯片集。针对商业交付进行优化：叙事清晰、语义化页面原型、精准简短的中文文本、精致的手绘图表，以及幻灯片集级别的视觉一致性。

Operating Rule

操作规则

Default production output is complete raster page images generated by the built-in image generation model. Blog/article covers default to 21:9; body illustrations and standard deck pages default to 16:9. Each page is a final visual deliverable with both diagram and Chinese text included in the image.

In this skill, "PPT", "slides", "page", and "deck" mean finished PPT-style visual page images, not editable presentation/document files. Do not route to presentation or document packaging merely because the user says PPT/PPTX/PDF. Editable PPTX, image-based PPTX, and PDF export are out of scope for this skill.

Do not use deterministic drawing scripts, HTML, SVG, canvas, or python-pptx as the primary visual generator for style samples. Deterministic post-processing is allowed for crop/resize, contact sheets, or exact text overlay when the generated image direction is accepted but image text fidelity is not good enough.

Produce a planning blueprint when the user asks to plan, outline, or design first. Production output is final PNG page images plus a contact sheet when there are multiple pages.

默认生成输出为内置图像生成模型创建的完整光栅页面图像。博客/文章封面默认采用21:9比例；正文插图和标准幻灯片集页面默认采用16:9比例。每个页面都是包含图表和中文文本的最终视觉交付物。

在本技能中，“PPT”“slides”“page”和“deck”均指成品PPT风格的视觉页面图像，而非可编辑的演示文稿/文档文件。请勿仅因用户提及PPT/PPTX/PDF就转向演示文稿或文档打包流程。可编辑PPTX、基于图像的PPTX以及PDF导出均不属于本技能的范围。

请勿使用确定性绘图脚本、HTML、SVG、canvas或python-pptx作为风格示例的主要视觉生成工具。当生成图像的方向符合要求但文本保真度不足时，允许进行确定性后期处理，如裁剪/调整大小、联系表制作或精确文本叠加。

当用户要求先进行规划、大纲编写或设计时，需生成规划蓝图。当涉及多页内容时，生成输出为最终PNG页面图像加联系表。

Resource Map

资源映射

Load only the references needed for the current task:

```
references/intake.md
```
: input types, missing-information checks, and concise clarification rules.
```
references/narrative-planning.md
```
: deck type selection and story structures.
```
references/slide-archetypes.md
```
: semantic mapping from content type to slide layout.
```
references/visual-dna-v6.md
```
: handdrawn Chinese technical PPT visual system and deck-level style lock.
```
references/output-quality.md
```
: output contracts and verification gates for final image pages.
```
references/prompt-patterns.md
```
: prompt templates for complete image-model slide pages.

Use

assets/theme-tokens.json

as the compact theme token file when writing prompts. Use

assets/reference-handdrawn-article-illustration-style.png

as the active style anchor for blog/article cover and body illustrations. When the current image tool supports local reference images, load or attach this style anchor before generation. When it does not, use the theme tokens plus the reference-match clause in

references/prompt-patterns.md

, and report the style as prompt-matched rather than image-referenced. Do not use legacy bordered PPT reference images unless the user explicitly asks to recreate the older bordered look.

仅加载当前任务所需的参考资料：

```
references/intake.md
```
：输入类型、缺失信息检查及简洁澄清规则。
```
references/narrative-planning.md
```
：幻灯片集类型选择及故事结构。
```
references/slide-archetypes.md
```
：从内容类型到幻灯片布局的语义映射。
```
references/visual-dna-v6.md
```
：中文手绘技术PPT视觉系统及幻灯片集级风格锁定规则。
```
references/output-quality.md
```
：最终图像页面的输出协议及验证标准。
```
references/prompt-patterns.md
```
：完整图像模型幻灯片页面的提示词模板。

编写提示词时，使用

assets/theme-tokens.json

作为紧凑主题标记文件。使用

assets/reference-handdrawn-article-illustration-style.png

作为博客/文章封面及正文插图的当前风格锚点。当当前图像工具支持本地参考图像时，生成前加载或附加此风格锚点。若不支持，则使用主题标记加上

references/prompt-patterns.md

中的参考匹配条款，并说明风格为提示词匹配而非图像参考。除非用户明确要求复刻旧版带边框的外观，否则请勿使用旧版带边框PPT参考图像。

Workflow

工作流程

Ingest material
- Read the provided content or attached file.
- If the input is
```
.pptx
```
  , extract the source content and visual intent only; do not edit or package the PPTX inside this skill.
- If the input is
```
.docx
```
  , use the Documents plugin or skill to extract content.
- If the input is
```
.pdf
```
  , use the PDF/document tooling appropriate to the task.
- If the input is plain text, Markdown, notes, or an outline, parse it directly.
Run intake and gap diagnosis
- Read
```
references/intake.md
```
  when the content is broad, incomplete, or the output requirements are unclear.
- Determine topic, audience, scenario, target length, and source sufficiency.
- Ask at most 1-3 questions only when the missing information materially changes the deck.
- If no critical information is missing, proceed with reasonable defaults.
Plan the deck narrative
- Read
```
references/narrative-planning.md
```
  .
- Classify the deck as teaching, persuasive, report, product explanation, or knowledge-card style.
- Create a slide-by-slide spine: each slide must have one main point.
Map each slide to an archetype
- Read
```
references/slide-archetypes.md
```
  .
- Choose slide layouts from the content semantics, not from a fixed template order.
- Vary archetypes so the deck has rhythm.
Apply visual DNA
- Read
```
references/visual-dna-v6.md
```
  .
- Use small exact Chinese text, fine handdrawn lines, light pastel marks, few characters, low visual heaviness, large negative space, and one shared master layout language across the whole deck.
- Lock cross-page constants before generating: page role, canvas ratio, near-white paper tone, no-border default, page number, title treatment, title optical size, line weight, pastel palette, corner grid marks, character policy, and spacing rhythm.
- Keep the outer shell fixed across pages: page number location, title block, underline, paper tone, corner marks, and visual scale. Vary only the middle semantic diagram area according to the content.
- Treat blog/article visuals as two role-specific outputs by default: a 21:9 cover image and 16:9 body illustrations. Do not let body pages look like cover pages.
Build output
- For planning-only requests, deliver a structured blueprint with deck type, slide count, title, main point, archetype, content blocks, visual brief, and missing inputs.
- For production requests, use the built-in image generation model to generate one complete page image per slide/visual. Use one image generation call per distinct page brief, not a generic repeated template.
- When the user asks for a cover plus body illustrations, generate the cover as 21:9 and body illustrations as 16:9 unless the user specifies otherwise.
- Before generating multiple pages, write one compact deck style lock and reuse it verbatim in every page prompt. Add page-specific layout instructions only for the central diagram/content area.
- Keep all visible Chinese text short and exact in the prompt. Include a
```
Required text only
```
  list for each page.
- If exact Chinese text is mission-critical or repeated generations render text incorrectly, reduce the text budget first. If needed, generate the accepted visual with blank label spaces and add exact text as deterministic post-processing; the final deliverable is still a raster page image.
- Save final selected images into the workspace, and make a contact sheet when generating multiple pages.
- Check actual image dimensions. If the image model returns near-target native sizes, report the actual size; normalize body illustrations to 1920x1080 and cover images to 2520x1080 only when strict delivery dimensions are requested.
Verify
- Read
```
references/output-quality.md
```
  .
- Check content accuracy, slide rhythm, Chinese text accuracy, visual consistency, style-anchor match, and commercial handoff readiness.
- If verification fails, revise before final delivery.

素材导入
- 读取提供的内容或附加文件。
- 若输入为
```
.pptx
```
  文件，仅提取源内容和视觉意图；请勿在本技能内编辑或打包PPTX文件。
- 若输入为
```
.docx
```
  文件，使用Documents插件或技能提取内容。
- 若输入为
```
.pdf
```
  文件，使用适合任务的PDF/文档工具。
- 若输入为纯文本、Markdown、笔记或大纲，直接解析。
输入检查与缺口诊断
- 当内容宽泛、不完整或输出要求不明确时，读取
```
references/intake.md
```
  。
- 确定主题、受众、场景、目标长度及素材充足性。
- 仅当缺失信息会实质性改变幻灯片集时，最多提出1-3个问题。
- 若不存在关键信息缺失，使用合理默认值继续。
规划幻灯片集叙事
- 读取
```
references/narrative-planning.md
```
  。
- 将幻灯片集分类为教学型、说服型、报告型、产品讲解型或知识卡片型。
- 创建逐页核心框架：每张幻灯片必须有一个核心要点。
为每张幻灯片匹配原型
- 读取
```
references/slide-archetypes.md
```
  。
- 根据内容语义选择幻灯片布局，而非固定模板顺序。
- 变换原型类型，使幻灯片集富有节奏。
应用视觉DNA
- 读取
```
references/visual-dna-v6.md
```
  。
- 使用精准简短的中文文本、精细手绘线条、浅淡柔和标记、少量字符、低视觉重量感、大量留白，以及贯穿整个幻灯片集的统一主布局语言。
- 生成前锁定跨页常量：页面角色、画布比例、近白色纸张色调、默认无边框、页码、标题处理方式、标题视觉大小、线条粗细、柔和调色板、角落网格标记、字符规则及间距节奏。
- 保持跨页外部元素固定：页码位置、标题块、下划线、纸张色调、角落标记及视觉比例。仅根据内容调整中间语义图表区域。
- 默认将博客/文章视觉内容分为两种特定角色输出：21:9比例封面图像和16:9比例正文插图。请勿让正文页面看起来像封面。
生成输出
- 对于仅规划的请求，交付包含幻灯片集类型、页数、标题、核心要点、原型、内容块、视觉 brief及缺失输入的结构化蓝图。
- 对于生成请求，使用内置图像生成模型为每张幻灯片/视觉内容生成一个完整的页面图像。为每个不同的页面brief调用一次图像生成，而非使用通用重复模板。
- 当用户要求封面加正文插图时，默认生成21:9比例封面和16:9比例正文插图，除非用户另有指定。
- 生成多页内容前，编写一个紧凑的幻灯片集风格锁定规则，并在每个页面提示词中逐字复用。仅为中心图表/内容区域添加页面特定布局说明。
- 在提示词中保持所有可见中文文本简短精准。为每个页面包含一个「仅需文本」列表。
- 若精准中文文本至关重要或多次生成后文本仍不准确，首先减少文本量。如有需要，生成带有空白标签位的可接受视觉效果，再通过确定性后期处理添加精准文本；最终交付物仍为光栅页面图像。
- 将最终选定的图像保存到工作区，生成多页内容时制作联系表。
- 检查实际图像尺寸。若图像模型返回接近目标的原生尺寸，报告实际尺寸；仅当要求严格交付尺寸时，将正文插图标准化为1920x1080，封面图像标准化为2520x1080。
验证
- 读取
```
references/output-quality.md
```
  。
- 检查内容准确性、幻灯片节奏、中文文本准确性、视觉一致性、风格锚点匹配度及商业交付就绪度。
- 若验证不通过，在最终交付前进行修改。

Defaults

默认设置

Use these defaults unless the user says otherwise:

Language: Simplified Chinese.
Audience: Chinese learners with some technical curiosity but not necessarily expert depth.
Deck length: 8-12 slides for an article, 15-30 slides for a course module, 5-8 slides for a short idea.
Output: final PNG page images plus a contact sheet and short slide blueprint summary.
Blog/article visual split: cover image is 21:9; body illustrations are 16:9.
Style: refined near-white Chinese handdrawn technical article/PPT illustration V6.

除非用户另有说明，否则使用以下默认设置：

语言：简体中文。
受众：有一定技术好奇心但不一定具备专业深度的中文学习者。
幻灯片集长度：文章类为8-12页，课程模块类为15-30页，简短想法类为5-8页。
输出：最终PNG页面图像加联系表及简短幻灯片蓝图摘要。
博客/文章视觉拆分：封面图像为21:9比例；正文插图为16:9比例。
风格：精致近白色中文手绘技术文章/PPT插图V6版本。

Final Response

最终响应

When finished, report:

The created image folder and contact sheet path.
The page count and deck type.
Any important assumptions.
Verification performed and any remaining risks.

For planning-only outputs, provide the blueprint directly and identify the critical questions to answer before deck production.

完成后，报告：

创建的图像文件夹及联系表路径。
页数及幻灯片集类型。
任何重要假设。
已执行的验证及剩余风险。

对于仅规划的输出，直接提供蓝图，并确定幻灯片集生成前需解答的关键问题。