tufte-viz
Skill20 starsChanged 4 days agoMITView on GitHub
Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays Applies principles: data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, and data density.
6 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- pskoett/pmx-canvasedited, first seen Oct 20, 2026
- nbbaier/agent-skillsedited, first seen Jul 8, 2026
- pjsny/tufte-vizedited, first seen May 25, 2026
- HugoVeltorai/publicskillstheir own version, first seen May 25, 2026
- aparente/claude-skillsword for word, first seen May 24, 2026
- ImpactMojo/ImpactMojoedited, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 1
- aparente/claude-skills★ 65100% same
Edited · 4
- pskoett/pmx-canvas★ 3136% same
- nbbaier/agent-skills★ 1599% same
- pjsny/tufte-viz★ 1098% same
- ImpactMojo/ImpactMojo★ 399% same
Wrote their own version · 1
- HugoVeltorai/publicskills★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- grill-meSkill
- paper-reviewSkill
- plain-speechSkill
- review-docSkill
- see-uiSkill
- tufte-vizSkill
- grill-meSkill
- paper-reviewSkill
- plain-speechSkill
- review-docSkill
- see-uiSkill
The file
We split this skill into the rules it gives an agent
6 rules. 5 are common, 1 is distinctive, and 0 are very specific to this project.
5
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 34
Start minimal, add only what's necessary
- Common: line 35
Every element must earn its ink
- Common: line 36
Default to grayscale; use color purposefully
- Distinctive: line 41
If two elements compete for the same job, keep the visual one and drop the textual one (or vice versa) — not both.
- Common: line 55
Verify baselines and scales
- Common: line 56
Look for 3D distortion
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tufte Visualization Ideation
Apply Edward Tufte's principles to design clear, honest, high-density data visualizations.
Workflow
For new visualizations:
- Clarify the data story
- What comparisons matter?
- What's the key insight to communicate?
- Who's the audience?
- Select approach using Tufte principles:
- High comparison need → Small multiples
- Dense data → Consider data tables, sparklines
- Time-series → Line charts with minimal grid
- Part-to-whole → Avoid pie charts; prefer bar/table
- Design with data-ink in mind
- Start minimal, add only what's necessary
- Every element must earn its ink
- Default to grayscale; use color purposefully
- Apply the eraser test before shipping
- For every element (label, tick, gridline, border, annotation): can it be erased without losing information that's not already conveyed elsewhere?
- Watch for duplicate encodings: numeric labels next to a value already marked by a tick; legends duplicating direct labels; per-panel scale annotations duplicating a shared-scale caption.
- If two elements compete for the same job, keep the visual one and drop the textual one (or vice versa) — not both.
- Apply the collision test before shipping
- For every text element in the plot (axis labels, point annotations, epoch labels, baseline labels, explanatory notes): mentally draw its bounding box. Does anything else — another text element, a data line, dense markers — live in or cross that box?
- The eraser test catches redundant elements; the collision test catches crowded ones. Both must pass.
- Standard fixes: move explanatory prose out of the plot into the figcaption; relocate band/epoch labels to a dedicated strip above the plot; push baseline/reference labels to the outside margin; give each in-plot annotation a leader line so the marker and the text occupy clearly separated space.
- Watch especially: inverted axes (top of plot is now where extreme values cluster, where annotations also want to go); shared-scale small multiples (labels stacked near zero in every panel); dense scatter (text vanishes into the dot cloud unless explicitly cleared).
- Apply the Tufte test (see references/tufte-principles.md)
For critiquing visualizations:
- Check graphical integrity
- Calculate lie factor if proportions seem off
- Verify baselines and scales
- Look for 3D distortion
- Identify chartjunk
- Decorative elements
- Heavy grids
- Unnecessary 3D effects
- Moiré patterns
- Evaluate data-ink ratio
- What can be erased?
- What's redundant?
- Suggest improvements with specific before/after recommendations
Key Principles Reference
references/tufte-principles.md— core principles from Visual Display of Quantitative Information: lie factor, data-ink, chartjunk, small multiples, integrity.references/analytical-design.md— extensions from Envisioning Information, Visual Explanations, and Beautiful Evidence: the 6 principles of analytical design, sparklines, layering & separation, micro/macro, range-frames, causality, confections. Load when designing dashboards, dense displays, sparklines, or explanatory graphics.
Quick checklist:
- Lie Factor ≈ 1.0 (no visual distortion)
- Maximum data-ink ratio
- Zero chartjunk
- Clear labeling
- Answers "compared to what?"
- Shows causality or mechanism where relevant
- Multivariate (not over-reduced)
- Words, numbers, images integrated — not segregated
- Reveals multiple levels of detail (micro + macro)
- Layering: primary data dominates, secondary recedes
- Appropriate data density
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

