跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

paper-visual-craft

Use when designing, redrawing, or validating research-paper figures and tables, including Matplotlib plots, LaTeX tables, benchmarks, captions, legends, annotations, color, and typography. Preserves exact evidence and checks rendered PDFs for clipping, overlap, and readability.

sidiangongyuan · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add sidiangongyuan/codex-skills-library --skill paper-visual-craft

技能说明


name: paper-visual-craft description: Use when designing, redrawing, or validating research-paper figures and tables, including Matplotlib plots, LaTeX tables, benchmarks, captions, legends, annotations, color, and typography. Preserves exact evidence and checks rendered PDFs for clipping, overlap, and readability. license: MIT

Paper Visual Craft

Routing Boundary

  • Use $paper-framework-figure-studio-pro first for source-grounded framework figure, method overview, architecture diagram, pipeline/process figure, system/data-flow figure, mechanism schematic, or agent workflow planning.
  • Return to $paper-visual-craft for final figure/table polish, Matplotlib or LaTeX edits, captions, color/typography cleanup, and rendered PDF/PNG validation.

Incremental Maintenance

  • For a local number, caption, or format fix, reuse the established paper story and table contract. Verify the scoped source and connected text only; do not restart story questioning, re-freeze the contract, run a full literature review, or rerun experiments for cosmetic-only changes.

Core Workflow

  1. Inspect before editing.

    • Read the paper context around the target figure or table.
    • Locate the source data, generation script, LaTeX include block, captions, and any reference visual the user named.
    • If data provenance is unclear, stop and identify the exact missing source instead of redrawing from copied numbers.
  2. Classify the visual.

    • Decide whether it is a main-result figure, appendix diagnostic, dataset/statistics figure, ablation table, reliability/control table, or qualitative panel.
    • Keep main-paper visuals compact and claim-focused. Use appendix visuals for diagnostics, extended controls, and richer tables.
    • For dataset or benchmark papers, ask what story the visual supports: benchmark positioning, annotation effort, evidence source, main control, or diagnostic richness.
    • Put the comparison axis first. The reader should immediately know what is being compared and what conclusion to read; the visual should not preserve implementation history, generated-condition inventories, or debug process unless those are the claim.
    • Prefer a simple table for categorical comparisons and component ablations. Do not turn a row-and-column question into a complex diagram merely to make the presentation look more elaborate.
  3. Freeze the table contract before experiments or a new visual contract.

    • When planning results, define the final rows, columns, comparison axis, claim owner, and reference row before runs start.
    • For each metric, record its plain definition, unit, direction, aggregation population, precision, and any delta reference or sign convention.
    • If a LaTeX manuscript is in scope, add the final table scaffold there. Use the project's explicit draft schema for missing values: preserve distinct markers for pending results (such as TBD) and inapplicable entries (such as N/A), or use -- when that is the specified marker. Keep internal completion status out of captions and paper prose; before submission, resolve pending markers as required while allowing structural N/A to remain. Do not leave unrun result claims or internal notes.
  4. Preserve measurement integrity.

    • Preserve exact values, units, sample counts, conditions, and axis semantics.
    • Do not mix raw values, percentages, percentage-point deltas, and relative deltas inside one visual unless the caption makes the units explicit.
    • For a new numeric value or result row, read the value from the project's source summary or artifact before inserting it. Fit it to the table's existing measurement schema, then check precision, named reference, metric direction, and delta sign. If the table uses reference cells, deltas, arrows, or semantic colors, compute the comparison with the same precision and directionality; do not paste raw values into a delta-coded table.
    • Put interpretation in captions or prose, not inside plot areas, unless a small label clarifies a data point without occluding information.
    • Let a complete table or caption carry secondary metrics and tradeoffs when their units, directions, comparison scope, and necessary conditions are clear. Let the surrounding prose carry the main finding; do not restate a table-visible tradeoff as a negative conclusion. Keep a boundary in prose when it changes fairness, applicability, or claim interpretation.
    • For diagnostic figures, show metric behavior without implying a causal mechanism unless the experimental design directly tests causality. The caption should say what the diagnostic supports and what it does not prove.
    • When table rows, columns, panels, or layout change, update the caption, nearby prose, cross-references, and later interpretive paragraphs in the same pass. A table edit is incomplete if the surrounding text still describes the old rows or comparison target, or if a new row omits the table's required reference/delta semantics.
  5. Design with restrained hierarchy.

    • Prefer vector outputs for papers and PNG previews for inspection.
    • Use consistent legends, typography, line weights, tick formatting, row highlights, and caption structure.
    • Reserve whitespace for endpoint labels and callouts; avoid labels floating over trends, bars, or dense table cells.
    • For table heatmaps, use semantic color rather than raw sign, fixed-width colored cells, and delta text that is visually smaller than the main value.
    • When a caption defines color semantics, color the color words themselves, such as green, red, amber, or blue.
    • Do not use unconditional table resizing to make a table fill the page width. Resize only to shrink a naturally overwide table; never enlarge a table that already fits.
    • Preserve the reader's intended comparison axis. For appendix dia
阅读完整来源 ↗