polish-sci-figures

Polish Scientific Figures

Deliver the near-final figure in one internal pass: establish the claim and final placement, trace the authoritative data, compare the existing and proposed forms, draw, export, inspect at real size, correct, and package. Do not make the user rediscover alignment, canvas, font, overlap, scientific-label, or editability defects.

Accept everyday requests such as “帮我把这张表画成适合论文的图”. Inspect the input first, present a few suitable candidates with plain-language explanations, and ask only for consequential facts the data cannot establish. Let users make routine appearance changes directly in Studio without another model call; do not require specialist vocabulary or a structured prompt.

Verify the agent's Python runtime first

Before running a bundled Python script, choose and verify an existing interpreter yourself. Prefer the current project's .venv/Scripts/python.exe (Windows) or .venv/bin/python, then a runtime exposed by the host's dependency tools; only then inspect registered Python launchers or python3. Do not assume that bare python is Python 3, or that a host-bundled interpreter includes scientific packages. Read-only checks should try the next available candidate before asking the user to install anything.

First run the candidate with -c "import sys; print(sys.executable); print(sys.version); sys.exit(0 if (3,10) <= sys.version_info[:2] <= (3,12) else 2)". For a supported interpreter, actually import numpy, pandas, scipy, matplotlib, openpyxl and PIL; a package-directory listing is not a successful import. If the full suite is present, run that interpreter's sci_figures.py doctor --font SELECTED_FONT --json for the remaining font and environment checks. Reuse the verified executable for every command and subprocess, with -X utf8 on Windows; python in examples means this verified executable.

If no candidate passes, identify the specific missing runtime/package and propose a task-local environment or the installed Figure Studio option. Do not modify PATH, install into the global interpreter, or ask a novice to guess executable paths. Runtime checks are the agent's work; the user's ordinary-language request is sufficient.