Beyond Websites
The map is bigger. Walk it one room at a time.
Everything you learned shipping a website — brief, build, react, publish — transfers to any work that lives in files. Here's the honest map, drawn to be explored slowly, not all at once.
The same loop, different rooms
Claude Code's real product isn't websites; it's finished file-shaped work. A report is files. A cleaned-up spreadsheet is files. A little tool that calculates your rates is files. If the result can live in a folder, the loop you already know applies unchanged. What follows are the rooms I've seen non-coders actually use — each with a first ask you could paste today.
Documents & decks
Polished Word docs, PDFs, and slide decks generated from your notes. "Turn these meeting notes into a two-page client proposal, my letterhead, PDF."
Spreadsheets & data cleanup
The tedium machine: merging exports, fixing formats, deduplicating. "Combine these three CSVs, standardize the phone numbers, flag duplicates."
Research reports
Reading folders of material and writing the summary you actually need. "Read these ten PDFs and give me a brief on what they agree and disagree about."
Personal tools
Tiny apps with an audience of one: a quote calculator, a habit tracker, a dashboard. "Build me a one-page tool that prices a job from hours and materials."
Automations
Recurring chores turned into routines that run on a schedule — reports assembled, files renamed, checks performed. "Every Monday, summarize last week's numbers into one page."
File tidying
The downloads folder of shame, organized: renamed consistently, sorted into folders, duplicates found. "Organize this folder by year and project, and show me the plan before moving anything."
Learning
The patient tutor that never sighs: it can explain any project, tool, or concept against your actual files. "Teach me what a spreadsheet formula is doing, cell by cell."
Creative projects
Interactive pieces, generative art, music practice tools, game experiments — things that need code you'll never write. "Make a page that visualizes my practice log as a garden."
Don't try to use all of it. The people who get overwhelmed are the ones who tour every room in week one. Pick the single room adjacent to work you already do — the report you already write, the folder that already haunts you — and live there until it's boring. Then move.
How to smell a good fit
A task suits Claude Code when most of these are true:
- It's file-shaped. The inputs and outputs can live in a folder.
- It's checkable. You can look at the result and know if it's right — a page renders, totals match, the folder is organized.
- It repeats or it compounds. Either you do it monthly, or the result keeps working for you (a site, a tool, a template).
- It's yours to judge. Quality depends on taste and context you have.
And the poor fits, honestly: one-off questions with no files involved (that's chat's job), high-stakes work you can't verify (legal, medical, tax — get a professional), and anything where being wrong is expensive and invisible. The tool is powerful; the judgment stays with you.