Guided build · a weekend
Tax & document organizer
Gathers and sorts your documents and does the boring math for you.
No commands. No code. You're about to build this by SAYING what you want — in your own language. The only skill is describing the result well. Here's the whole thing, start to finish.
Gathers and sorts your documents and does the boring math for you.
First, how to actually talk to the agent
- 1Describe the RESULT, not the tech: what's on screen, what each button does, what gets saved. The agent handles the 'how'.
- 2Be concrete about screens and fields — 'a form with amount, category and date' beats 'let me add expenses'.
- 3Ask for the smallest working version first. You grow it by talking afterwards — that's Step 2, not the first message.
- 4Decide what's YOURS, not the agent's: name the categories, colours, rules. Don't make it guess what only you know.
Step 1 — Build it live
Prompting for this kind of tool
- 1For a tax organizer, spell out THREE things: what ONE document row holds (here: name, ticked-or-not, a note, an amount), how rows GROUP (income, deductions, donations) and what gets SUMMED (a total per category plus a grand total).
- 2List the documents YOU actually need yourself — W-2, your 1099s, donation receipts, mortgage interest — and add 'let me add my own rows'. Don't let Claude guess your tax situation; it doesn't know it.
- 3Add 'everything stays on my device, nothing is sent anywhere' — this is your tax data, it must never leave your machine or get bolted onto some account.
- 4Always end with the magic line: 'build the whole thing and tell me exactly how to open it; don't stop to ask questions.'
claude --dangerously-skip-permissions
Open the terminal and run this (if Claude is already running, type /exit first). Then ask it to make a folder for this project and work inside it.
✕ what most people type
you ▸ do my taxes
✓ what actually works — copy it, or better, say it in YOUR words
you ▸ Build me a tax-season document organizer. A checklist of the
documents I need (W-2, 1099s, donation receipts, mortgage
interest, and rows I can add myself) where I tick each one as
collected and attach a note and an amount. The app groups
documents into categories (income, deductions, donations) and
sums the amounts per category plus a grand total. A progress
line shows how many documents I still haven't ticked, and I can
see last year's totals beside this year's. Everything saves on
my device, clean readable look. Build the whole thing and tell
me exactly how to open it; don't stop to ask questions.Say it in YOUR language — Russian, Spanish, anything. Claude understands.
Build it now — tick as you go
0/6Step 2 — It's built. Now make it yours
Don't panic at the techy link. Claude tells you one of two things. Either a file like index.html — find it in your project folder and double-click it; it opens in your browser. Or a web address starting with http://localhost — copy it into your browser's address bar and press Enter. 'localhost' just means 'this is running on your own computer right now'. That's your tool. It's real.
Now tweak it until YOU like it — just talk
This is the part that makes it YOURS. Don't accept the first version — change it by saying what you want, right there in the same chat. Claude rebuilds and you refresh. Keep going until it fits how you actually work. For this tool, try things like:
you ▸ add a row for charitable donations and total them you ▸ remind me which documents I still haven't ticked you ▸ show last year's totals next to this year's
I don't type long messages. I open voice-to-text (the mic in ChatGPT, or your phone keyboard), and just TALK through everything I think about what it built — what's wrong, what I want next — then select-all, copy, and paste the whole brain-dump into Claude Code. Messy spoken thoughts work fine; the agent sorts them out. It's several times faster than writing.
Step 2.5 — Test it like a real thing (it won't be perfect first try)
The truth no one tells beginners: the first build is a DRAFT. The agent makes something, you run it, you find what's off, you tell it — and THAT loop is the actual work. Don't read the code. Use the tool like a stranger would and watch where it lets you down. For this tool, check exactly this:
- 1Open it (Claude gives a localhost link or an index file — see Step 2) and tick off three documents in different groups, each with an amount.
- 2Check the category sums: does 'income' equal the income rows you entered, and does the grand total equal all of them added up? If not, the math is your first fix.
- 3Look at the progress line — does it correctly say how many documents you still HAVEN'T ticked? Untick one and watch the count go up.
- 4Refresh the page (F5 / Cmd-R). Are your ticks, notes and amounts still there? If they vanish, 'saves on my device' isn't wired up — fix that next.
- 5Add one of your own custom rows. It should appear in the right group and roll into that group's total.
Found something wrong? Say it like this
You fix nothing yourself — you DESCRIBE what's wrong in plain words and the agent fixes it. Be specific: what you saw vs. what you expected. Real examples for this tool:
you ▸ 'the grand total doesn't match the category sums — recalculate every total from the ticked rows whenever an amount changes' you ▸ 'when I refresh the page all my ticks and amounts disappear — save everything on my device so it stays' you ▸ 'the progress line counts wrong — it should show how many documents I still haven't ticked, and update the moment I tick one'
Don't stop at v1 — grow it
A tool you built in ten minutes is a starting point, not the finish line. The people who get hooked keep saying 'now also…'. Each line below is one sentence you paste into the same chat to level this tool up:
you ▸ 'let me attach a photo or PDF of each document to its row so everything for tax time lives in one place' — turns a checklist into your actual filing cabinet. you ▸ 'keep a copy of this year when I start next year, so I can see last year's totals beside this year's' — year-over-year is where you spot what changed. you ▸ 'add an estimated-refund line that subtracts my deductions from my income at a tax rate I type in' — rough math now beats a surprise in April. you ▸ 'add a button to export everything as a single CSV I can hand to my accountant' — saves the both of you an hour of re-typing.
Step 3 — Connect it to the world (optional)
Free data & APIs for this one
An API is just how your tool pulls in outside data or sends things out — many are free. You rarely need to research them yourself; the move that works for ANY idea is to ask the agent to find them:
- 1To start you need NO external API — every tax row, sum and total runs locally on your device, which is exactly where tax data belongs.
- 2Country tax rates and brackets change yearly; rather than hard-code them, ask Claude: 'find a free, official source for this year's tax brackets and let me type my rate in for now.'
- 3Reusable move for ANY idea: ask Claude — 'look up free or open APIs that fit a tax-document organizer and tell me which actually need a key.' It will list them; you pick.
About paying for the AI parts
- 1You don't pay for Claude twice. With a Claude subscription you create an API key right in the terminal and use it inside your projects — within your plan.
- 2From June 15 the rule splits: automation through that key gets its own monthly credit — about $20 on Pro, $100 or $200 on Max. Stay under it and it works as before.
- 3Run out and you pay per use (pay-as-you-go); unused credit doesn't roll over. So check your account and see whether the included credit already covers what you're building.
This tool needs no keys to be great — it runs entirely on your computer. Add one only if you later want it to reach out to a service.
Step 4 — Put it online (only if someone else needs it)
Just for you, on your computer? You're already done — skip this step with a clear conscience. Put it online only if someone ELSE should open it, or you want to reach it from your phone away from home.
Step 6 — Stay safe (two easy habits)
- 1Back up anything you'd hate to lose. If the tool holds real data (your budget, health log, client list), ask Claude early: 'add an export/backup button' — one click saves your data to a file. Do it before you ever rebuild from scratch or move the folder.
- 2Don't hand Claude the keys to dangerous rooms. Keep it pointed at this project's own folder. Never connect a learning project to your bank, your crypto, or anything irreversible. Receipts and calendars — yes. Savings — no.
- 3Think before you ask. Claude does what you say in the folder you're in. 'Optimize my photos' optimizes them; it won't delete them — unless you ask for something reckless. Sane requests, clean workspace, and there's simply nothing scary left.
The mistakes that stop most people
- 1Asking for something vague ('make me an app') and getting something vague back. Name the screens, the buttons, what gets saved.
- 2Cramming in ten features at once. Ask for the tiniest working version first — then grow it with follow-up requests.
- 3Stopping at the first error. An error isn't failure — paste it to Claude or describe what you see, and it fixes it. That loop IS the work.
- 4Deciding you need to 'learn programming first'. You don't need to understand the code Claude writes. You need to describe the result.
- 5Forgetting the magic line — 'build the whole thing, don't stop to ask questions' — then wondering why it keeps pausing.
- 6Building for an imaginary audience. Build the version YOU will open tomorrow. Polish never; use immediately.
Normal. Tell Claude what's wrong in plain words ('the button does nothing', 'the page is blank') or paste the red error text. It finds and fixes it. You check. Repeat until it works.
That's it. You built a real tool.
Notice what just happened: no commands, no code — words. This is the entire skill. The people who 'can build things' are just people who describe what they want and let Claude do the typing.