visualize-data

To choose the right chart type, match your analytical question to a defensible chart family that addresses trends, comparisons, composition, distributions, or relationships, ensuring the visual tells the correct story.

Visualizing data distributions and uncertainty involves selecting chart families that accurately represent progression and statistical spread, enforcing proper labeling, palette rules, and QA constraints before rendering static or interactive outputs.

Yes, you can create charts for dashboard widgets and HTML exports by adapting the visualization design to specific delivery surfaces, setting structural data contracts, and enforcing quality checks for MCP-rendered or static artifact output.

To QA a scatter plot or ranking chart before sharing, enforce labeling, palette, and layout constraints, validate the chart contract against the analytical question, and verify data structure requirements to prevent misleading visuals.

Yes, this visualization method works with static Python exports by defining chart contracts, palette rules, and quality checks that apply to seaborn outputs, ensuring portable artifacts remain readable and defensible across report surfaces.

You should not use a composition chart for comparing product performance over time when a trend or progression chart family better represents temporal changes, ensuring the visual accurately answers the analytical question without misleading framing.