Figures logo

Figures

Community
scdenney
figures

Designs publication figures for social-science manuscripts. Covers chart choice, axes and scales, color and accessibility, legend order, captions that carry the title, and script-based reproducibility. Use when making, revising, or critiquing a figure for a paper, such as a coefficient plot, small multiples, a distribution, a trend, a map, or a network. Finished figure sets go to figure-table-audit for end-stage QA.

Overview

Publisherscdenney
Repositoryopen-science-skills
Skill namefigures
Stars
69
Forks
3
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by scdenney on GitHub. Read the source before you install it.

Installation

Install the Figures AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/scdenney/open-science-skills/tree/main/plugin/skills/figures
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/scdenney/open-science-skills.git /tmp/open-science-skills
mkdir -p .claude/skills
cp -r /tmp/open-science-skills/plugin/skills/figures .claude/skills/figures
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Figures in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Figures on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Figures is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Figure Designer

Applies to any figure type in a social-science manuscript. For figures whose interpretation depends on method-specific standards, also consult the relevant sibling skill (conjoint-design, conjoint-diagnostics, list-experiment, topic-modeling, text-classification, vlm-ocr). For end-stage QA on a finished figure set, hand off to figure-table-audit.

A figure is ready when it makes one comparison legible, can be read without the surrounding text, and can be regenerated from a script.

Instructions

1. State the comparison before drawing

Write down, in one sentence, what the figure should let the reader see (for example, "The treatment effect is larger among low-information respondents"). If the comparison does not fit in one sentence, the figure has too many goals; split it into panels or separate figures.

2. Choose the chart type from the comparison

Match the geometry to the comparison, not to the data type. Two defaults that are often missed:

  • Effect estimates compared across models or subgroups go in a coefficient plot (point and interval), not a regression table.
  • Many small comparisons go in small multiples on a shared scale, not in separate figures.

Pie, donut, 3D, and dual-axis charts do not belong in academic figures.

3. Pick scales and axes deliberately

  • Label both axes with the quantity and its units: "Household income (USD, 2020)", not "Income".
  • For percentages, write 0.00–1.00 or 0%–100% consistently — do not mix within a figure.
  • Use a log scale when the data span more than two orders of magnitude or when a multiplicative effect is the substantive story, and label the scale as log.
  • Anchor axes at zero only when zero is meaningful for the comparison (counts, proportions). Deviations, differences, and z-scores need no zero baseline.
  • Use the same y-axis range across panels of small multiples unless the claim is explicitly about within-panel scale.
  • Reverse the y-axis only when the substantive direction demands it (e.g., rank where 1 is "best") and label the reversal in the caption.

4. Choose color with intent

  • Sequential (light → dark): for ordered/quantitative variables (income brackets, time, density).
  • Diverging (red ↔ blue, etc.): for variables with a meaningful midpoint (effect sign, deviation from baseline).
  • Categorical: for unordered groups; use a colorblind-safe palette (Okabe-Ito, viridis discrete, ColorBrewer Set2/Dark2).
  • Test grayscale: convert the figure and check that the comparison still reads. If it does not, add shape, line type, or direct labels.
  • Encoding one variable in both color and shape is fine as an accessibility aid; keep the legend consistent with it.
  • Replace default rainbow / jet ramps, which are not perceptually uniform.

5. Match legend order to the visual order in the chart

Legend order mirrors the data's visual order, so the reader can match series without scanning back and forth:

  • For lines, areas, or stacked elements arranged top-to-bottom in the plot at the rightmost x-value, list legend entries in the same top-to-bottom order.
  • For bars or categories arranged left-to-right, use a horizontal legend listed left-to-right in the same order.
  • For panels (small multiples), follow the panel grid: rows top-to-bottom, columns left-to-right.
  • Do not alphabetize a legend when the data have a natural order (time, magnitude, treatment intensity, ordinal scale). ggplot2 and similar libraries sort character variables alphabetically by default, and the result is a frequent cause of misreading.
  • With five or fewer series, label lines or bars directly at their ends instead of using a legend.
  • When a legend is needed, place it where it does not cover data.

6. Put the title in the caption, not inside the figure

Keep titles and subtitles out of the plotting area. The figure's title, and any explanatory note, belong in the document as the caption beneath the figure, set in the manuscript's font and editable alongside the prose. A title rendered inside the image duplicates the caption, sets in a mismatched typeface, and cannot be changed without regenerating the plot. Strip ggtitle(), labs(title=, subtitle=), plt.title(), and plt.suptitle() from the figure script and let the caption carry the title. (Panel tags such as "A" and "B" inside a multi-panel figure are fine; a descriptive title is not.)

The caption must be self-contained: a reader who skims should understand the figure from the caption alone. Include:

  • What is plotted (the dependent quantity, the unit of analysis).
  • The sample (N, source, time window).
  • The uncertainty interval (e.g., "95% confidence intervals from cluster-robust standard errors").
  • Panel meanings, if multi-panel.
  • Any transformations or exclusions.
  • The estimand or model family if the figure is showing model output (not just "Results").

Keep abbreviations defined and units explicit.

7. Make it reproducible

  • Generate the figure from a script (R, Python, Stata, Julia) in the replication archive. Hand edits in Illustrator or Inkscape are acceptable only when the manual step is documented.
  • Save with the script: input data path, package versions, random seed (for jittered or sampled plots), output dimensions.
  • Export vector (PDF, SVG) for plots with text and lines; export raster (PNG at ≥300 dpi) only for raster-native content (heatmaps with thousands of cells, photographs, maps with imagery).
  • Use a single ggplot/matplotlib theme across the manuscript so figures are visually consistent.
  • For multi-panel figures, build with patchwork/cowplot/gridExtra or matplotlib's subplots/gridspec — not by stitching exported PNGs in Word.

8. Accessibility and production sanity

  • Axis label and tick text ≥ 8pt at print size.
  • Alt text for journals that require it (a one-sentence description of what the figure shows).
  • Consistent figure dimensions and fonts across the manuscript.

Output

When asked to design or revise a figure, produce:

# Figure Plan

Comparison: <one sentence>
Chart type: <type and why>
Geometry: <axes, scales, faceting>
Color encoding: <palette, what it encodes, accessibility check>
Legend / labeling: <direct label or legend; order matches visual order>
Caption draft: <self-contained>
Reproducibility: <script path, packages, output format and dimensions>
Open issues: <anything that needs author input — denominator choice, sample restriction, etc.>

When asked to produce code, default to a single ggplot2 (R) or matplotlib + seaborn (Python) script with the theme, palette, and figure dimensions explicit at the top.

Frequently asked questions

What does the Figures AI skill do?

Designs publication figures for social-science manuscripts. Covers chart choice, axes and scales, color and accessibility, legend order, captions that carry the title, and script-based reproducibility. Use when making, revising, or critiquing a figure for a paper, such as a coefficient plot, small multiples, a distribution, a trend, a map, or a network. Finished figure sets go to figure-table-audit for end-stage QA.

Why use Figures on TypingMind?

Because you install it once and use it with any model. Figures is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Figures in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/scdenney/open-science-skills/tree/main/plugin/skills/figures. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Figures?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Figures?

As many as you like. As long as a model supports skills, you can use Figures with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Figures AI skill free?

It is published on GitHub by scdenney. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇