chart-communication

Design and audit quantitative charts with honest scales, accessible encodings, and decision-focused takeaways.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/coreyone/software-maestro --skill chart-communication-coreyone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chart-communication
Source: https://github.com/coreyone/software-maestro/tree/main/design/experience-and-flows/chart-communication
Command: npx skills add https://github.com/coreyone/software-maestro --skill chart-communication-coreyone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the wrong chart type, truncating axes, or relying on color alone makes quantitative evidence misleading or unreadable. This Skill guides the selection, design, and auditing of data visualizations so charts stay truthful, perceptually accurate, and tied to a specific audience decision. ## Core Features & Use Cases - Chart selection by analytical task: Maps tasks like ranking, change over time, distribution, composition, and uncertainty to appropriate forms such as sorted bars, line charts, histograms, and scatterplots. - Integrity and accessibility auditing: Runs an eight-step audit covering evidence integrity, perceptual accuracy, axis baselines, colorblind-safe palettes, alt text, and keyboard access. - Implementation guidance: Provides technology recommendations for web charts, from static HTML/SVG to SvelteKit with LayerChart or D3, with data validation and fallback tables. - Use Case: Ask it to audit an executive KPI dashboard, and it flags truncated bar baselines, unexplained dual axes, and missing uncertainty intervals, then recommends a redesigned bullet chart with direct labels. ## Quick Start Ask the assistant to recommend and design an accessible chart comparing quarterly revenue across regions, including axis, scale, and alt text choices.

Frequently Asked Questions about chart-communication

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

FAQPage Schema
How do I choose the right chart type for my data?▼

Start from the analytical task, not the data shape. Use sorted horizontal bars for ranking, line charts for change over time, histograms or box plots for distributions, scatterplots for relationships, and stacked bars only for simple composition. Pick the simplest form that makes the intended comparison easiest.

What chart library should I use for a web dashboard?▼

Start with static HTML and SVG for single reports without application state. For maintained dashboards, use SvelteKit with LayerChart as the default chart library, adding D3 only for custom geometry or interactions the library does not provide.

When should a bar chart axis not start at zero?▼

Quantitative bar axes should always start at zero because bar length encodes value. Line charts may use a nonzero range when clearly labeled and analytically justified, since position rather than length carries the meaning.

How do I make data visualizations accessible and colorblind-friendly?▼

Use a colorblind-safe palette and never rely on color alone; supplement with text, symbols, position, or pattern. Provide alt text stating chart type, main pattern, and key values, plus a table fallback for exact values and keyboard-reachable controls.

When is a pie chart a bad choice?▼

Avoid pie charts for trends, precise ranking, or many slices, since angle and area are weak perceptual encodings. Use them only for one whole with few slices and approximate shares; otherwise prefer sorted bars or stacked bars.