It's not just for code

The name trips people up. Claude Code sounds like a thing for programmers, working on programs. So if you don’t write software, it’s easy to assume the whole tool sails right past you.

It doesn’t. Here’s the reframe that unlocks everything:

The thing Claude works on isn’t “code.” It’s a folder of files — and the files can be anything. Photos. Spreadsheets. PDFs. A pile of notes. Your messy Downloads folder.

Code is just one kind of file Claude is good with. But a folder of vacation photos is also just a folder of files. So is a year of bank statement PDFs. Claude can read, sort, rename, summarize, and reshape any of it — the same way it reads and edits code.

The trick, in one sentence

Put a bunch of files in a folder. Open Claude there. Then tell it what you want.

The part people miss is the second half: Claude can also write a small script to do the boring work, and it can build you an HTML page to look at the result in your browser. You don’t write the script. You don’t touch the HTML. You ask in plain English; Claude writes the thing and runs it — pausing for your approval first, exactly like Lesson 2.6 taught you.

That turns Claude into a little tool-builder for your own stuff:

• 300 photos named DSC_0001.jpg, DSC_0002.jpg… → “rename these by the date each was taken.”
• A sales.csv you can’t make sense of → “turn this into a bar chart I can open in my browser.”
• A folder of 40 PDF invoices → “pull the total from each one into a single table.”

None of those are “coding.” They’re just your files, plus a sentence.

Watch it work, start to finish

Say you’ve got a folder full of random downloads and no idea what’s in there. Make one and step inside, the way you did in Lesson 2.8:

cd ~/Downloads
claude

Then ask for something you’d never want to do by hand:

make me an HTML page that lists every file in this folder
with its size and the date it was last changed

Watch the same agent loop you already know — ask → Claude proposes → you approve → Claude does → you verify:

1. Claude figures out it needs to write a small script to read the folder, and shows you what it wants to do.
2. You see a permission prompt (Lesson 2.6 again). You read it, then pick allow once.
3. Claude runs the script and writes a new file — index.html — into the folder.
4. You open that file. Double-click it, or:

open index.html

A real web page opens in your browser: every file, neatly listed, with sizes and dates. You just built a tool. You wrote zero code.

That index.html is yours — it’s a real file sitting in a real folder, no different from the README you edited in Level 2. If the page isn’t quite right, you say so (“sort it by date, newest first”) and Claude redoes it. That’s iterating, which is most of what the rest of this level is about.

What’s next

You’ve seen Claude build something new from your own files. The next move is the one this level is named for: asking Claude to change a file that already exists — and learning to read exactly what it proposes before you say yes.