▌ Guided build · an evening

Bank-statement breakdown

Drop in a statement; see exactly where the money actually goes.

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.

ℹWhat you'll have at the end

Drop in a statement; see exactly where the money actually goes.

Start Claude

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.

The wrong ask vs. the right ask

✕ what most people type
you ▸ analyze my bank account

✓ what actually works — copy it, or better, say it in YOUR words
you ▸ Build a statement analyzer: I paste rows copied from my bank
      statement (date, description, amount), it groups spending into
      categories with rules I can edit, and shows totals and a pie
      chart. Everything stays on my device — nothing is sent anywhere.
      Build it all, tell me how to open it, don't ask questions.

✦✦

Say it in YOUR language — Russian, Spanish, anything. Claude understands.

Build it now — tick as you go

0/6

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.

!If something breaks

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.

checkpoint

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.

← All ideas Build another one →