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

Seismogram line chart, light theme: A helicorder drum record of 24 hourly traces with one burst and a red marker.

Seismogram

LightLine

A helicorder drum record of 24 hourly traces with one burst and a red marker.

  • Drum paper#FDFDFB
  • Trace ink#1A1A1A
  • Event red#C0392B
  • Minute rule#D6D6D0
  • Label gray#6B6B66

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 "Seismogram" 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 helicorder drum record pulled off a seismograph at the end of the day. Fine black ink on white paper, one line per time block stacked down the page, and a single red mark where something happened. Scientific, quiet and dense.

Colors (use these exact values):
- Paper: #FDFDFB.
- Trace ink, title and strong labels: #1A1A1A.
- Event red: #C0392B, used for exactly one marker and its label. Nothing else is red.
- Minute rules: #D6D6D0. Secondary labels, subtitle and footer: #6B6B66.

Typography (Google Fonts):
- IBM Plex Sans Condensed: title 600, 25px, #1A1A1A at x 40, baseline 44, stating the finding; subtitle 400, 15px, #6B6B66, baseline 70; header-strip keys 600, 11px uppercase with 1.2px letter-spacing in #6B6B66; secondary annotations 400 italic, 12px.
- IBM Plex Mono: header-strip values 500, 13px; row time labels 11px (every sixth row #1A1A1A, the rest #6B6B66, the event row 600); the event label 600, 11.5px red; the minute axis 11px.

Layout:
- A header strip like a helicorder record at y 86 to 120, x 40 to 920: a 1px #1A1A1A box divided by 0.6px rules into fields such as STA, NET, CHA, GAIN, DATE, FILTER and SCALE, each a small key followed by its mono value.
- The traces run from x 104 to 912, one line per period (an hour for a day of data), stacked from y 160 with a 16.2px pitch. Row labels right aligned at x 90.
- Faint vertical minute rules (0.8px #D6D6D0) every ten units across the whole stack; the minute axis labels ("+0", "+10" ... "60 min") sit 30px below the last trace.
- Footer baseline 588: source at the left in the condensed face, a mono record reference ("Helicorder KRG HHZ XK . 24 h . 60 min/line") right aligned at x 920.

Axes and grid:
- No y axis and no frame. The stacked rows are the axis: each row's baseline is its own zero.
- Each row is broken into short segments with 1.6px gaps at every minute, the way drum recorders mark time.

Marks:
- Line chart: every series is a 0.75px #1A1A1A trace with round joins, sampled densely (about one point per pixel) so noise reads as fine jitter. Quiet rows wobble about 1 to 3px; the event row is drawn last and may swing up to 70px, overlapping four rows above and below, with its peaks flat-clipped at that limit like a saturated pen. If my chart has several series, stack them as rows in this way rather than overlaying colors.
- Bar chart: draw bars as thin 0.75px black outlines filled with dense 0.5px vertical jitter strokes (like a burst of trace), square corners, about 50% band width, on a 1px #1A1A1A baseline; the single highlighted bar gets the red marker instead of a red fill.

Labels and annotation:
- The event marker: a 2px red vertical tick through the event row (18px tall) with a small red downward triangle above it, and the red mono label ("P 14:37:12  ML 4.1  38 km" style) right aligned 10px to its left, sitting between rows with a 4px paper-colored halo (paint-order stroke) so traces never cut through the text.
- Lesser events get a gray italic condensed note with the same halo, never a second red.

Avoid: color-coded rows, thick lines, smoothing, gridlines between rows, drop shadows, and more than one red element.

When you're done, render the chart and check that the rows are evenly spaced, minute breaks are visible up close, the event burst clearly overlaps its neighbors, and the red label is readable over the traces.