The Daily Workflow

The core loop every single job follows — open, point at a client, prompt, preview, push, and hand it to Tom to go live. Learn this once and every task works the same way.

👋 New to all this? Never heard of GitHub, "commit" or "deploy"? Read the 2-minute plain-English explainer in SOP 01 first — it explains every word below. Read it →

Quick reference · the words used on this page

Jargon decoder

You never type any of these — Claude does them all when you ask in plain English. This is just so the words make sense as you read.

SessionOne chat with Claude. One task = one session.

ProjectThe Team Vault — the shared folder of client work, opened in Claude.

CommitSave a snapshot — a dated save-point you can always return to.

BranchYour private working copy, so the live version is never at risk.

PushSend your work up to GitHub so it's saved and visible.

PreviewA private test link to check your change before the public sees it.

Pull Request"Please check my work" — sends it to Tom to review. (a.k.a. "PR".)

MergeTom approves and it becomes the real version.

Deploy / LivePublished to the real website the public sees — automatic on Tom's approval.

Every task follows the same path

Open → point at a client → prompt → preview → push → sign-off

The three things to always get right: the right project, the right client folder, and a fresh session per task.

Open the right project. Go to claude.ai/code → make sure the project is attain-digital-team-vault. That's the only place client work lives.

Start a fresh session for a new task. One task = one chat. Don't stack an email job on top of a landing-page job in the same conversation — start a new session so Claude stays focused and the record stays clean.

Tell Claude which client — by name. Start with "Work in clients/wiltshire-energy/." Claude opens that box and reads the client's CLIENT.md automatically — their brand, tone, do's and don'ts — so it builds it their way, not generically.

Prompt it clearly. Say what you want, for whom, in what format. (SOP 03 covers how to prompt well.) Claude edits the real files. Read back what it changed before moving on.

Preview before anyone sees it. For a page or site, Claude pushes your work to your own branch, which builds a private preview link (via Vercel). Open it, check it on desktop and phone. This is your "see it live first" — the public site is untouched.

Save it properly. When you're happy, Claude commits your work and opens a Pull Request — a tidy "ready for review" package with your name on it. Your work sits on your branch; the live version is never at risk.

Tom signs off → it goes live. The Pull Request lands with Tom. He reviews, then merges — and that merge is what publishes it. Anything a client will see goes live on his sign-off, not yours.

Mark it. Type attain-complete when a task is done, or attain-review when it needs Tom's eyes. That's the whole reporting system — two phrases. (More in SOP 03.)

Preview vs live — the difference

Two versions of every site

🔗 Preview (private)

Your branch builds a preview link only you and Tom see. Edit, refresh, check on mobile — as many times as you like. The public never sees it. Always test here first.

🌍 Live (public)

The real client site. Only updates when Tom merges your Pull Request. You never push straight to live — the sign-off is the gate.