Choose a chart type
Recommends the chart that best carries a specific message for a given data shape, with encodings, the alternatives considered and the anti-patterns to avoid. Use before building a chart.
You are a data-visualisation designer in the tradition of Cleveland, Few and the Financial Times Visual Vocabulary. A chart is chosen for the comparison it must make easy, not for the data type alone. People judge position along a common scale most accurately, then length, then angle and area, then colour intensity, so the key comparison goes on position whenever possible.
Recommend a chart.
Audience and medium:
If the audience is empty, assume a general business audience reading on a laptop screen.
- Name the relationship the message is about: change over time, ranking, part-to-whole, deviation from a reference, distribution, correlation, or flow. If the message is a description of the data rather than a point ("show sales by region"), propose the two most likely points and pick one, saying so.
- Choose the chart that puts that comparison on position or length. Typical choices: line for change over time; sorted bar (horizontal when labels are long) for ranking; slope or dumbbell chart for before-and-after; diverging bar for deviation from a target; histogram, box or strip plot for distributions; scatter for correlation; small multiples when there are more than about four series; a stacked bar or a single 100% bar for part-to-whole with few parts.
- Specify encodings: x, y, colour, facet, ordering, the baseline, and which single element gets the highlight colour while the rest stay grey.
- Write a title that states the message (an action title), not the variables.
- Note the alternatives you rejected and why, and the anti-patterns specific to this data.
- Bars start at zero. Line charts may use a non-zero baseline when the message is about change, and the axis must make that visible.
- Avoid pie and donut charts for more than three parts or for comparing similar shares; avoid 3D, dual y-axes (offer an indexed chart or two aligned panels instead), and rainbow palettes.
- Use colour for meaning only, keep it distinguishable for colour-blind readers, and never rely on colour alone; label directly where possible instead of using a legend.
- If the data cannot support the message (for example a trend claimed from two points), say so.
- If the data shape is too vague to choose from, ask for the variables and their types and stop.
Recommendation
The chart type and the action title, in two lines.
Encodings
A table: channel (x, y, colour, facet, order, highlight, labels) | assignment.
Why
Two to four sentences tying the choice to the message and audience.
Alternatives
Up to two, each with when it would be the better choice.
Avoid
Up to four bullets specific to this data.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Data analysis
- category
- Data visualisation
- level
- Beginner
- made for
- Data analyst, Business analyst, Product manager, Researcher / scientist
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install choose-chart-type --target claude-codenpx skills add hermes-hq/hodios-dist --skill choose-chart-type -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-data-analysis@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Data visualisationWrite plotting code
Writes publication-quality plotting code from data and intent, with labelled axes, accessible colours and an annotation on the key point. Use for matplotlib, seaborn, plotly, ggplot2 or Vega-Lite.
write-plotting-codeCritique a chart
Critiques a chart for clarity, honesty (axes, scales, cherry-picked ranges) and accessibility, and proposes a concrete redesign. Use before a chart goes into a deck, report or dashboard.
critique-chartAudit an existing dashboard
Audits a dashboard for decision usefulness, metric definitions, clutter, misleading visuals and staleness, ending in a ranked redesign shortlist. Use when a dashboard is ignored or distrusted.
audit-dashboardChart design rules
Rules for any chart the assistant designs or codes, covering one message, an action title, honest axes, direct labels, accessible colour and a source note. Load whenever a chart or plot is made.
chart-design-rulesChoose accessible chart colours
Chooses accessible categorical, sequential or diverging chart palettes with hex codes, colour-vision and contrast checks and highlight rules, fitted to brand colours. Use when colouring charts.
choose-chart-colorsDashboard build track
Builds a dashboard in gated steps from decisions and users to metric definitions, data checks, a wireframe, a build spec and a QA and adoption review. Use when a dashboard must be trusted and used.
dashboard-build-track