Chart Prompts

1,337 ways to dress a line or bar chart, 669 light and 668 dark. Open any chart to see it full size and copy a prompt that gives your own chart the same look.

Every chart uses illustrative data. The prompts work with any coding agent and any charting library; they describe colors, type, spacing and marks precisely enough to reproduce each look.

← More from Emergent Mind Labs

String Output bar chart, light theme: Field report bars in solar blue with orange fault-tagged underperformers.

String Output

LightBar

Field report bars in solar blue with orange fault-tagged underperformers.

  • Solar blue#1D4E89
  • Safety orange#E8742A
  • Ink#1B2533
  • Rule gray#E4E7EC

Prompt for your coding agent

Paste it with your chart's code. It restyles your data to match this chart.

Restyle my chart in the "String Output" style described below. Keep my data, chart type, title meaning and units; change only the presentation. Use the charting library this project already uses (plain SVG if there is none). If the library can't express a detail, draw it in a custom layer instead of dropping it. Measurements assume a 960 x 600 chart; scale them proportionally.

Mood: a field technician's diagnostic report printed on white. Crisp, condensed and practical: one solar blue for everything normal, one safety orange for everything that needs a truck roll.

Colors (use these exact values):
- Page: #FFFFFF.
- Normal marks: #1D4E89 (solar blue).
- Exceptions, fault tags, header rule and the fault key heading: #E8742A (safety orange).
- Ink: #1B2533. Secondary text: #667085. Gridlines and footer rule: #E4E7EC.

Typography (Google Fonts):
- Barlow for the title (600, 28px, #1B2533, sentence case, with the computed count of exceptions) and for subtitle (15px #667085), legend (13px) and source (12px).
- Barlow Condensed for all IDs and technical labels: report header 13px 600 uppercase with 1.6px letter-spacing (right half 500 in #667085 with 1.2px letter-spacing), category IDs 13px 500 (700 orange for exceptions), y labels 14px 500 with units ("8 A"), group labels 13px 600 uppercase with 1.4px letter-spacing in #667085, fault tags 14px 700 white with 0.6px letter-spacing, tag values 14px 600 orange.

Layout:
- 56px side margins. A report header row at y 38 (breadcrumb on the left, reading conditions on the right), then a 2px #E8742A rule across the full content width at y 48. Title baseline about y 94, subtitle about 27px below, legend row at y 158.
- Plot from about x 92 to x 904, top at y 200, baseline at y 470. Bars are grouped (e.g. six strings per inverter block) with a 30px gap between groups; under each group a thin #667085 bracket (1px, 5px end ticks) and a centered group label.
- A footer rule at y 548 and a fault key at y 572: "FAULT CODES" in orange 700 condensed, then each code in 700 ink followed by its meaning in 500 #667085; source right-aligned.

Axes and grid:
- Y axis from zero, 1px #E4E7EC gridlines every 2 units, labels right-aligned with units. A 1.2px #1B2533 baseline.
- The expected value as a full-width 1.4px #1B2533 dashed line (5 on, 3 off).

Marks:
- Bar chart: square-cornered bars 20px wide on a ~30px pitch, solid #1D4E89; any bar below the tolerance threshold (here 90% of expected) turns solid #E8742A. Exceptions get a tag in a lane above the plot (top about y 200): a 50 x 20 orange rounded rectangle (radius 3) with the white fault code, the value in orange 24px below it, and a 1px orange dashed (2 on, 2 off) leader down to the bar top.
- Line chart: a 2px #1D4E89 line with 4px #1D4E89 square markers; points below the threshold get orange 6px square markers and the same tag-and-leader treatment; the expected value is the same dashed ink line.

Avoid: rounded bars, gradients, shadows, more than one accent color, rotated labels, and value labels on every bar (only exceptions are labeled).

When you're done, render the chart and check that the count in the title matches the orange bars, tags never overlap each other or the bars, IDs are legible at thumbnail size and the orange header rule spans the same width as the footer rule.