输出规则（必读）

• 只保存到本地：所有生成或编辑的文件保存到用户指定路径或当前工作目录，操作完成后告知用户完整的文件路径。
• 禁止向对话发送文件内容：不要将文件内容（文本、二进制、base64 等任何形式）粘贴或发送到用户的聊天/会话中。大文件会导致整个 session 卡死。
• 如需预览：只在对话中展示简短的摘要信息（如文档标题、页数等元信息），不要展示完整内容。

工具调用纪律

• 禁止读取源代码文件（.py / .js / .sh）。所有操作通过 Quick Start 命令完成。
• 禁止手动编辑中间文件（tokens.json、XML 等）。如需自定义参数，使用 CLI 的 --flag。
• 命令失败时：只看错误信息的最后几行，不要去读源码调试。常见错误见下方 Troubleshooting。
• reference 文件：design/design.md 仅在需要自定义设计风格（字体、颜色、布局）时阅读，常规使用无需阅读。
• 依赖安装：只运行一次环境准备脚本，不要手动重复 pip install 或 npx playwright install。
• Windows 注意：使用 python（不是 python3），使用 python scripts/run_pipeline.py 代替 bash scripts/make.sh run。

环境准备（首次使用 必须自动执行，无需询问用户）

读完本 SKILL.md 后，立即静默运行依赖安装脚本。不要问用户是否需要安装。

# macOS / Linux / WSL
bash scripts/make.sh fix

# Windows（PowerShell）
powershell -ExecutionPolicy Bypass -File scripts/setup_deps.ps1

无需单独运行 check，也无需手动 pip install 或 npm install。脚本已包含全部依赖的检测与安装。

平台检测： 如果 bash 命令不可用（Windows CMD），改用 python scripts/run_pipeline.py（见 Quick Start）。Windows 上 Python 命令是 python（不是 python3）。

minimax-pdf

Three tasks. One skill.

Quick Start

创建 PDF：

# macOS / Linux / WSL
bash scripts/make.sh run \
  --title "Report Title" --type report \
  --author "Author" --accent "#2D5F8A" \
  --content content.json --out report.pdf

# Windows（CMD 或 PowerShell）
python scripts/run_pipeline.py --title "Report Title" --type report --author "Author" --accent "#2D5F8A" --content content.json --out report.pdf

填写 PDF 表单：

# macOS / Linux
python3 scripts/fill_inspect.py --input form.pdf
python3 scripts/fill_write.py --input form.pdf --out filled.pdf \
  --values '{"Name": "张三", "Date": "2025-04"}'

# Windows
python scripts/fill_inspect.py --input form.pdf
python scripts/fill_write.py --input form.pdf --out filled.pdf --values "{\"Name\": \"张三\", \"Date\": \"2025-04\"}"

重排现有文档：

# macOS / Linux
bash scripts/make.sh reformat \
  --input source.md --title "标题" --type report --out output.pdf

# Windows — 先用 reformat_parse.py 提取内容，再走 run_pipeline.py
python scripts/reformat_parse.py --input source.md --out content.json
python scripts/run_pipeline.py --title "标题" --type report --content content.json --out output.pdf

文档类型速查： report · proposal · resume · portfolio · academic · general · minimal · stripe · diagonal · frame · editorial · magazine · darkroom · terminal · poster

CJK 中文支持： 自动检测。当 content.json 包含中文/日文/韩文时，自动注册系统 CJK 字体并切换为左对齐排版。无需手动配置字体路径。

Route table

Rule: when in doubt between CREATE and REFORMAT, ask whether the user has an existing document to start from. If yes → REFORMAT. If no → CREATE.

Route A: CREATE

Full pipeline — content → design tokens → cover → body → merged PDF.

# macOS / Linux / WSL
bash scripts/make.sh run \
  --title "Q3 Strategy Review" --type proposal \
  --author "Strategy Team" --date "October 2025" \
  --accent "#2D5F8A" \
  --content content.json --out report.pdf

# Windows
python scripts/run_pipeline.py --title "Q3 Strategy Review" --type proposal --author "Strategy Team" --date "October 2025" --accent "#2D5F8A" --content content.json --out report.pdf

Doc types: report · proposal · resume · portfolio · academic · general · minimal · stripe · diagonal · frame · editorial · magazine · darkroom · terminal · poster

Cover extras (inject into tokens via --abstract, --cover-image):

• --abstract "text" — abstract text block on the cover (magazine/darkroom)
• --cover-image "url" — hero image URL/path (magazine, darkroom, poster)

Color overrides — always choose these based on document content:

• --accent "#HEX" — override the accent color; accent_lt is auto-derived by lightening toward white
• --cover-bg "#HEX" — override the cover background color

Accent color selection guidance:

You have creative authority over the accent color. Pick it from the document's semantic context — title, industry, purpose, audience — not from generic "safe" choices. The accent appears on section rules, callout bars, table headers, and the cover: it carries the document's visual identity.

Rule: choose a color that a thoughtful designer would select for this specific document — not the type's default. Muted, desaturated tones work best; avoid vivid primaries. When in doubt, go darker and more neutral.

content.json 格式： 必须是 JSON 数组（[...]），每个元素是一个 block 对象。不要写成单个对象 {}。示例：[{"type":"h1","text":"标题"}, {"type":"body","text":"正文段落"}]

content.json block types:

chart / flowchart schemas:

{"type":"chart","chart_type":"bar","labels":["Q1","Q2","Q3","Q4"],
 "datasets":[{"label":"Revenue","values":[120,145,132,178]}],"caption":"Q results"}

{"type":"flowchart",
 "nodes":[{"id":"s","label":"Start","shape":"oval"},
          {"id":"p","label":"Process","shape":"rect"},
          {"id":"d","label":"Valid?","shape":"diamond"},
          {"id":"e","label":"End","shape":"oval"}],
 "edges":[{"from":"s","to":"p"},{"from":"p","to":"d"},
          {"from":"d","to":"e","label":"Yes"},{"from":"d","to":"p","label":"No"}]}

{"type":"bibliography","items":[
  {"id":"1","text":"Author (Year). Title. Publisher."}]}

Route B: FILL

Fill form fields in an existing PDF without altering layout or design.

# Step 1: inspect (macOS: python3, Windows: python)
python3 scripts/fill_inspect.py --input form.pdf

# Step 2: fill
python3 scripts/fill_write.py --input form.pdf --out filled.pdf \
  --values '{"FirstName": "Jane", "Agree": "true", "Country": "US"}'

Windows 用户： 将上方 python3 替换为 python。

Always run fill_inspect.py first to get exact field names.

Route C: REFORMAT

Parse an existing document → content.json → CREATE pipeline.

# macOS / Linux / WSL
bash scripts/make.sh reformat \
  --input source.md --title "My Report" --type report --out output.pdf

# Windows — 分两步
python scripts/reformat_parse.py --input source.md --out content.json
python scripts/run_pipeline.py --title "My Report" --type report --content content.json --out output.pdf

Supported input formats: .md .txt .pdf .json

Environment

# macOS / Linux
bash scripts/make.sh check   # verify all deps
bash scripts/make.sh fix     # auto-install missing deps

# Windows
powershell -ExecutionPolicy Bypass -File scripts/setup_deps.ps1

Troubleshooting