the-canonical-figure

Solid

Use when planning figures, at study design and again before writing. Covers the figures a paper in this field is expected to contain, why an original figure does not substitute for a standard one, and how to decide what to draw first.

AI & Automation 804 stars 25 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 82/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Draw the field's standard figure before your own Every field has one or two figures a paper of that kind is expected to contain. A reader looks for them first, and their absence is read as the analysis not having been done — even when the same information is present somewhere else, in a table, in prose, or inside a figure you designed yourself. Some examples of the shape, not a checklist: - Bayesian parameter inference is expected to show the joint posterior — a corner or triangle plot over the parameters — not only marginal summaries or a table of medians and intervals. - An iterative optimiser is expected to show objective against iteration, log scale, your method and the baseline on the same axes. - Anything trained is expected to show the learning curves: training and validation loss against epoch, on the same panel, so overfitting is visible. - A spatial field is expected to be shown as a map, per epoch or lead time, beside the reference field — not summarised into one error number. - A classifier is expected to show the curve its threshold moves along, not one operating point. ## Why your own figure does not substitute You will usually find something more interesting than the standard plot, and it is right to show it. But an original figure answers a question the reader did not ask yet. The standard one answers "did the thing work, in the way this field checks that". Publish both, standard first. ## The trace has to be written down while it exists A...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
5 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

figures

Design and format publication-quality figures. Use for chart choice, color, scales, legends, captions, accessibility, and reproducible figure workflows.

45 Updated 3 days ago
scdenney
AI & Automation Solid

draw-the-system-not-your-study

Use at study design when allocating figure slots, and again at analysis and writing, on tasks where the source's own rendered figures are not available to copy. Covers the four slots reserved for the system before any hypothesis claims one, drawing the loaded arrays instead of their counts, why a panel that reports a shortfall is not the panel carrying the result, and why a deliverable marked covered_by an artifact path is not covered.

804 Updated today
tangxiangru
Testing & QA Listed

figure-style

Publication-grade figure correctness and legibility rules. Load before drawing any plot and call `apply_figure_style()` — sets a role-mapped font-size ladder, outward ticks, frameless legends, and 300-dpi output. The skill is a checklist, not a house look: data fidelity (claim-titles tested against every row, excluded data never enters summaries), label economy (floor and ceiling), colour threading, chart-choice-by-data-shape, layout, and a render-then-verify QA loop (bbox collision + per-panel perceptual check). Ships helpers: focal_palette, bar_with_points, strip_with_median, end_of_line_labels, panel_letter, set_frame, panel_crops. For multi-panel figures load `figure-composer`; for whole-paper figure arc load `paper-narrative`.

3 Updated 2 weeks ago
emaballarin