agentleFS
aref-vcaref-vc/tufte-claude-skill/SKILL.md

tufte

Skill297 starsChanged 5 months agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. brunohapp/skills-de-infografico★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jpoindexter/tufte-skills★ 1same 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.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, work through these in order:

    line 19
  2. Very specific:

    Apply kill-list.md: before rendering — strip the things that don't belong in any Tufte-compliant chart.

    line 23
  3. Very specific:

    Check before-after.html: when the user wants to see the difference.

    line 24
  4. Very specific:

    Read report-voice.md: when the output is a report, recap, or slide with prose around the chart.

    line 25
  5. Very specific:

    Run checklist.md: before declaring the chart done.

    line 26
  6. Distinctive:

    When the output is a report, recap, or slide, the text matters as much as the chart.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tufte — visual display, by the book

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).

What this skill produces

Two output stacks, selected by the user's project context:

  1. Self-contained HTML/SVG — single file, inline SVG, no external deps. For one-offs, embeds, screenshots, slide decks.
  2. React (Recharts + D3 fallback) — for projects that already use React. Recharts where the chart type fits; raw D3-in-React where it doesn't (slopegraph, sparkline-in-table, small multiples).

How to use this skill

When invoked, work through these in order:

  1. Read principles.md — 10 rules, one paragraph each. The whole frame.
  2. Use 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.
  3. Apply kill-list.md before rendering — strip the things that don't belong in any Tufte-compliant chart.
  4. Check before-after.html when the user wants to see the difference. Six side-by-side examples covering the cases AI tools default to badly.
  5. Read 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.
  6. Run 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.

Default behavior

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.

Prose around the chart

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.

The kill list, summarized

These are not in any Tufte-compliant chart unless the user explicitly overrides:

  • 3D effects on any 2D quantity
  • Pie charts (use a sorted bar or a small table)
  • Dual-axis charts (use two small multiples instead)
  • Rainbow color scales for ordered data (use sequential single-hue)
  • Heavy gridlines, frame boxes, tick marks at every minor unit
  • Drop shadows, gradient fills, bevels, glow, "ducks"
  • Legends placed away from data (label data directly)
  • Moiré patterns, cross-hatching, dense stippling
  • Redundant data-ink (bar plus number plus axis plus gridline all showing the same quantity)
  • KPI cards with giant numbers and no context

The keep list

These belong in most Tufte charts:

  • Direct labels on data (no legends)
  • Sparklines next to numbers
  • Small multiples for any cross-cut
  • Range frames (axes only span where data exists)
  • Subtle gridlines (white-on-light, or omit)
  • A single accent color (--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.
  • Data marks where they aid reading: dots on line endpoints, dot plots in place of bare bars
  • Sorted categories (rarely alphabetical, almost never as-input)
  • Tables when n ≤ ~20 and exact values matter

File index

FilePurpose
principles.mdTufte's 10 rules with practical interpretation
chart-selection.mdData + goal → chart type decision table
kill-list.mdWhat to remove from any chart
before-after.htmlSix side-by-side comparisons (open in browser)
report-voice.mdProse rules for reports/recaps/slides (no slop, no em-dashes)
checklist.md20-item pre-publish check
cheatsheet.htmlOne-page printable reference
cheatsheet.pdfSame, as PDF
presets/html-svg.mdStyle tokens + a working SVG bar chart, line chart, sparkline, small multiple
presets/react.mdRecharts theme + D3 patterns for slopegraph, sparkline-in-table, small multiples

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.