Math Figure Generator
Generate and render-verify publication-quality mathematical-modeling figures from saved...
Install
npx skills add zhnnky329/MathModeling-skills --skill math-figure-generator -g -a claude-code -y- Repository
- zhnnky329/MathModeling-skills1.1k
- Category
- Engineering
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Lightabout 526 tokens
- Runs scripts
- No, instructions only
What it does
Generate and render-verify publication-quality mathematical-modeling figures from saved evidence, using the approved figure plan, source data, claim, type, and consistent visual system.
Preconditions
- Figure type, source artifacts, and target claim are known.
- Type 3 claim is human-confirmed.
- Submission figures use final/frozen evidence.
References
Load only what the requested chart needs:
references/chart-patterns.mdreferences/color-systems.mdreferences/layout-guide.mdreferences/render-check.md
Workflow
- Verify source files and the exact variables/units to plot.
- Choose the smallest chart form that communicates the claim.
- Generate with deterministic code, preferably matplotlib.
- Save editable source code and the requested output format.
- Apply the shared color, typography, sizing, and labeling conventions.
- Render the final output and inspect it visually.
- Check clipping, overlap, illegible text, misleading axes, legends, empty panels, and source/claim mismatch.
- Iterate until render checks pass.
Output Locations
- Type 1/2 exploration:
results/Qx/experiments/roundN/figures/ - Type 3/4 submission:
paper/figures/
Use stable descriptive filenames. Do not copy Type 1 diagnostics into the paper directory.
Figure Requirements
- Labels include units where applicable.
- Captions state what is shown and the evidence-backed takeaway without overstating causality.
- Baseline is visually distinct but not exaggerated.
- Uncertainty is shown when it is part of the claim.
- Type 3 raster output is at least 300 dpi; vector output is preferred when compatible.
- Accessibility and grayscale differentiation are considered.
Rules
- Do not fabricate or manually alter plotted values.
- Do not use a chart type that hides concentration, uncertainty, or negative results.
- Do not truncate axes misleadingly.
- Do not create decorative 3D effects.
- Do not treat code execution as render verification.
- Keep diagnostic and paper roles separate.
