Figure Table Planner
Plan the smallest set of diagnostic, comparison, paper, and appendix figures or tables...
Install
npx skills add zhnnky329/MathModeling-skills --skill figure-table-planner -g -a claude-code -y- Repository
- zhnnky329/MathModeling-skills1.1k
- Category
- Engineering
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Lightabout 571 tokens
- Runs scripts
- No, instructions only
What it does
Plan the smallest set of diagnostic, comparison, paper, and appendix figures or tables needed to support verified mathematical-modeling decisions and claims.
Purpose
Make every visual evidence-bearing. Prefer fewer useful visuals over a decorative inventory.
Inputs
- method card and decision ledger;
- run summaries and final result analysis;
- robustness evidence;
- solution package and frozen numbers in submission mode;
- existing figures/tables.
Figure Types
- Type 1 diagnostic: internal debugging; never in the paper.
- Type 2 comparison: main vs usable baseline or a genuinely tested alternative; optional in paper.
- Type 3 paper: directly supports a main claim; required only when the claim benefits materially from a visual.
- Type 4 appendix: supplementary evidence referenced from the main text.
Workflow
- List verified claims that need visual or exact tabular support.
- Reuse an existing artifact when it already communicates the claim.
- For each proposed visual record:
- ID and Qx;
- type;
- source artifact and frozen claim IDs when applicable;
- one core claim;
- chart/table form;
- target section;
- status and render needs.
- Ask the human to confirm judgment-bearing Type 3 claims through one compact choice card when they are not already in the decision ledger.
- Save
methods/Qx/qx_figure_table_plan.mdonly when durable planning is needed. In lean exploration, a compact in-conversation plan is sufficient.
Planning Heuristics
- Use tables for exact values, parameters, and small comparisons.
- Use plots for trends, distributions, sensitivity, or many-item comparisons.
- Use diagrams for mechanisms, dependencies, and workflows.
- A main-vs-baseline figure needs compatible metrics and the same evaluation setup.
- Do not create a multi-method comparison merely to imply breadth.
