Procedure · 1 September 2026
Written 1 September 2026, for Ken and Beth. Ken asked for this on 31 August: "I need to learn how to operate the machine effectively where I don't F anything up." He also said, twice, to write it in plain words. So this is written in plain words. Corrected the same day after Dil sent the real account details.
You are already good at the hard part. Ken, 31 August: "I'm very good at prompting. What I need is, how do I get my prompt into that machine?" So this does not teach you how to write an instruction. It shows you where to put it.
| You want to | Do this |
|---|---|
| Start work | Go to claude.ai/code. Start a new chat. Never open an old one. |
| Check you are in the right place | Your name at the bottom, and your own repo name near the top. |
| Type your instruction | The box at the bottom of the screen. That is the only box. |
| Make the others see your work | End with: "Push it to main when you're done." |
| Be asked to run a command | You should not be. Say: "You run it." |
| Undo something | Say: "Undo that and push it to main." |
| Get stuck | Start a new chat and say it again. |
Everything below is the same seven lines, with the reasons.
Three people. Three separate Claude accounts. We do not share logins. Two different sets of files. One server that none of you ever touches.
| Signs in to Claude as | Works on | Server | |
|---|---|---|---|
| Ken | ken@outcropinspector.com · Max | Outcrop-Q — Josh, the phone, the booking system | Rose Hosting |
| Dil | dil@thesavvyinspector.com · Max | Outcrop-Q — the same files as Ken | The same Rose Hosting |
| Beth | ken@homeinspectorhelp.com · Max | Home Inspector Help — the services files | The same Rose Hosting |
⚠️ Beth's login starts with the word "ken". That is correct. It is not Ken's.
It is an old company address, and it is Beth's Claude account. The email at the top of the menu is not the person. Look at the name at the bottom of the screen instead: it says Beth. Ken's account is
ken@outcropinspector.com, on a different company.This is worth ten seconds of your time because these two are one word apart and they open two different sets of files.
Nobody shares a login, and nobody should start. Each account has its own allowance for the month. Two people on one login share one allowance, and it runs out halfway through the first busy day. That is why Dil moved off Ken's account in the first place.
Ken and Beth work on different things, on purpose. Ken's chats are about Josh, the phone lines and the bookings. Beth's are about the services side. You are not treading on each other, and you cannot see each other's chats — nobody can see anybody else's.
Go to claude.ai/code and sign in as yourself.
Start a new chat every time. There is a list of old chats down the side. Some are weeks old. Do not open them.
Here is why that matters more than it sounds. An old chat still holds everything it was told back then. A lot of that is now wrong. In an old chat, Hanif still works here. Josh does not exist. Ken is still called Austin. There are prices on the website that we pulled months ago. Claude is not broken when it says those things. It is reading an old note, and reading it correctly.
A new chat reads today's files. So: one new chat for each job.
Check two small labels before you type.
| Label | Should say |
|---|---|
| Your name, bottom left | Ken, or Beth — whichever you are |
| The repo name, near the top | Ken: Outcrop-Q. Beth: the Home Inspector Help one. |
⚠️ Anything starting zz-RETIRED is a dead copy. Close it and start again. There are two of them. They are kept only because they hold old history, and they are frozen.
That one-second look is what stopped the mess on 21 August. Claude gave Ken old answers about Hanif and Josh, and nothing was wrong with it. It was reading a dead copy of the business that had almost the same name.
Then type in the box at the bottom. That is it. There is one box. Everything you say goes in it. You do not need any other window, ever.
You already write good instructions. Two things to add, and both are about the paper trail, not the wording.
Say where the answer should live. Claude will happily write you a brilliant answer that lives only in the chat, and a chat is not a filing cabinet. So finish with something like:
Write it up, save it in the Owner's Inbox, and push it to main.
"Push it to main" is the sentence that matters most in this whole document. It is what makes your work exist outside your screen.
Here is the picture. You each have your own desk. Nobody can see anybody else's chat, and nobody ever will. But Ken and Dil work out of one filing cabinet, and pushing to main is the act of putting the folder in that cabinet. Until that happens, your work is on your desk only, and Dil's Claude cannot see it no matter how good it is.
⚠️ Beth's cabinet is a different one. Her work goes to the Home Inspector Help files. So if Beth finds something Ken or Dil need, pushing it to main is not enough on its own — it lands in her cabinet, not theirs. Tell them. A message is the only thing that crosses between the two sides.
Nobody gets a bell. Even inside one cabinet, the other person's Claude only reads your work when it next goes looking. So send a text saying it is there. The cabinet moves the work. A message moves the attention.
One job per chat. Two jobs in one chat get tangled, and neither gets finished well.
This should not happen any more. If it does, the answer is one line:
You run it.
Copy that. It is a complete instruction. Claude has its own copy of everything and can run its own commands in it.
We changed the settings on 1 September so it stops asking. The list of what it may do without asking lives inside the files themselves, in .claude/settings.json. Because it lives there, it reaches every account by itself. There is nothing to install on anybody's laptop.
This is the answer to Beth's ask — 31 August: "I do not want them accessing GitHub and RoseHosting because they are the boss." Agreed, and here is the good news: neither of you ever needs to.
| Job | Who does it now |
|---|---|
| Save a file, write a report | Claude, on its own |
| Run the tests | Claude, on its own |
| Put work in the cabinet (GitHub) | Claude, on its own |
| Update the live website and dashboard | Nobody. It happens by itself when Claude pushes to main. |
| Log in to Rose Hosting | Nobody. Not ever. |
That last line is not a rule we are hoping people follow. It is how the thing is built. Pushing to main sets off a job that updates the live server on its own. There is no step in the middle where a person types anything.
There are exactly two, and both are about the phone, so they are Ken's side, not Beth's.
Both used to need a person on the server. They do not any more. There is a page of fixed buttons for them, and Claude can press the buttons for you. You will never see GitHub; you will just see a question in the chat.
Claude will ask you first, on purpose. Pressing that button restarts the phone service, and that service is answering Chad's and Ted's real lines. If somebody is mid-call, the call drops. So the question is worth asking. Answer it when nobody is in the middle of a test call.
If Claude seems muddled, going in circles, or answering a question you did not ask: start a new chat and say it again. That is the whole fix. Do not reset, restart, clear or reinstall anything else. There is nothing else to reset.
This is the job Ken could not do while Dil was away, so it gets the most room.
Patty's notes from GC were 36 calls of handwritten comments. They found real faults that nothing else found. Seven times she wrote some version of "he never asked for my email." That one line, repeated, is what proved the problem was in our tool and not in Josh's script — and it got fixed the next day.
Step 1. Get the notes however they come. Email, a Word file, a photo of a page, a text message. It does not matter.
Step 2. Start a new chat.
Step 3. Paste the whole lot in. Do not tidy it up.
This is the step people get wrong, so it is worth a sentence of its own. Do not summarise them. Do not fix the spelling. Do not pick out the important ones. The value is in the exact words. "He said $545 for a 2,300 square foot home" tells us where the bug is. "He got the price wrong" tells us almost nothing. And it is the boring repeats that find the real faults — you only notice a thing was said seven times if all seven are still there.
If it is too long for one message, send it in two. That is fine.
Step 4. Say who, what and when. Claude cannot guess these and will have to ask:
Step 5. Ask for the four things. Here is a paragraph you can copy word for word and change the details:
These are test call notes from Patty at GC Home Inspection, from calls to 704-520-8683 between the 1st and the 3rd of September. Please do four things. One, save the notes word for word as the source file in the Owner's Inbox, with nothing edited. Two, count what repeats and how many times. Three, split the faults into Josh getting it wrong, and Josh reading his card correctly where the card itself is wrong — those second ones are Chad's to rule on, not ours to fix. Four, check each fault against the code before you report it, in case we already fixed it. Then push it all to main and add a line to the decisions log.
Step 6. Answer its questions. It will have some. That is the job working, not failing. If it says it cannot see some of the calls, tell it what it is missing or say to go ahead without them.
Step 7. Text Dil that it is there.
A written transcript is not a recording. The robot that tests Josh listens to him and types what it thinks it heard. So a line that looks wrong on the page has two possible causes, and they look exactly the same: Josh really said it badly, or Josh was perfect and the robot misheard. This has cost us a day, twice. If a transcript looks wrong, listen to ten seconds of the real call first. Business Center, then Calls, then Listen.
Not every fault is Josh's. Three of Patty's 36 were Josh reading his card correctly, and the card was wrong. Chad's own price list said one thing and his written instructions said another. Fixing Josh there would have made him wrong. Always ask for that split.
Short list. Everything on it is something you genuinely never need.
| Do not | Because |
|---|---|
| Open a black command window | You have no reason to. Claude runs its own. |
| Log in to Rose Hosting | The live site updates itself. Nobody logs in. |
| Open an old chat | It will tell you things that stopped being true in July. |
Work in a repo whose name starts zz-RETIRED | Those are dead copies kept only for their history. |
| Copy a file onto the server by hand | The next update wipes it. This has happened twice. |
Delete a file ending in .md | Ask first. They are the written record. |
Claude will ask you before it sends anything to a customer, publishes anything, or spends money. When it does, look for these three. They are the ones that have gone wrong before.
[PRICING TBC].Start here: you almost certainly cannot lose anything. Every version of every file is kept, forever, going back to the start. "Undo" is a normal thing to ask for, not an emergency.
| What happened | What to say |
|---|---|
| It changed something and you want it back | Undo your last change. |
| It changed a file yesterday and you noticed today | Put this file back the way it was before yesterday's change. |
| The wrong thing is now live | Undo it and push to main. |
| You are not sure what it even changed | Show me everything you changed today, in plain English. |
Live things take a minute or two to go back. That is normal.
One exception, and it is the phone. If a phone change went wrong, say so plainly: "Put the phone brain back and redeploy it." The phone does not update itself, so undoing it needs that extra sentence.
Never try to fix it by hand. Do not copy files about. Say what you want in the chat and let it do the work. Hand-fixing is how we lose an afternoon.
For anything big, ask for it to be kept off to one side first:
Do this on a new branch, not on main. Show me before it goes live.
Nothing on a branch is live. Nothing on a branch can break anything. You look at it, and then you say push it to main, or you say scrap it. For small things — a report, a note, an answer — just go straight to main. That is what it is for.
Ken, ask for this:
Run put-it-back and tell me what it says.
It checks whether anything was switched off for a test and never switched back on. That is a real thing that has happened twice, and neither time did anything complain. It only reports. It changes nothing.
Ken is out on Friday 4 September. If something breaks and nobody can fix it:
Dil, you offered: "i can open the terminal if you want to setup something for Beth and Ken so they will not access the terminal or github when im not around." Here is the whole list. Most of it is done.
| Three separate Claude accounts | Ken, Beth and you. All on Max. Confirmed from the screenshots. |
| Ken's access to Outcrop-Q | Working. His sessions already run against it. |
| The list of commands Claude may run without asking, on Outcrop-Q | Done 1 September, in .claude/settings.json. It ships with the files, so it reaches Ken's account and yours by itself. |
| The dead copies of the repo | Renamed zz-RETIRED- and locked in August. |
⚠️ Beth's repo is not under the ClaudeAustin2026 account. I checked: that account holds three repos — Outcrop-Q and the two retired ones. Nothing for Home Inspector Help. So I cannot reach Beth's files from here. Somebody with access to her side has to do it.
Without it, Beth gets asked to approve commands one at a time, which is the exact thing she asked not to happen.
✅ AND IT IS NOT A TERMINAL JOB. Dil, 2026-09-01: "i can access beth's Claude Code."
That is the easy way and it is the one to use. Open Beth's Claude Code, in her own repo, and ask it to write the file itself. No terminal, no copying files between folders, nothing to install.
Dil has the exact words to paste. They tell it to look at her repo first and match the settings to how her project actually runs its checks — which is the one thing that has to be right, and the one thing a straight copy would get wrong.
The pattern to copy is resources/claude-code-settings-template.json in this repo. It goes into Beth's repo as .claude/settings.json, and it has to reach main there, the same as anything else.
⚠️ Beth must start a NEW chat afterwards. Settings are read when a chat begins, so the chat that wrote the file is still running under the old rules. A new one picks them up.
That is a five-minute job and there is no terminal work on this list at all.
Read the decisions log and tell me, in plain English, the five most important things that changed in the last two weeks. Save it in the Owner's Inbox and push it to main.
Then check it worked: the file is there, and you can see it. If that works, the batch of call reviews will work, because it is the same seven steps.
There is no software to install, no key to copy, no server to log in to, and no settings screen to fill in. Nobody needs a second Claude account — all three already have their own.
Anything here that does not make sense, put it to Claude in a new chat and ask it to explain that bit again. That is a fair use of it, and no question is a daft one.