Engineering Figure Agent For Claude Code
Use this skill for the figure-production layer after the figure goal is reasonably clear.
If the figure claim, panel logic, or caption argument is still unclear, first use a research-writing or paper-analysis workflow to settle the scientific message.
Core Decision
- Use
image mode for conceptual figures: system architecture, algorithm workflow, graphical abstract, hardware block diagram, or reference-inspired redraw.
- Use
plot mode for exact values: benchmark bars, ablation plots, trend curves, heatmaps, scatter plots, or multi-panel quantitative figures.
- Use
mixed when exact plot panels should be rendered locally and conceptual panels should be generated or described separately.
Workflow
- Inspect the user's paper context, data, caption draft, or figure brief.
- Create or normalize a figure brief with
figure_goal, paper_claim, figure_type, mode, panels, must_keep_labels, data, style_constraints, output_formats, and verification_checklist.
- If numeric truth matters and data is missing, ask for values instead of inventing them.
- For image mode, produce a final prompt using concise labels, white background, publication style, and faithful technical terms.
- For plot mode, produce a concise plot-request JSON. Use
data.series[] for multi-series scatter plots, and use outside or dedicated legends for dense annotated charts.
- Keep real API keys outside the repository.
- Require explicit user opt-in before sending API keys, prompts, or files to third-party provider endpoints.
- For high-resolution or final-export requests, fail closed if the configured high-resolution path is unavailable instead of silently downgrading.
- Treat generated diagrams as drafts until labels, scientific claims, and numeric values are verified.
Output Files
Prefer these files when writing to disk:
figure-brief.md
prompt.txt
plot-request.json
output/
Quality Rules
- Do not fabricate measurements, benchmark improvements, device values, or unsupported causal claims.
- Keep labels readable at paper width.
- Preserve standard English symbols and formulas in Chinese figures when they improve clarity.
- Never use image generation for exact numeric chart geometry.
- Do not present light figure critique as a full reviewer-style paper-figure audit.
Source: heyu-233/engineering-figure-agent — distributed by TomeVault.
1---2name: heyu-233-engineering-figure-agent-engineering-figure-agent3description: Engineering Figure Agent For Claude Code4---56# Engineering Figure Agent For Claude Code78Use this skill for the figure-production layer after the figure goal is reasonably clear.910If the figure claim, panel logic, or caption argument is still unclear, first use a research-writing or paper-analysis workflow to settle the scientific message.1112## Core Decision1314- Use `image mode` for conceptual figures: system architecture, algorithm workflow, graphical abstract, hardware block diagram, or reference-inspired redraw.15- Use `plot mode` for exact values: benchmark bars, ablation plots, trend curves, heatmaps, scatter plots, or multi-panel quantitative figures.16- Use `mixed` when exact plot panels should be rendered locally and conceptual panels should be generated or described separately.1718## Workflow19201. Inspect the user's paper context, data, caption draft, or figure brief.212. Create or normalize a figure brief with `figure_goal`, `paper_claim`, `figure_type`, `mode`, `panels`, `must_keep_labels`, `data`, `style_constraints`, `output_formats`, and `verification_checklist`.223. If numeric truth matters and data is missing, ask for values instead of inventing them.234. For image mode, produce a final prompt using concise labels, white background, publication style, and faithful technical terms.245. For plot mode, produce a concise plot-request JSON. Use `data.series[]` for multi-series scatter plots, and use outside or dedicated legends for dense annotated charts.256. Keep real API keys outside the repository.267. Require explicit user opt-in before sending API keys, prompts, or files to third-party provider endpoints.278. For high-resolution or final-export requests, fail closed if the configured high-resolution path is unavailable instead of silently downgrading.289. Treat generated diagrams as drafts until labels, scientific claims, and numeric values are verified.2930## Output Files3132Prefer these files when writing to disk:3334```text35figure-brief.md36prompt.txt37plot-request.json38output/39```4041## Quality Rules4243- Do not fabricate measurements, benchmark improvements, device values, or unsupported causal claims.44- Keep labels readable at paper width.45- Preserve standard English symbols and formulas in Chinese figures when they improve clarity.46- Never use image generation for exact numeric chart geometry.47- Do not present light figure critique as a full reviewer-style paper-figure audit.4849---50> Source: [heyu-233/engineering-figure-agent](https://github.com/heyu-233/engineering-figure-agent) — distributed by [TomeVault](https://tomevault.io).51<!-- tomevault:4.0:skill_md:2026-06-22 -->