Tool Guide — T40 Associates

Website
Updates
via Claude

A plain-English walkthrough for making changes, updating images, and submitting them for review. No code required.

T40 Associates · 2026

You describe it. Claude does it. Ben reviews it.

You use the Claude desktop app to describe what you want changed on the website. Claude makes the edits directly in the code. You then create a pull request — a bundle of your changes — for Ben to review and approve before anything goes live.

Before You Start

Two Things to Install

Both are free downloads. You only set them up once.

01
GitHub Desktop
Handles code syncing without needing the command line. Sign in with the GitHub account Ben has added to the repo, then clone (download) the website to your computer.
→ desktop.github.com
02
Claude Desktop App
The interface you use to describe changes and let Claude do the work. Requires a Claude Pro subscription. Sign in with your Anthropic account.
→ claude.ai/download

One-Time Setup

Three Steps to Get Started

Do this once. After that, open Claude and start describing changes.

1
Clone the website to your computer
In GitHub Desktop, go to File → Clone Repository. Find the repo in the list (it shows under your account). Choose where to save it on your Mac — e.g. Documents/t40-website. Click Clone. This downloads the full website to your computer.
You only clone once. After that, the folder lives on your Mac and GitHub Desktop keeps it in sync.
2
Install the Claude Desktop App
Download from claude.ai/download and sign in with your Anthropic account. You need a Claude Pro subscription for the code editing features.
3
Connect Claude to the website folder
Open the Claude desktop app. Click the Claude Code tab at the bottom left (looks like a terminal icon). Click Open Folder and navigate to the folder you cloned in step 1. Claude now has full access to the website files.
Claude remembers the folder. You do not need to reconnect it each session.

Day-to-Day Workflow

Making Changes

Just type in plain English. Be specific. Claude finds the file, makes the change, and shows you what it did.

Text and Design
Describe what you want changed. The more specific, the better.
"Change the hero heading on the homepage to say 'We help security firms grow'"
"The CTA button says 'Get in touch' — change it to 'Book a call'"
"The font on the team page feels too heavy — lighten it to 400 weight"
"Update the background colour of the services section to #1A1A2E"
Images and Screenshots
Drag files or screenshots directly into the Claude chat window, then describe where they go.
"This is the new hero image. Replace the existing hero background with this one."
"Add this headshot as Mark’s profile photo in the team section."
"[screenshot] This section looks off on mobile — can you fix it?"
Drag a screenshot into the chat and Claude can see exactly what’s on your screen — then fix it precisely.

Before You Submit

Previewing Locally

Run the site on your own computer before creating a PR. The fastest way to catch anything that looks off.

  • 1
    First time only: install Node.js from nodejs.org — click the LTS version (left button). Run the installer, click the defaults.
  • 2
    Ask Claude: "Start the local dev server so I can preview the site." Claude runs the command for you.
  • 3
    After a few seconds Claude shows a local address. Open it in your browser — that’s your live preview.
  • 4
    The preview updates automatically as Claude edits. No refresh needed.
  • 5
    When done, tell Claude to stop the server. Or just close the app — it stops automatically.
Your local address
localhost:4321
Open this in any browser once the server is running. Updates live as Claude edits — changes appear within a second or two.

Submitting Your Changes

Creating a Pull Request

When you’re happy, ask Claude to bundle the changes. Claude does the rest. You just send the link to Ben.

Ask Claude
"Create a pull request with a clear title and description of everything we just changed."
Claude Packages
Creates a branch, commits the changes with descriptions, and pushes to GitHub.
You Get a Link
Claude gives you the pull request URL — copy it and send it to Ben in Slack or WhatsApp.
Ben Reviews
Ben approves and merges. Your changes go live. If he has notes, he leaves them on the PR.

Worked Example

A Typical Session

Start to finish — from opening Claude to sending Ben the link.

You
Morning. Start the local dev server please.
Claude
(runs the server) Running at http://localhost:4321 — open that in your browser.
You
The homepage headline needs to change to "Security marketing that actually works". I’ve also got a new hero image to drop in.
Claude
(updates the heading) Done — check localhost:4321. Drop the image in and I’ll swap it out.
You
(checks browser — looks good. Drags image file into chat) Here’s the new hero. Use this.
Claude
(saves the image, updates the code) Image saved and referenced. Check the browser — showing now.
You
Perfect. Create a PR.
Claude
Created branch mark/homepage-update-may26. Pull request at github.com/BigMacUK007/[repo]/pull/42 — "Homepage: updated headline and hero image".

Worth Knowing

Tips

Small habits that make the workflow smoother.

"You describe it. Claude does it. Ben reviews it."

T40 Associates — Guide written for Mark Ingleby

← All Resources