Guided build · ~15 min
Kid's reading tracker
Logs minutes read, rewards streaks, keeps your little one going.
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.
Logs minutes read, rewards streaks, keeps your little one going.
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
- 1Nail what one entry holds (minutes read today, optionally the book title) and the TWO screens: a big friendly kid home screen and a separate calmer parent view.
- 2Spell out the kid's rewards precisely — 'today's minutes, a flame with the current day-streak, and stars earned at 7 and 30 days in a row'. Vague 'make it motivating' won't build a streak; a flame and named milestones will.
- 3Describe the parent view as its own thing: a calendar of the whole month with minutes per day and a monthly total to beat last month. Say it saves on your device.
- 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 ▸ make my kid read
✓ what actually works — copy it, or better, say it in YOUR words
you ▸ Build me a kids' reading tracker. My child taps in how many
minutes they read today (and optionally the book title), and the
big friendly home screen shows today's minutes, a flame with the
current day-streak, and a row of stars they earn at 7 and 30
days in a row. A separate parent view shows a calendar of the
whole month with minutes per day and the monthly total so we can
try to beat last month. Bright, encouraging look, saves progress
on my device. 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 ▸ let my kid log the book title too and show a shelf of finished books you ▸ add a reward they pick at 10 stars, like extra screen time you ▸ show a monthly total of minutes read so we can beat last month
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 log today's minutes the way your child would — type a number, maybe a book title.
- 2Look at the kid home screen: do today's minutes show big, and does the flame show a streak of 1 after the first day?
- 3Log a few days (or ask Claude how to fake past days for testing): does the streak count up and do the stars appear at 7 days?
- 4Open the parent view: does the calendar fill in minutes per day and does the monthly total add up correctly?
- 5Refresh the page (F5 / Cmd-R). Are today's minutes and the streak still there? If they reset, 'saves on my device' isn't wired up — fix that next.
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 streak resets even though my kid read yesterday — only break the streak when a full day is actually missed' you ▸ 'the rewards aren't exciting enough for a child — make the flame bigger and celebrate loudly when a star is earned' you ▸ 'when I refresh the page the minutes and streak disappear — save progress on my device so they stay'
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 my kid log the book title and show a shelf of finished books they can be proud of' — minutes become a visible, growing collection. you ▸ 'add a reward my kid picks at 10 stars, like extra screen time, and celebrate when they hit it' — the streak now leads somewhere real. you ▸ 'add a second child with their own streak and shelf so siblings each have their own' — one tool for every reader in the house. you ▸ 'show a monthly total next to last month so we can try to beat it' — turns reading into a gentle family game.
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:
- 1No API is needed to start — all the minutes, streaks and stars run locally on your device, which is perfect for a kid's tracker.
- 2Want to confirm a book is real or pull a cover image for the finished-books shelf? The Open Library API is free and needs no key — ask Claude to use it to fetch covers by title.
- 3Reusable move for ANY idea: ask Claude — 'look up free or open APIs about books and reading 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.
More to build