aref-vc/tufte
Apply Edward Tufte's principles to any data visualization, chart, dashboard, or infographic. Use when the user asks to produce, design, critique, or improve a chart, graph, dashboard, KPI tile, table-with-data, sparkline, small multiple, time series, distribution plot, choropleth, or any other visual that communicates quantitative or categorical information. Also triggers on words like "visualize", "viz", "data viz", "chart", "graph", "dashboard", "infographic", "Tufte". Outputs Tufte-compliant designs in either self-contained HTML/SVG or React (Recharts/D3). Defaults to Tufte rules; user can opt out per chart.
npx skills add https://github.com/aref-vc/tufte-claude-skill --skill tufte
This skill turns "make me a chart" into a Tufte-compliant chart. Distilled from *The Visual Display of Quantitative Information* (1983/2001), *Envisioning Information* (1990), and *Visual Explanations* (1997).
Two output stacks, selected by the user's project context:
When invoked, work through these in order:
principles.md — 10 rules, one paragraph each. The whole frame.chart-selection.md to pick the chart type from the user's data and goal. Don't reach for a chart you know; reach for the one this table prescribes.kill-list.md before rendering — strip the things that don't belong in any Tufte-compliant chart.before-after.html when the user wants to see the difference. Six side-by-side examples covering the cases AI tools default to badly.report-voice.md when the output is a report, recap, or slide with prose around the chart. The writing can ruin a clean chart. Plain business English, no em-dashes, no AI slop.checklist.md before declaring the chart done. Twenty items, takes 30 seconds.For a quick lookup, cheatsheet.html (and cheatsheet.pdf) is the one-page reference.
Tufte rules apply by default. If the user explicitly requests something on the kill list ("I need a pie chart for this board deck because the CFO wants one"), comply, but note the Tufte alternative in a one-line comment in the code or the response.
When the output is a report, recap, or slide, the text matters as much as the
chart. Write plain business English: no em-dashes, no drama or theatrics, no hype
verbs, no AI-slop jargon. Name every label and caption for the specific case, not
a placeholder. First the number, then what it means. See report-voice.md for
the full kill/keep list. A clean chart wrapped in slop reads as slop.
These are not in any Tufte-compliant chart unless the user explicitly overrides:
These belong in most Tufte charts:
--accent red), actually applied to the focal data point — not declared and left unused. Minimal ink is not the same as no signal. If nothing carries the accent, the chart is flat; pick the point the reader should look at and color it.| File | Purpose |
|---|---|
| principles.md | Tufte's 10 rules with practical interpretation |
| chart-selection.md | Data + goal → chart type decision table |
| kill-list.md | What to remove from any chart |
| before-after.html | Six side-by-side comparisons (open in browser) |
| report-voice.md | Prose rules for reports/recaps/slides (no slop, no em-dashes) |
| checklist.md | 20-item pre-publish check |
| cheatsheet.html | One-page printable reference |
| cheatsheet.pdf | Same, as PDF |
| presets/html-svg.md | Style tokens + a working SVG bar chart, line chart, sparkline, small multiple |
| presets/react.md | Recharts theme + D3 patterns for slopegraph, sparkline-in-table, small multiples |
Take aref-vc/tufte from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.