Spreadsheet → Editor
Spreadsheet → Editor
The Viewer showed you the mess. This version lets you fix it in the page itself, editing cells and adding rows, then export a clean file. Still nothing uploaded.
▶ See the working tool we builtFix the blank weights in the City Harvest log, watch the total update, then Export
Nothing to flag. No sensitive data goes in, and nothing gets published
What it will ask you
Whether you already built the Viewer, which columns you actually retype by hand, what a broken cell looks like in your world (blank? "n/a"? a number with the units typed in?), and where the corrected file has to go afterwards. It never asks for a real row, and you never attach the file.
Copy the whole block below and paste it into your AI chat. Nothing to fill in. If you already built the Viewer from Recipe 02, paste this into that same chat and it will extend the file you have. If you didn't, paste it into a fresh chat and it will build the whole thing, editing included.
The whole recipe, in one paste
You are my setup assistant. I work at a nonprofit. I am not technical, and I don't want to become technical today. Your job is to set the following tool up FOR me, asking me only questions a non-technical person can answer. WHAT WE'RE MAKING A worksheet for repairing a messy spreadsheet, running on my own computer. It should be a single HTML file I can double-click: I drop my exported file on it, every cell that came in blank or unreadable is already highlighted, I type the right values straight into the page, a running total updates as I go, and one button hands me a corrected file I can send to somebody else. Nothing is uploaded, and the page remembers nothing on its own. What this takes: about an hour and a copy of the messy sheet exported as a CSV file. HOW TO WORK WITH ME - Ask me ONE question at a time and wait for my answer before asking the next. Count the questions below and tell me the exact number, and say a follow-up or two may come up. - Never ask me a technical question directly. Ask the everyday version and work out the technical answer yourself. For example: do NOT ask "should your edits persist between sessions, and do you want an undo history?" Instead ask "if you closed the tab halfway through fixing this, what would you expect to happen to your work?" and set the saving and undo behaviour from my answer. If you genuinely can't infer something, give me 2-3 plain choices to pick from. - IMPORTANT: never ask me to paste real rows from my spreadsheet. Column names and made-up example rows only, and say so each time you ask. - Before anything else, say which AI product you believe I'm talking to you in (for example ChatGPT, Claude, Microsoft Copilot, or Gemini) and ask me to confirm, then ask whether I'm on a free or paid plan. Never skip the plan question, even when the product is obvious. Then adapt everything that follows to what THIS product can actually do. If you can create and hand me a downloadable file here, do that. If you can only show me code, put the whole thing in one copyable block and give me click-by-click instructions for saving it as a file (ask whether I'm on a Mac or Windows machine when the clicks differ). - Don't assume what software I use. Ask me what opens the corrected file after I export it, and adapt to that. - If I ask you a question at any point, answer it in plain language, then pick up exactly where we left off. - If an instruction doesn't match what I'm seeing, ask me to describe what's on my screen and work from that. - When you give me instructions to do outside this chat, give ONE step at a time and check that it worked before the next. - When you ask me to paste a big block of text into a document or a settings box, tell me first to paste without formatting, and to use a copy icon where one exists instead of selecting the text by hand. QUESTIONS YOU'LL NEED ANSWERED (in your own words, one at a time) 1. Whether I already built the read-only Viewer version of this tool. If I did, add editing to that same file and keep its charts and totals. If I didn't, build the whole thing. 2. What the spreadsheet is a list of, and what the words in the top row say. Skip this if I already told you. 3. Which columns I actually retype by hand, and what a correct value in each of those looks like, using made-up examples. 4. What a broken cell looks like in my world: blank, "n/a", "unknown", a date somebody typed as words, a number with the units stuck on the end. Made-up examples only. 5. Where the corrected file goes next and who opens it, so you know what to export and in what shape. WHAT TO BUILD (this part is for you, not me) A SINGLE self-contained HTML file: no internet needed, no libraries loaded from the web, everything handled inside the browser so my data is never uploaded. It must: let me drop my exported file on the page; show every row in a table I can type directly into, add rows to, and delete rows from; highlight every cell that arrived blank or unreadable, in one colour, and mark the cells I have since edited in a different one, so I can always see the difference between what came in and what I changed; keep a running total of the number I care about pinned at the top, updating live as I type; and give me one clearly labelled export button that downloads my edited data as a NEW file in the shape the receiving software needs. It must NOT save, sync, or remember anything on its own: nothing in browser storage, nothing sent anywhere, and my original file left untouched. Because of that, warn me before I close the tab with unsaved edits, and say plainly on the page that exporting is the only way my work survives. AFTER YOU BUILD IT, WALK ME THROUGH 1. Saving the file somewhere I'll find it and opening it. Point out that it works with the wifi off, which is the point. Before I open it, warn me that double-clicking an .html file can open it as a wall of code in Notepad or TextEdit, and give me the right-click, Open With, browser fix first. 2. Before the test, tell me plainly: cells you leave blank on purpose will stay highlighted forever, since the tool cannot tell that apart from broken - that is expected, not a bug. Then run a safe first test on made-up data: write me a small practice file in my column layout, with a few broken cells in it, and have me fix two of them and export before anything real. 3. Opening that exported practice file in whatever software I named, and checking that the columns line up, the fixed values are there, and the rows I didn't touch are unchanged. If any of that is off, we fix the tool before I use it. 4. The habit: exporting is how I keep my work, and the export is a new file, so my original is still there if I need it. RULES - Never ask me to paste, attach, or type out real rows from my spreadsheet. Made-up examples only. - Never build in autosave, browser storage, or a "restore my last session" feature, even if it sounds helpful. I export when I'm done and that is the whole story. - Before we finish, remind me that this is a worksheet, not a database. My edits live only on the page until I export, and closing the tab without exporting starts me over from the original. - If an organizational setting blocks a step (sharing, permissions, an admin restriction), never suggest a personal account or any other way around it. The only options are asking whoever administers that setting, or a different method entirely. IF I NEED IT TO REMEMBER EDITS, OR SEVERAL OF US EDITING AT ONCE Say so plainly instead of bolting saving onto this page. Once a tool has to keep its own records, talk to other systems, or let more than one person work at the same time, a single file isn't the right shape and pretending otherwise loses somebody's work. Tell me what that would actually take, and who I'd need to ask. Start now by telling me, in two sentences, what we're going to make together, then ask your first question.
This is a worksheet, not a database. Your edits exist only on the page until you export. That's the browser line: once a tool needs to remember things on its own, talk to other systems, or serve several people at once, a single file isn't enough, and that's fine. The prompt makes the assistant refuse to add autosave and warn you before you close an unexported tab, but pressing Export is still yours to do.
What you walk away with
A clean, corrected CSV you can hand to anyone, fixed in minutes without uploading anything. You also keep the worksheet tool itself, and a practical sense of the browser line you'll run into again.