This takes about twenty minutes. You need the app running, as in the Quickstart. Your own data helps, but a CSV or Excel export of one table is enough: give it to Claude first (“Here is orders.csv. Put it in the CSV folder.”). Connect your own data has the details, and the database route.

Pick one table and one question#

Start small: one table, one question. For example, a CSV export of your orders and the question “How many orders do we get each week, and for how much?”

If you are not sure what the columns are called, ask Claude to look first:

“Look at orders.csv and tell me which columns could give a weekly order count and amount.”

Ask for it#

Say four things: the question, the table, the figures, and the period.

“Make a report called Orders from orders.csv. Show the number of orders and their total amount per week, with tiles for the totals and a line chart over time. Follow the date filter.”

What you see#

After a minute or two, Claude answers in plain words: it made the Orders report, checked it, and opened it in your browser at http://localhost:9923/reports/orders. The page has tiles with the totals, a line chart of orders per week, and the date filter at the top. The report is also in the Reports list from now on. Here is its chart:

Claude wrote two files for it. You never need to read them; they are under What Claude wrote at the end of this page.

Look and steer#

Check one figure against a number you trust. Then ask for changes in plain words:

• “Show the amount in thousands.”
• “Start the chart at the beginning of the year.”
• “Add a table of the last twelve weeks under the chart.”

If something looks wrong, say what you expected:

“Last week shows 40 orders, but our shop had about 400. Check the SQL.”

Claude reads the SQL (the query behind the figure), explains the difference, and either fixes it or writes the rule into the report’s dialog, the one the (i) button at the top opens, where readers see how a figure is counted.

Make it yours#

Each of these is one request. Try them on the same report.

Every chart, table and switch is a component, one building block of a report page. They are all listed in All components.

Save it#

When it looks right, ask:

“Save this version: the Orders report with the category table.”

A saved version is a snapshot of all your app’s files at one moment. Claude keeps them with git, the free program you installed in the Quickstart, which records every change; you never use it yourself. You can ask “What changed since yesterday?” or “Put the Orders report back as it was this morning”, and nothing is lost. Your passwords in app/.env are never part of a saved version.

-- Orders and amount per week
select strftime('%Y-W%W', ordered_on) as week,
       count(*) as orders, sum(amount) as amount
from orders
where ordered_on between date($from) and date($to)
group by 1
order by 1

import { defineReport, query } from "~/components/report-kit/define"

import weekly from "./weekly.sql?raw"

type Week = { week: string; orders: number; amount: number }

export default defineReport({
  meta: { title: "Orders", description: "Orders and amount per week.", connector: "csv" },
  queries: { weekly: query<Week>(weekly, { grain: "week" }) },
  components: (k) => [
    <k.Line key="orders" series="weekly" x="week" xFormat="week" y={{ orders: "Orders" }} title="Orders per week" />,
  ],
})

Next#

Connect your own data: give Claude your files, keep a weekly export fresh, or connect your company’s database.

Then, when you want to know more: Modules (the app’s sidebar entries), Report files (what a report holds), All components (every chart, table and input) and FAQ.