book-illustration-workflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Book Illustration Workflow

这个 skill 处理的是“章节截图从规划到落文再到飞书同步”的完整流程。

This skill handles the complete workflow of "chapter screenshots from planning to insertion into text and synchronization to Feishu".

目标

Objectives

把一章书稿中的插图工作拆成稳定流程：

明确章节里真正需要的截图和成品图
逐步给出可在 Claude Code 中执行的真实提示词
约束截图文件名、图号和正文位置一一对应
把图片放回本地 Markdown 的正确位置
清除不该给读者看到的作者备注
把读者版章节和图片同步到 Feishu

Break down the illustration workflow for a book chapter into a stable process:

Identify the screenshots and final images actually needed in the chapter
Provide real, executable prompts for Claude Code step by step
Ensure one-to-one correspondence between screenshot filenames, figure numbers, and positions in the text
Place images back in the correct positions in local Markdown
Remove author notes that are not intended for readers
Synchronize the reader-facing chapter and images to Feishu

触发条件

Trigger Conditions

当用户有下面任一意图时使用：

让你帮他做书稿某一章的截图流程
让你逐步指导 Claude Code 截图或生成图
让你整理“图号 -> 提示词 -> 文件名 -> 原文位置”
让你把图片插回本地文章
让你把章节同步到 Feishu 文档
让你“按上次那套流程继续”

Use this skill when users have any of the following intentions:

Ask you to handle the screenshot workflow for a book chapter
Ask you to provide step-by-step guidance for taking screenshots or generating images with Claude Code
Ask you to organize the mapping of "figure number -> prompt -> filename -> position in original text"
Ask you to insert images back into local articles
Ask you to synchronize chapters to Feishu Docs
Ask you to "continue with the previous workflow"

核心原则

Core Principles

1. 截图里的提示词必须像真实工作

1. Prompts in screenshots must resemble real work tasks

给 Claude Code 的提示词里，禁止出现这些词：

```
书
```
```
章节
```
```
案例
```
```
演示
```
```
截图
```
```
适合展示
```
```
chapter7-demo
```
```
为了写书
```

截图里的用户输入必须像真实办公任务。

The following terms are prohibited in prompts for Claude Code:

```
book
```
```
chapter
```
```
case
```
```
demo
```
```
screenshot
```
```
suitable for display
```
```
chapter7-demo
```
```
for book writing
```

User input in screenshots must look like real office tasks.

2. 数据准备放在截图外

2. Data preparation should be done outside screenshots

不要把“造测试数据”“建目录供截图使用”“为了展示准备样本”放进 Claude Code 对话。

正确做法：

截图外准备数据
截图内只展示真实使用

Do not include "creating test data", "setting up directories for screenshots", or "preparing samples for display" in Claude Code conversations.

Correct approach:

Prepare data outside screenshots
Only show real usage within screenshots

3. 一次只推进一步

3. Only advance one step at a time

如果用户要求“我们一步一步来”，每次只给：

发给 Claude Code 的内容
要截哪一屏
截图保存名
对应原文位置
原文里是否已有占位

用户完成后，再给下一步。

If the user requests "let's take it step by step", only provide the following each time:

Content to send to Claude Code
Which screen to capture
Screenshot filename
Corresponding position in the original text
Whether there is already a placeholder in the original text

Provide the next step only after the user completes the current one.

4. 图片位置按正文语义，不按占位块整坨插

4. Place images according to text semantics, not placeholder blocks

如果文章里存在这种编辑痕迹：

```
素材占位
```
```
插图占位
```
一组图号集中挂在小节开头

不要机械地把图片全塞到那一块。

正确做法：

找到正文里真正引出该图的句子
把图片放在那句或那段后面
同步 Feishu 时也按这个顺序上传

If the article contains editing traces like:

```
material placeholder
```
```
illustration placeholder
```
A group of figure numbers clustered at the start of a section

Do not mechanically insert all images into that block.

Correct approach:

Find the sentence in the text that actually introduces the image
Place the image right after that sentence or paragraph
Follow this order when uploading to Feishu as well

5. 给读者看的正文不能保留作者备注

5. Reader-facing text must not retain author notes

这些内容不应出现在读者版正文或 Feishu 文档中：

```
素材占位
```
```
插图占位
```
```
建议拍法
```
```
建议做法
```
```
插图说明文案
```
```
来源提示
```
```
如果这里配一张……
```
```
如果你在书里配图……
```
```
你在书里可以……
```

处理原则：

有价值的信息改写成面向读者的正文
纯编辑备注直接删掉
已完成截图的，直接换成实际图片

The following content should not appear in reader-facing text or Feishu Docs:

```
material placeholder
```
```
illustration placeholder
```
```
suggested shooting method
```
```
suggested approach
```
```
illustration description copy
```
```
source hint
```
```
If we add an image here...
```
```
If you include an image in the book...
```
```
You can... in the book
```

Processing principles:

Rewrite valuable information into reader-facing text
Delete pure editing notes directly
Replace completed screenshot placeholders with actual images

标准流程

Standard Workflow

阶段 A：梳理章节

Phase A: Chapter Sorting

找到目标章节 Markdown 文件
找出所有图号、代码块、表格占位和“素材占位”段
判断哪些图是：
- 原始数据截图
- Claude Code 对话截图
- 成品图表/报表
- 外部官方页面截图
- 后期拼版图
给出最小可执行截图顺序

优先顺序通常是：

安装或环境确认
原始数据图
核心任务调用图
结果图
对比图
扩展应用图

如果需要快速建立整章截图计划，优先使用 references/chapter-illustration-template.md 里的总表模板。它适合在正式截图前先把“图号、用途、提示词、文件名、原文位置、是否完成”一次性列清。

Locate the target chapter Markdown file
Identify all figure numbers, code blocks, table placeholders, and "material placeholder" sections
Classify each image type:
- Raw data screenshots
- Claude Code conversation screenshots
- Final charts/reports
- External official page screenshots
- Post-edited composite images
Provide the minimum executable screenshot sequence

Priority order is usually:

Installation or environment confirmation
Raw data images
Core task invocation images
Result images
Comparison images
Extended application images

If you need to quickly create a full chapter screenshot plan, prefer the master table template in [references/chapter-illustration-template.md]. It is suitable for listing "figure number, purpose, prompt, filename, position in text, completion status" all at once before official screenshotting.

阶段 B：逐步指导截图

Phase B: Step-by-Step Screenshot Guidance

如果用户要一步一步执行，按这个模板输出：

第N步：<动作名称>

发给 Claude Code 的内容：
```text
<真实提示词>

你要截哪一屏：

<明确说明保留输入 / 输出 / 结果图>

截图保存名：

<文件名.png>

对应原文位置：

<章节中的位置或图号说明>

原文里现在有没有占位符：

有 / 没有


要求：

- 不抢跑后续步骤
- 不一次给太多
- 文件名直接可落盘

If the user wants to execute step by step, output using this template:

Step N: <Action Name>

Content to send to Claude Code:
```text
<Real Prompt>

Which screen to capture:

<Clearly specify to retain input / output / result image>

Screenshot filename:

<filename.png>

Corresponding position in original text:

<Position in chapter or figure number description>

Is there a placeholder in the original text now:

Yes / No


Requirements:

- Do not jump to subsequent steps
- Do not provide too much information at once
- Filenames should be directly usable for saving

阶段 C：回填本地文章

Phase C: Fill Back into Local Article

先检查本地 Markdown 是否属于哪一种：

```
读者版正文 + 独立图片占位
```
```
作者版正文 + 大块素材占位
```
```
正文里夹着大量编辑备注
```

处理方式：

如果还是作者版，先清理成读者版
如果图片已经有了，直接在正文中插入图片 Markdown
如果暂时没有图片，只保留简洁的读者可见表述，不保留编辑备注

图片插入格式优先：

![图7-10 趋势图成品示例](第七章图片/图7-10_趋势图成品示例.png)

First check which type the local Markdown belongs to:

Reader-facing text + independent image placeholders

Author-facing text + large material placeholders

Text with numerous embedded editing notes

Processing methods:

If it is still the author version, first clean it into the reader version
If images are ready, directly insert Markdown image syntax into the text
If images are not ready yet, only keep concise reader-friendly expressions and remove editing notes

Preferred image insertion format:

![Figure 7-10 Example of Completed Trend Chart](Chapter7_Images/Figure7-10_Completed_Trend_Chart.png)

阶段 D：同步到 Feishu

Phase D: Synchronize to Feishu

同步 Feishu 时，不要在旧文档上盲改大批错位图片。优先做法：

先把本地 Markdown 修成读者版
按“markdown 段落 -> 对应图片 -> 下一段”的顺序切分
新建一份 Feishu 文档上传
让新文档成为主文档

只有在用户明确要求保留原文档时，才在旧文档上修补。

When synchronizing to Feishu, do not blindly modify a large number of misplaced images in old documents. Preferred approach:

First revise the local Markdown into the reader version
Split the content in the order of "Markdown paragraph -> corresponding image -> next paragraph"
Create a new Feishu document and upload the content
Set the new document as the main document

Only modify the old document if the user explicitly requests to retain it.

阶段 E：Feishu 上传规则

Phase E: Feishu Upload Rules

使用

lark-cli

时：

```
docs +create
```
创建文档
```
docs +update --mode append
```
追加 markdown
```
docs +media-insert
```
插图

注意：

图片必须按正文顺序插
不要按“图号排序”插，必须按文章出现顺序
如果文件名有前缀冲突，例如
```
图7-1
```
会误匹配
```
图7-10
```
，必须做精确匹配

精确匹配规则：

只能匹配
```
^(图号)(_|\\.|$)
```
这种边界
不能用简单前缀包含

When using

lark-cli

```
docs +create
```
to create a document
```
docs +update --mode append
```
to append markdown
```
docs +media-insert
```
to insert images

Notes:

Images must be inserted in the order they appear in the text
Do not insert images by "figure number order", strictly follow the order in the article
If there is a prefix conflict in filenames (e.g.,
```
Figure7-1
```
mistakenly matches
```
Figure7-10
```
), use exact matching

Exact matching rules:

Only match boundaries like
```
^(figure number)(_|\\.|$)
```
Do not use simple prefix inclusion

命名规则

Naming Rules

截图文件名默认采用：

```
图号_简短说明.png
```

例如：

```
图7-2A_添加官方Skills市场.png
```

图7-8A_调用xlsx清洗数据界面.png

```
图7-18_报表首页示例.png
```

要求：

图号必须在文件名前部
中文说明尽量短
后续插文和上传 Feishu 都依赖这个命名

Default screenshot filename format:

```
figure_number_brief_description.png
```

Examples:

Figure7-2A_Add_Official_Skills_Market.png

Figure7-8A_Call_xlsx_Data_Cleaning_Interface.png

```
Figure7-18_Report_Homepage_Example.png
```

Requirements:

Figure number must be at the beginning of the filename
Chinese descriptions should be as concise as possible
This naming is relied on for subsequent text insertion and Feishu upload

附带模板

Attached Templates

章节截图总表模板：见 references/chapter-illustration-template.md

Chapter Screenshot Master Table Template: See references/chapter-illustration-template.md

质量检查清单

Quality Check List

在宣布完成前，必须自查：

每张图片是否和对应图号匹配
提示词是否像真实办公任务
是否还残留作者备注
本地 Markdown 里的图片顺序是否正确
Feishu 中图片是否跟着正确段落走
是否存在
```
图7-1
```
误匹配
```
图7-10
```
这类问题

Before declaring completion, you must self-check:

Whether each image matches its corresponding figure number
Whether prompts resemble real office tasks
Whether any author notes remain
Whether image order in local Markdown is correct
Whether images in Feishu follow the correct paragraphs
Whether there are issues like
```
Figure7-1
```
mistakenly matching
```
Figure7-10
```

默认回答风格

Default Response Style

如果用户说“按这个流程来”，默认这样执行：

先检查目标章节文件和图片目录
如果需要截图指导，进入一步一步模式
如果截图已经完成，优先修本地 Markdown
本地确认后，再同步 Feishu

If the user says "follow this workflow", execute the following by default:

First check the target chapter file and image directory
If screenshot guidance is needed, enter step-by-step mode
If screenshots are already completed, prioritize revising the local Markdown
After confirming locally, synchronize to Feishu

不要做的事

Things Not to Do

不要把写给作者自己的编辑备注留在读者版正文
不要在截图提示词里暴露“这是为了写书”
不要按大块素材占位盲插图片
不要在旧 Feishu 文档上反复乱修，造成更多错位
不要用模糊文件匹配规则批量找图

Do not leave author's personal editing notes in reader-facing text
Do not reveal "this is for book writing" in screenshot prompts
Do not blindly insert images into large material placeholders
Do not repeatedly modify old Feishu documents randomly, causing more misalignment
Do not use vague file matching rules to find images in batches