Visualization Recommendation
Starting from the insight rather than the chart type ensures the visualization serves the story. Asking for common mistakes prevents the most frequent data viz errors.
I need to visualize {{data_description}} for an audience of {{audience}}. The key insight I want to communicate is: "{{key_insight}}" Data shape: {{num_rows}} rows, {{num_columns}} columns Key variables: {{variables_list}} Tool: {{visualization_tool}} Recommend the top 3 chart types for this data and insight. For each recommendation: 1. Chart type and why it works for this specific data + insight combination 2. Which variables to map to which visual encodings (x-axis, y-axis, color, size) 3. Specific design choices (color palette for {{audience}}, annotations to highlight {{key_insight}}) 4. Code snippet to create it in {{visualization_tool}} 5. One common mistake to avoid with this chart type Rank them by how clearly they communicate {{key_insight}} to a non-technical audience.
Variables to customize
Why this prompt works
Starting from the insight rather than the chart type ensures the visualization serves the story. Asking for common mistakes prevents the most frequent data viz errors.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Providing the full schema and relationships eliminates guesswork. Asking for comments and assumption flags makes the output reviewable and trustworthy before running against production.
Data Cleaning ScriptRequiring before/after logging and a summary report turns a cleaning script into an auditable process. Flagging rows for manual review prevents silent data loss.
Statistical Analysis GuideListing confounders and asking for assumption checks prevents the common mistake of running a test on data that violates its assumptions. The plain-English interpretation ensures you understand the results.
Dashboard Design SpecDefining the key questions the dashboard must answer at a glance prevents scope creep and ensures every widget earns its space. Specifying the audience expertise level calibrates complexity.