Frame Check

A CSV report builder app idea: a weekly report builder for messy CSV exports. One week build with Python, DuckDB, Flask and Claude API, for small team leads who live in spreadsheet exports.

See the spec
Why now

Why now

DuckDB is up 61% and polars up 61% on PyPI, so fast local analysis of large files is now easy. Builders are also tired of reading huge piles of generated text, so a short change summary is more useful than a long one. From the signals of the week of 26 Oct 2026.

The spec

The spec

Drop in the same CSV export each week and get a short written summary with charts and what changed since last time. It replaces the manual copy and paste into slides.

Build time

One weekAPIs or integrations · Level 3 of 5

Audience

Small team leads who live in spreadsheet exports.

Stack

  • Python
  • DuckDB
  • Flask
  • Claude API

Fun factor

Watching a dull export become a readable report feels like getting an hour back.

Core features

  • CSV upload with column type detection
  • Week over week change table
  • Auto charts for top movers
  • Saved report templates

AI features

  • Writes a five line summary of the biggest changes with the numbers cited
  • Flags rows and columns that look broken, such as sudden nulls or duplicates

Stretch goals

  • Schedule reports by email
  • Connect to Google Sheets
  • Add alert thresholds per metric

First version

Upload two CSVs from consecutive weeks and see a diff table, three charts and a short written summary.

Build plan

Build plan

4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.

Load and profile filesUse DuckDB to read CSVs and detect types and key columns.
Start here
Compute the diffJoin the two weeks and rank the biggest changes.
Chart the moversRender the top changes as simple bar charts.
Add the summarySend the diff to the model and show the text above the charts.
The build prompt

The build prompt

Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.

frame-check.prompt.md
# Build Frame Check

You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end.

## The idea

**Frame Check.** Drop in the same CSV export each week and get a short written summary with charts and what changed since last time. It replaces the manual copy and paste into slides.

**Why now:** DuckDB is up 61% and polars up 61% on PyPI, so fast local analysis of large files is now easy. Builders are also tired of reading huge piles of generated text, so a short change summary is more useful than a long one.

**Who it is for:** Small team leads who live in spreadsheet exports

**What makes it fun:** Watching a dull export become a readable report feels like getting an hour back.

## Scope

- **Build time:** One week. Size every decision to ship a working first version inside this window.
- **Technical ambition:** Level 3 of 5, "APIs or integrations". The product leans on third-party APIs. Wrap each integration in its own module, handle its failures and rate limits, and cache what is safe to cache.
- **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them.

## Core features (each must work end to end in the first version)

1. CSV upload with column type detection
2. Week over week change table
3. Auto charts for top movers
4. Saved report templates

## AI features

- Writes a five line summary of the biggest changes with the numbers cited
- Flags rows and columns that look broken, such as sudden nulls or duplicates

How to build them:
- Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI.
- Read API keys from environment variables only, and document each one in `.env.example`.
- Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them.
- Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds.
- Never let a feature depend on the model being perfect. Show the result, let the user edit or retry.

## Stretch goals (later, not in the first version)

- Schedule reports by email
- Connect to Google Sheets
- Add alert thresholds per metric

Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask.

## Tech stack

Use exactly: Python, DuckDB, Flask, Claude.

Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change.

## Owner's notes

Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict.

The first version should be exactly this, and no bigger: Upload two CSVs from consecutive weeks and see a diff table, three charts and a short written summary.

## Build plan (with saved progress)

0 of 4 steps complete. Resume at step 1: Load and profile files. Before you start it, check what is already implemented so you do not repeat finished work.

1. **Load and profile files** [not started]
   Use DuckDB to read CSVs and detect types and key columns.

2. **Compute the diff** [not started]
   Join the two weeks and rank the biggest changes.

3. **Chart the movers** [not started]
   Render the top changes as simple bar charts.

4. **Add the summary** [not started]
   Send the diff to the model and show the text above the charts.

## Definition of done for the first version

- [ ] CSV upload with column type detection works end to end, with real data, not a placeholder.
- [ ] Week over week change table works end to end, with real data, not a placeholder.
- [ ] Auto charts for top movers works end to end, with real data, not a placeholder.
- [ ] Saved report templates works end to end, with real data, not a placeholder.
- [ ] Every screen handles loading, empty, and error states.
- [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand.
- [ ] A README explains setup, environment variables, and how to run it locally.

## Quality bar

- Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast.
- Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next.
- Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`.
- Type-safe end to end. No `any` without a comment explaining why.
- Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note.
- Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose.

## How to work

1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision.
2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it.
3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub.
4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early.
5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why.
6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass.
7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion.
8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not.

If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step.

Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.

How to use

  1. Copy the prompt above.
  2. Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
  3. Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.

Want ideas built around you instead? Generate four from your own interests, time, and stack.

Frequently asked questions

FAQ

Frequently asked questions

Answers on what Frame Check is, how to build it, and where example ideas come from.

Similar ideas

Similar to Frame Check

More data & analytics ideas, then a few from other categories.

Generate your own

Ready to generate yours?

Four ideas per round, shaped by your interests, skill level, and how much time you have.