Quick Reference

Working with Claude Code

How to change the FAR Analyzer — or build something new — without touching code yourself. Just talk to Claude Code.

Part 1

Changing the FAR Analyzer

1
Open the Claude Code app on your computer
It's the desktop app you already have installed.
2
Start a new conversation

Click New chat (top-left corner) — fresh start, no leftovers from yesterday's stuff.

Don't worry about which folder it's pointed at. We'll handle that next.

3
Tell Claude what you want to do

Type or paste this exact message — replace the bracket part with what you actually want changed:

I want to make a change to the FAR Expense Analyzer at github.com/delveunderground/far-expense-analyzer-delve. Please grab the project and set it up so we can work on it. Then I'd like to: [describe the change you want]. When the change is ready, show it to me in a browser before we publish it.

Claude will download the project, set it up, make the change, and open a window so you can see what it looks like.

4
Look at the change in your browser

Claude will give you a link that looks like http://localhost:something — that's a private preview only you can see. Click it (or copy and paste it into Chrome / Edge / Safari).

If the change isn't quite right, tell Claude in plain English what to fix. Examples:

The button's still too dark. Make it lighter green.
Actually, never mind. Undo that last change.

Refresh the preview window after each fix. Repeat until you like it.

5
When you're happy, ship it

Tell Claude:

Looks good. Please publish this change so the live site updates.

Claude takes care of the rest. About a minute later, the live site (far-expense-analyzer-delve-five.vercel.app) shows your change.

You can't break anything

Every version of the project is saved automatically, forever. If a change has a problem — even one you don't notice until next week — you can undo it.

Just open Claude Code and say:

Something's broken on the FAR Analyzer. Please put it back to how it was yesterday.

Within a minute, the live site is restored. There's no version of this where you ruin it permanently.

Bonus

Starting a brand-new project from scratch

If you ever want to build something totally new — not the FAR Analyzer, but a different app — here's the same workflow extended.

A
Tell Claude what you want to build

Open Claude Code, start a new chat, and describe the project. Be as specific as you want — Claude will ask follow-up questions if it needs more.

I want to build a small web app that [describe what it does]. Set it up in a new folder on my computer, build a basic version, and show it to me in a browser when it's ready.
B
Look at it in your browser

Like before, Claude will give you a http://localhost:something link. Click it (or paste it into your browser) to see the app running on your machine.

Tell Claude what to change until you like it. Refresh the browser after each tweak.

C
Put it online (GitHub + Vercel + auto-updates, all in one go)

When you're ready to share your app with the world, tell Claude:

Please save this project to my GitHub as a private repository, deploy it to Vercel, and wire it up so the live site auto-updates whenever I change the code. Give me the live URL when you're done.

Claude does all three things for you — saves the code, puts it on the internet, and connects them so future changes go live automatically. About a minute later you'll get back a web address (something like your-project.vercel.app). Anyone with the link can use the app.

From now on, every time you say "publish this change" the live URL updates within a minute.

D
If the new app needs secret keys or settings

Some apps need things like API keys or passwords. Tell Claude:

What secret keys or settings does this project need? Walk me through adding them to Vercel.

Claude will tell you what's needed and walk you through where to paste each one — same kind of step-by-step you've already done for the FAR Analyzer.

If you ever get stuck

Paste any error message you see into Claude Code and ask "what does this mean?" Most of the time it'll figure it out and walk you through.

Brian can still edit the code as long as he's a collaborator, so if you have a request that's complicated, feel free to reach out to him and describe what you need.