tufte-viz

Solid

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.

Code & Development 19 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Tufte Visualization Ideation Apply Edward Tufte's principles to design clear, honest, high-density data visualizations. ## Workflow ### For new visualizations: 1. **Clarify the data story** - What comparisons matter? - What's the key insight to communicate? - Who's the audience? 2. **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 3. **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 4. **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. 5. **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 — l...

Details

Author
angadhn
Repository
angadhn/botference
Created
5 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

tufte

Apply Edward Tufte's information design principles to create, improve, or critique any chart, graph, infographic, dashboard, table, or data visualization. Use this skill whenever the user wants to design a new chart, graph, or visualization from data; asks how to show data more clearly; wants to review or critique an existing graphic, report, dashboard, or infographic; asks about chartjunk, data-ink ratio, lie factor, small multiples, sparklines, or visual integrity; is choosing between chart types; wants to make a visualization honest, dense, or clear; mentions "compared to what?"; or asks about visual storytelling with data. Do NOT wait for the user to say "Tufte" — intervene proactively any time data needs to be shown visually.

8 Updated 2 weeks ago
kogakure
AI & Automation Listed

tufte-graphical-competence

Use when diagnosing why a team, publication, or product keeps shipping weak or dishonest data graphics; when chart production is owned by art, brand, or marketing alone; when a brief claims the audience won't understand, statistics are boring, or 'if you have to explain it, don't use it'; when auditing what share of a report's displays are relational; or when deciding who must review a data display before it ships.

0 Updated 1 months ago
jpoindexter
AI & Automation Listed

tufte-aesthetics-and-technique

Use when refining or judging the look of a finished data graphic — aspect ratio and proportion, line weights, type choices, legend versus direct labels, integrating a graphic with its surrounding text — or when a chart is technically correct but ugly, portrait-shaped by software default, legend-dependent, set in clotted all-caps type, or exiled from the prose it belongs to. Not for data-integrity or chartjunk audits.

0 Updated 1 months ago
jpoindexter