Not Just Websites: Claude Code on Your Everyday Files

Somewhere on your computer there's a folder you avoid opening. Forty PDFs, a dozen spreadsheets, meeting notes going back months. Sorting it out is the job you keep promising yourself you'll do on a quiet Friday afternoon — and somehow the Friday never comes.

Keep that folder in mind. This whole lesson is about it.

Any folder you point it at

Everything you've built in this course so far happened inside one tidy project folder — the one we created together, on purpose, for the recipe site. It would be easy to walk away thinking that's what Claude Code is: a website-building thing.

Here's the frame worth breaking: Claude Code works on any folder you point it at — and on the files already inside. Your documents. Your downloads. That zip a colleague sent over labelled "everything — please sort." Open Claude Code there, and the rule from lesson three applies exactly as before: the folder becomes Claude's world for the session, a window and a fence. It can see what's inside, and the permission dial still governs every change.

How it does the work — one honest line

For documents and notes there's no trick to explain: Claude reads them and writes them, the same way it read and wrote your recipe pages. The interesting part is the heavier jobs — crunching a spreadsheet, drawing a chart. For those, Claude writes a small script — a little program — behind the scenes and runs it. You'll see it happen in the conversation; you never have to touch it, read it, or understand it.

And that's genuinely good news. A language model guessing at arithmetic across five hundred rows would be a worry. A script doesn't guess — it computes, the same way every time, on every row. When Claude tells you the top five products by revenue, that number came out of a calculation.

Expand

One aside before the fun part. Anthropic also publishes ready-made file skills — prebuilt versions of the lesson-six idea — that teach Claude to produce especially polished Word, Excel, PowerPoint, and PDF files. If Claude ever suggests adding one before a document job, that's all it means: a one-time yes, and it handles the rest.

So what can it do with your files?

Grouped by the kinds of files you actually have. Every line below is a complete prompt — a sentence you could paste in today, word for word.

Notes and text files

• "Read all my meeting notes from this month and give me one summary of decisions and open items."
• "Merge these three drafts into one clean version and flag anything contradictory."
• "Turn these rough notes into a tidy one-page brief, as a Word doc."

Word documents

• "Read this report and give me the five key points."
• "Update the proposal: replace every mention of the old product name with the new one — carefully, not blindly."
• "Combine these two documents into one, keep the formatting consistent, and add a table of contents."

That middle one is subtler than it looks. Claude reads before it replaces, so it can tell your product's name from the same word used in an ordinary sentence — something blind find-and-replace gets wrong constantly.

Spreadsheets and data

• "Read this sales spreadsheet and tell me the top five products by revenue this quarter."
• "Clean this CSV: fix the date formats, remove the duplicates, and save the result as a new file."
• "Make charts from this data — revenue by region as a bar chart, by month as a line — saved as images I can drop into a slide."
• "Build me a simple budget tracker with working formulas."

PDFs

• "Summarize this sixty-page PDF — just what matters for my decision."
• "Extract the tables from these PDF invoices into one spreadsheet."
• "Fill in this PDF form using the details from my notes file."

The one hard case: PDFs that are photographs of paper. If it was scanned, expect a rougher ride.

Whole folders — including the messy ones

• "Make an inventory of everything in this folder — what's here, what's duplicated, what looks old."
• "Sort it into subfolders by type and year, and rename the photos to the date they were taken."
• "Turn the data in this folder into a short report, Word or PDF, charts included — something I could send to my manager."
• "Convert these Word docs to PDF, and this spreadsheet to CSV."

Real files deserve a little care

Up to now you've been working on practice files. These are your actual documents — so borrow the habits people who do this daily swear by. Four of them, all calm:

1. Keep the dial on Plan or Ask. You saw every mode in lesson four; with real files, stay where you approve each change before it lands.
2. Originals stay untouched. Ask for results as new files — cleaned-sales.xlsx sitting next to sales.xlsx, never overwriting it.
3. Big reorganisations: plan first. Ask Claude to show you the plan, read it, then let it proceed.
4. Review before you keep. Claude Code snapshots your files automatically before every change — you don't set anything up. So the habit is the glance: look at what changed, and if you don't like it, press Esc twice and the files snap back.

From chore to habit

You came into this lesson with a website-building tool. You're leaving with a general assistant for anything file-shaped — reading it, tidying it, updating it, charting it, reporting on it. And if one of those file jobs repeats every week? You already know what that is: a skill waiting to be written, exactly like lesson six.

Files were step one, though. At work, a lot of what matters doesn't live in files at all — it lives in systems: the board where your tickets live, your sales dashboard, the place your product's records sit. Next lesson, the same plain-English leverage goes live — on connected systems, through the connectors you met last time.