@edmundmiller/tufte-viz
AIdeate 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.
Install
agr install @edmundmiller/tufte-viz --target claudeWrites 1 file into .claude/skills/, pinned to git-2301ad20.
- .claude/skills/tufte-viz/SKILL.md
Document
name: tufte-viz description: | 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.
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 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
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-2301ad20d0af2026-07-31