Data Chart Visualization Design

Problem Being Solved

When a dataset is large enough to matter but the conclusion is narrow, the usual failure is not a missing chart; it is a wrong chart. Too many categories in a pie chart, discrete items plotted as a line, multiple KPIs crammed into gauges, or repeated manual rewrites across ECharts, Chart.js, and Excel. Chart Designer treats visualization design as a set of explicit decisions: infer the data relationship, audience, and display context, then propose chart type, configuration, and styling.

How It Works

Core capabilities include:
- Chart recommendation: match comparison, trend, distribution, part-to-whole, flow, and KPI scenarios to bar, line, histogram, treemap, sankey, gauge, and similar forms.
- Configuration output: produce ECharts JSON, Chart.js setup, Excel chart instructions, and CSS/color-scheme suggestions.
- Design review: apply data-ink ratio, axis labels, units, color limits, colorblind-friendly palettes, tooltips, zoom, and drill-down checks.
The usual workflow starts from a data description: field types, the question to answer, audience, and placement in a report, dashboard, or presentation. It then returns candidate chart types, layout notes, color options, and a config draft that can be pasted into the target tool. This fits teams that need a reviewable visualization spec instead of a vague “make a chart” request.

Boundaries and Caveats

It does not render charts directly and does not access or process data sources automatically. Custom visualizations, real-time data pipelines, and integration into a specific frontend stack still require engineering work. Generated configurations are starting points and may need adjustment for library versions, themes, or business fields. If the goal is a static image, treat the skill as a chart specification workflow rather than a finished renderer.