ai-charts-bot is a website for an AI charts bot. It gives visitors a place to turn a plain-language request into a chart, and a place to look at charts the bot has produced.
The product intent is narrow and deliberate: a visitor arrives, describes what they want charted, the bot generates the chart, and the visitor can view it. There is no enterprise BI suite here, no account wall, no spreadsheet grid. The audience is analysts, founders, students, and data-curious visitors who want to type a prompt and watch a chart appear.
The experience is built around a single idea — data made flesh. The chart field is the page. The bot's own output is the background, the demo, and the gallery.
ai-charts-bot is a first-party web application with three destinations:
Two accepted human personas use the product: the Chart Creator, who describes what they want charted, reviews the generated chart, and adjusts it until the result is usable; and the Chart Viewer, who opens the site to look at charts the bot has produced rather than to create one.
The bot itself is a system actor. It receives a chart request, produces a chart, and returns it to the requesting surface. It is not a persona and has no page of its own.
Delivery. ai-charts-bot is delivered as a custom first-party web application. All three destinations are application-owned custom pages. There is no provider-owned surface, no external destination, and no headless-only delivery in the current scope.
Access. All three destinations are reachable without an account. The Landing page is the anonymous public entry. Create Chart and Charts are likewise reachable anonymously — a visitor can submit a chart request and view charts produced by the bot without establishing an identity. No sign-in, sign-up, invitation, or provisioning flow is part of the current product.
Current vs. future. Everything described in this document is current. No future-horizon requirements were accepted in the authoritative thread; the future section is therefore empty and no page, control, or state exists to serve it.
Exclusions. The product is a website for an AI charts bot and nothing more. It does not include account management, billing, team collaboration, permissions or role-based visibility, data-source connectors, scheduled or automated chart generation, or any adjacent BI capability. These are not prohibited by name in the source; they are simply not accepted requirements, and no page or control is created for them.
Revenue by region, last 6 quarters…. It is the entry affordance into Create Chart; submitting from here hands the visitor to the Create Chart workspace with their request.FR-1 — Website for an AI charts bot (explicit) As a visitor, I should be able to reach a website for an AI charts bot so that I have a place to create and view charts produced by the bot.
FR-2 — Create charts with the AI charts bot (explicit) As a Chart Creator, I should be able to create a chart with the AI charts bot so that I get a chart from what I described.
FR-3 — View charts produced by the bot (explicit) As a Chart Viewer, I should be able to view charts produced by the bot so that I can see the chart content I came for.
FR-4 — Anonymous entry and routing from Landing (required_inference) As a visitor, I should be able to understand what the bot does and reach either creating or viewing from the Landing page so that I can start the thing I came to do.
FR-5 — Submit a chart request from the Landing prompt bar (required_inference) As a Chart Creator, I should be able to type my chart request into the prompt bar on the Landing page so that I can start creating without first navigating.
FR-6 — Supply data for the chart (required_inference) As a Chart Creator, I should be able to supply the data my chart should be built from so that the bot charts my numbers rather than guessing them.
FR-7 — Review the generated chart and adjust (required_inference) As a Chart Creator, I should be able to review the chart the bot returns and adjust my request so that I end up with a chart that is usable.
FR-8 — Open a chart from the gallery (required_inference) As a Chart Viewer, I should be able to open a chart from the grid so that I can see it at full size.
FR-9 — Read a chart's caption (required_inference) As a Chart Viewer, I should be able to read what produced a chart so that I understand the chart I am looking at.
FR-10 — Live model state (required_inference) As a visitor, I should be able to see whether the bot is idle, generating, or in error so that I know what the product is doing.
Product context. The Chart Creator arrives at ai-charts-bot with something in mind that they want to see as a chart — a set of numbers, a comparison, a trend. They are not looking for a BI tool; they are looking for the shortest path from a sentence to a legible visual. They may arrive from the Landing page's prompt bar or navigate straight into the Create Chart workspace.
Primary goal. To end up with a chart they can view and keep, produced from what they described.
Distinct accepted responsibilities. The Chart Creator is the only persona who submits a chart request to the bot. They describe what they want charted, supply the data the chart should be built from, submit the request, and review what comes back. They are also the only persona who adjusts and resubmits — the loop of refining a request until the output is usable belongs to them alone.
Relevant inputs and decisions. They decide what to ask for and what data to supply. They decide whether the returned chart is usable or needs another pass. They decide whether to keep the chart or move on.
Interactions with other accepted participants. The Chart Creator interacts with the bot, which receives their request and returns a chart. They do not interact with the Chart Viewer; the two personas use the product independently. A chart the Chart Creator produces becomes available in the Charts destination, where the Chart Viewer may later open it.
Observable success. A chart renders in the chart pane from their request, with its readouts visible, and they can open it in the Charts destination.
Product context. The Chart Viewer opens ai-charts-bot to look at charts the bot has produced, not to make one. They come to the Charts destination and treat it as a wall to browse — reading captions, opening plates, moving on.
Primary goal. To see the chart content they came for.
Distinct accepted responsibilities. The Chart Viewer is the only persona who browses and opens existing charts. They read the grid, open a plate to see a chart at full size, and read its caption to understand what produced it. They never submit a request to the bot.
Relevant inputs and decisions. They decide which chart to open and how long to look. They read the caption — prompt, model version, date — to interpret what they are seeing.
Interactions with other accepted participants. The Chart Viewer interacts with the bot only indirectly, by viewing charts it has already produced. They do not interact with the Chart Creator. If the grid is empty, their route out is into Create Chart, which is the Chart Creator's workspace.
Observable success. A chart opens at full size with its caption legible, and they can return to the grid and open another.
Revenue by region, last 6 quarters… — and submits.The visual direction is Data made flesh: generative light as the charting engine after Refik Anadol. The muse is Refik Anadol, whose language is data rendered as a living, luminous surface — which is exactly what an AI charts bot does. The emotional register is discovery and quiet awe: the moment raw numbers turn into something legible and beautiful. Not enterprise BI greyness, not playful SaaS, not a dashboard template.
Mode. Dark mode only. There is no light mode.
Palette.
| Role | Hex | Use |
|---|---|---|
| Background | #07080C | Near-black ink. Carries ~75% of every screen. |
| Surface | #111319 | Panels, floating readouts. |
| Hairline | #262A33 | 1px strokes on panels and plates. |
| Text | #F2F1EC | Warm off-white, never pure white, so luminous chart fields read brighter than the page. |
| Primary | #E8FF4D | Acid chartreuse. The data/action colour: prompt cursor, active series, primary CTA, focus rings. Under 8% of pixels. |
| Accent | #FF5C2E | Ember orange. The single hot signal for the generating state, errors, and the second data series. |
| Muted | #8A8D96 | Metadata, axis labels, timestamps. |
Charts draw from a 6-stop luminous ramp derived from primary → accent → #7CE7FF cyan → #B79BFF violet, always on dark grounds so contrast stays above 4.5:1 at body size.
Typography. Headings and body both use Instrument Sans. Headings at 600–700 with tight -0.03em tracking, sentence case for headlines — never all-caps at large sizes. Optical sizing is pushed big: hero headline 96–140px, section heads 48–64px. Uppercase micro-labels in 11px / 0.18em tracking are reserved for axis, HUD, and metadata only. Numerals are always tabular. Data readouts pair Instrument Sans with tabular figures and 0.02em tracking at 13/11px.
Type scale. 1.333 modular on a 4px baseline: 140 / 104 / 78 / 58 / 44 / 32 / 24 / 18 / 16 / 13 / 11.
Shape language. Full-bleed rectangular canvas with hard edges — no rounded cards. Overlay panels are thin-bordered rectangles (0–2px radius, 1px #262A33 stroke, 72% opaque #111319) that float over the generative field like HUD readouts. Section boundaries are soft vertical light-washes rather than lines. Data marks are crisp: 1.5px strokes, square caps, no drop shadows.
Layout. The chart field is the page. A fixed left rail (64px) holds the wordmark, page index, and a live model-state dot. Content sits in an asymmetric 12-column grid with the generative canvas bleeding behind columns 3–12. Landing scrolls as a sequence of full-viewport scenes: headline over field → prompt console → example chart gallery as a horizontal filmstrip → CTA. Create Chart is a two-pane workspace: left 5 columns = prompt + data input + parameters, right 7 columns = live chart on the dark field with a floating readout panel. Charts is a museum wall: a sparse grid of chart plates on near-black with generous gutters, each captioned like an artwork label.
**Im

Prompt console — chart request
No account needed. Your request carries into the workspace.
Every plate below was produced from a single typed prompt — no spreadsheet, no chart editor. Each caption records the prompt, the model version and the date the chart was rendered.
Revenue by region, last 6 quarters
Weekly cohort retention, 12 weeks
p95 latency by service, trailing 30 days
Generation mix by source, 2025
Landing / Close
Describe the chart you want, or browse what the bot has already made.

Prompt console — chart request
No account needed. Your request carries into the workspace.
Every plate below was produced from a single typed prompt — no spreadsheet, no chart editor. Each caption records the prompt, the model version and the date the chart was rendered.
Revenue by region, last 6 quarters
Weekly cohort retention, 12 weeks
p95 latency by service, trailing 30 days
Generation mix by source, 2025
Landing / Close
Describe the chart you want, or browse what the bot has already made.
No comments yet. Be the first!