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

Queue Times line chart, dark theme: A dark live-ops console pairing a blue player area with a glowing pink queue line.

Queue Times

DarkLine

A dark live-ops console pairing a blue player area with a glowing pink queue line.

  • Navy#111827
  • Muted blue#3B5B8C
  • Hot pink#FF4DA6
  • Event green#34D399

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 "Queue Times" 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 live-operations console for an online game. Dark navy, soft rounded sans labels, monospaced figures, a calm blue volume panel above a hot pink alert line, and green event ticks tying the two together.

Colors (use these exact values):
- Background: #111827 (dark navy). Gridlines and inactive tab outlines: #243044. Primary text: #E5E9F0. Secondary text: #8B95A7. Faint labels: #5F6B80.
- Volume area: #3B5B8C (muted blue) as a vertical gradient from 95% to 25% opacity, with a 1.5px #7FA3D9 top edge. The active tab fill is #22314D with a #7FA3D9 outline.
- Alert series: #FF4DA6 (bright pink). Event ticks and the live dot: #34D399 (green).

Typography (Google Fonts):
- Nunito Sans: title 800 27px, subtitle 400 15px #8B95A7, panel headings 800 12px uppercase with 1.6px letter-spacing in the panel's series color followed by the unit in 400 12px #5F6B80, tabs 13px (800 active, 600 inactive), footer 12px.
- Azeret Mono (500 to 600) for every number: tick labels 11px #5F6B80, event labels 10.5px green, value callouts 11 to 12px, "LIVE 24H" 11.5px with 1px letter-spacing.

Layout:
- A row of pill tabs (28px tall, 14px radius) across the top left for segments such as regions, the first one active; a green live dot and label top right.
- Title about 50px under the tabs, subtitle under it.
- Two panels stacked on one shared x axis, never a dual y axis: the volume panel on top (about 150px tall) and the alert panel below (about 130px tall), each with its own heading and 3 gridlines. The x labels sit only under the bottom panel.
- Event labels live in the 40px gap between the panels.

Axes and grid:
- Horizontal gridlines 1px #243044, three per panel, labels right-aligned 10px left of the plot in 11px mono ("50k", "60s"). No vertical grid.
- Time labels in HH:MM every 4 hours.

Marks:
- Line chart: the top measure as a smooth (monotone) filled area; the bottom measure as a 2px straight-segment #FF4DA6 line over a 4px blurred copy at 45% opacity for a soft glow. Mark each spike's peak with an r 3.5 ring (background fill, 2px pink stroke) and a 12px pink value label to its left. Mark the top panel's maximum with a small #E5E9F0 dot and a two-line label ("peak 88.5k", "at 20:45").
- Bar chart: the top measure as narrow #3B5B8C columns (1px gap, #7FA3D9 2px cap on each), the bottom measure as pink columns; keep the same event ticks and panel split.
- Events: 1px #34D399 vertical lines at 75% opacity running through both panels, each with a small label chip in the gap (background fill, 3px radius, green outline at 60% opacity, a small green up triangle, then text like "+40 servers 08:15").

Avoid: a right-hand y axis, more than one accent per panel, bright gridlines, drop shadows, and event chips that touch each other.

When you're done, render the chart and check that both panels share exactly the same x positions, event lines line up with the spikes they explain, chips do not overlap, and the title's claim is true for the data.