data-viz

Enforce Tufte-inspired design principles for accessible web data visualizations.

3|3|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KyaniteLabs/tastecheck --skill data-viz-kyanitelabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-viz
Source: https://github.com/KyaniteLabs/tastecheck/tree/main/skills/data-viz
Command: npx skills add https://github.com/KyaniteLabs/tastecheck --skill data-viz-kyanitelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This skill prevents the creation of misleading, cluttered, or inaccessible data visualizations by enforcing Tufte-inspired design principles and web-native accessibility standards.

Core Features & Use Cases

  • Honest Encoding: Ensures charts accurately represent data through zero-baseline bars, 1-D length/position mapping, and lie-factor verification.
  • Accessibility Parity: Guarantees every visualization includes a text-based takeaway and a screen-reader-friendly data table.
  • Use Case: When building a dashboard, use this skill to replace a default, misleading 3D pie chart with a responsive, contrast-safe range-frame line chart that clearly communicates quarterly revenue trends.

Quick Start

Use the data-viz skill to generate a range-frame line chart and accessible table for the provided quarterly revenue dataset.

Frequently Asked Questions about data-viz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is lie-factor minimization in data visualization and why does it matter?▼

Lie-factor minimization in data visualization ensures graphical representations accurately reflect quantitative changes without distortion. It enforces honest encoding through techniques like zero-baseline bars and 1-D length mapping, preventing charts from visually exaggerating or misrepresenting the underlying data.

How do I make web charts accessible for screen readers?▼

Making web charts accessible for screen readers requires pairing every visualization with a text-based takeaway and a screen-reader-friendly data table. This approach ensures accessibility parity by providing structured, navigable data alternatives to visual graphical encoding.

How do I apply Tufte design principles to a responsive dashboard chart?▼

Applying Tufte design principles to a responsive dashboard chart involves maximizing data-ink ratio and enforcing graphical excellence. The process generates honest, responsive visualizations using design-system token integration, replacing cluttered defaults with clear, quantitative length mappings.

Does this approach work for converting misleading 3D pie charts into honest visualizations?▼

Yes, this approach works for converting misleading 3D pie charts into honest visualizations by replacing them with contrast-safe, responsive alternatives like range-frame line charts. It enforces strict requirements for zero-baseline encoding and 1-D position mapping.

When should I not use standard charting libraries for quantitative data display?▼

You should not use standard charting libraries for quantitative data display when strict graphical excellence and accessibility parity are required. Default libraries often produce cluttered output lacking zero-baseline enforcement, lie-factor verification, and screen-reader-compatible data tables.