data-visualization

Enforce accurate encoding, accessibility, and responsive behavior in UI charts.

Updated May 6, 2026
One-click install
npx skills add https://github.com/shipiit/shipit-ui-design --skill data-visualization-shipiit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-visualization
Source: https://github.com/shipiit/shipit-ui-design/tree/main/skills/data-visualization
Command: npx skills add https://github.com/shipiit/shipit-ui-design --skill data-visualization-shipiit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents dashboards from turning data into misleading visuals by enforcing correct chart selection, encoding hierarchy, axis honesty, and accessibility-ready chart semantics.

Core Features & Use Cases

  • Pick the right chart for the question to ensure the visualization matches the intended decision (e.g., time trends, distributions, part-to-whole).
  • Encoding and color rules that don’t lie by prioritizing position/length over color, limiting categorical colors, and using sequential/diverging ramps correctly.
  • Axis honesty and annotation rigor including zero baselines for bars, appropriate log scaling, and contextual reference lines and callouts.
  • Accessible chart output with required alt-text and a “View as table” pattern for screen-reader and keyboard users.
  • Responsive and interactive behavior covering sizing density, tooltip behavior on hover/focus, keyboard reachability, and motion that respects prefers-reduced-motion.

Quick Start

Use the data-visualization skill to generate or refine an accessible chart for a dashboard that answers this question: “How does revenue change over time by region?”.

Frequently Asked Questions about data-visualization

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

FAQPage Schema
How do I make accessible charts in React that work with screen readers?

Accessible charts require alt-text and a "View as table" pattern for screen-reader and keyboard users. You enforce these semantics alongside correct axis encoding and responsive behavior to ensure dashboards are usable by everyone.

How do I choose the right chart type for my dashboard data?

Choosing the right chart type means matching the visualization to the intended decision question, such as using time trends for changes over time or distributions for frequency. This prevents dashboards from turning data into misleading visuals.

Does this approach work with recharts, visx, tremor, and echarts?

Yes, this approach works with recharts, visx, tremor, echarts, and chart.js. It applies when generating or refining charts and dashboard elements in codebases using these libraries to enforce correct encoding and accessibility rules.

What are the rules for color encoding in data visualization?

Color encoding rules prioritize position and length over color, limit categorical colors, and use sequential or diverging ramps correctly. This ensures your visualizations do not lie and accurately represent the underlying data hierarchy.

How do I handle chart animation and prefers-reduced-motion constraints?

Chart animation must respect prefers-reduced-motion constraints. This involves enforcing motion restrictions and responsive interactive behavior, including tooltip behavior on hover and focus, to support users with motion sensitivity.

Why do my bar charts misrepresent the data distribution?

Bar charts misrepresent data when axis honesty rules are ignored, such as omitting zero baselines for bars. You enforce zero baselines, appropriate log scaling, and contextual reference lines to ensure accurate visual representation.