What is Szum
A chart design system built around purpose-driven chart types, curated themes, and consistent output.
Chart libraries usually solve drawing and leave every design decision to you. Image APIs return pixels without a visual system. Design-tool charts often become screenshots disconnected from production.
Szum adds the missing design-system layer: one shared chart definition, six curated visual systems, and consistent results wherever the chart appears.
One shared chart definition
ChartConfig describes the chart itself: its type, labels, theme, and the roles played by the data. ChartDocument brings that config together with the data and delivery choices needed to validate, render, edit, or save it.
Every Szum workflow works from that same document. Geometry, typography, labels, and color decisions do not have to be rebuilt when the chart moves between tools or outputs.
One chart, wherever it goes
The same chart can become a static graphic for an email or report, an editable Figma asset, or a responsive interactive embed. A saved chart keeps stable public URLs as its document changes, so updates do not require replacing links already used in a product, document, or campaign.
Clarity over configuration
type: "bar" states the chart's job. Field roles describe what the data means in that chart. Themes supply the visual defaults that most callers should never need to specify.
Each chart type includes the labels, reference lines, and annotations that make sense for it. The result is a smaller definition with fewer invalid combinations and more consistent output.
Validated charts
Validation checks more than JSON shape. It verifies field presence and value compatibility, aggregation, scales, labels, color roles, compatibility with older configs, and chart-specific semantics before output.
Errors block rendering and saving. Warnings preserve usable work but require explicit acknowledgement before MCP render and save actions. Suggestions are optional improvements. When a safe fix exists, Szum returns a complete verified replacement document rather than changing the input silently.
When to use Szum
Szum is a good fit when:
- the same visual language must work across code and design;
- an agent or automation needs a small, discoverable chart contract;
- images must look considered without hand-tuning every property;
- a published chart needs stable image and embed URLs;
- a designer needs editable output rather than a flattened screenshot.
If you need arbitrary low-level drawing, a general visualization library is a better fit. Szum trades unlimited composition for a curated set of chart families that work consistently.