AI · Updated November 11, 2026
Every named thing in the system, in plain words, with when it first appeared. Sorted by date, so reading down the list is reading the system being built.
His first system: a method for building a good prompt for any job, kept as its own document.
The steps he used to build a prompt: define the role, gather context in batches, state the task, set the format, test, refine, then move it into a Project.
A workspace in Claude with its own standing instructions and files. Marketing is one. Thinking Better is another.
The standing document Claude reads at the start of every chat in the Marketing project. It says how the work is done. Called the seed prompt until v1.66.
The box in the Project where the instructions live. Claude can't write to it, so every new version was copied in by hand.
Each change to the instructions gets a number, v1 through v1.78 so far. The first 28 are separate files in Drive. After that it is one document edited in place.
A document of how he talks and writes, with every line he picked or rejected logged in it, so Claude writes from his voice and not a generic one.
The Drive folder of his own letters, emails and course notes. It is the authority on his voice. Other people's material informs structure only.
A Drive folder made to hold a picture of how the process works at each version. The first attempt at this log.
After a correction, Claude states what went wrong mechanically and moves on. No "you're right," no apology.
The numbered list of things a stranger has to believe, in order, to get from where they are to yes. Copy is built on it.
No em dashes in any copy, ever. Checked as its own step.
A document edited in place with its history kept, in place of a new numbered file for each version.
A fixed group of named direct-response marketers (Kennedy, Halbert, Brunson and others). Claude writes as each one in turn, so he gets several different takes on one line. A seat is one of them.
The same people talking to each other about an idea, as a conversation, where the council only writes lines.
When a saved copy and the live page differ, the live one is the truth.
His word that a piece is finished. A locked line is never reworded, only placed.
One thing being made from start to finish: a page, an offer, a deck. Each has its own log.
One file per build. Every decision goes in the moment he makes it, so a later chat can read what was settled.
A short line of checks run under every slide before he sees it: numbers traced, nothing overlapping, nothing changed that wasn't asked for.
A number he gives is used as given. Claude does not audit it or ask him to prove it.
A holding area for new rules. Each has a date, a reason, what to watch for and when to decide.
A trial rule: suggest a picture or a comparison wherever an idea stays abstract. Still on trial.
A new thing we set out to do. The gate runs once per objective, not once per message.
Before any new job starts, Claude lists what it is assuming (who it's for, what it sells, when, where, how much) and he marks each right or wrong.
Chet Holmes's idea: pick the hundred best-fit buyers and go after them again and again, in place of approaching everyone.
A separate copy of Claude started to do one job on its own and report back. Seats, fresh readers and simulated readers all run this way.
The first brainstorm on a new job. Every seat runs as its own agent and thinks alone first, then the room talks.
Reading a piece for the mental shortcuts it uses on the reader, and the ones it could. Still on trial.
The intake flow that came out of the first Deep Room: an AI-made report that shows a business owner how strangers see them, with some findings held back.
Two settings chosen before writing: how aware the reader is of the problem and the product, and how many times they have heard this kind of claim. From Eugene Schwartz.
The instructions reorganized by when a rule applies: when a job opens, before a line is written, before anything is shown, after a correction, at the end of the session.
The document that says how he decides whether a line of copy is good.
The known format a piece lives in: sales letter, video sales letter, Invisible Funnel, story email. Named first, because it sets the order.
One line under every piece of copy that names what was read to write it and which settled decisions it touches.
The five things done before he sees any first draft: 1 read his own work in the same format, 2 read the original source of every story and pull its real details, 3 make every section finish its thought, 4 have two fresh readers go through it, 5 name what was read.
When he talks through copy, he is giving the idea, not the words. Claude writes it fresh. His words stand only when he says word for word, exactly, or lock it.
An agent that did not watch the piece being written, reading it as the stranger it is for.
A story doesn't stop at the fact. It goes on to the owner's new life, hands the same picture to the reader, then asks.
A short document written at the end of a session so the next chat can pick up the work.
Ray's rules, pulled from his two books into one working document and read on every copy job.
His own list emails from 2008 to 2015, word for word, mined for stories, subject lines and patterns.
A made-up crowd of realistic people, 12 or 100 of them, who each read the copy cold and decide. It predicts; it does not prove.
Fix what changes the audience's experience. Leave alone the arithmetic nobody in the room is doing.
Before a big rework, Claude says out loud that it is about to write new copy, shows his version beside the new one, and waits.
Don't remind him to check with, or get sign-off from, the people in his stories. He handles that. In project memory; not found in the current instructions.
Rules being followed early in a long chat quietly stop being followed later in the same chat.
A visible action Claude takes, like opening a document. It shows on screen, so it either happened or it didn't.
A one-screen document, per job, of the rules in force right now. Claude reads it as a tool call before every batch of work.
The instructions split into three: the instructions, the Doctrine and the Changelog.
The craft rules by format: emails, lead capture pages, offers, closes, slides. Read only when writing that kind of piece.
The history of every version and why each rule exists. It governs nothing.
The reading done the moment a copy job is confirmed: the standard, Ray's rulebook, and the Doctrine sections for that format.
A mark put on a decision in the log when it should become a standing rule, so it gets carried into the instructions at the end of the session.
A packaged set of instructions Claude loads only when a job needs it, so it isn't carried in the main instructions.
conversion-sim (would they act), price-sim (which price), skeptic-study (why the ones who said no said no), copywriter-contest (other writers take a run at a working version).
Make him stronger. His words are the floor: never softened without asking.
A list under the copy of his strongest phrases, each marked kept, sharpened or cut.
A reader restates a line in their own words. If it comes back blank, wrong or vague, the line failed.
In a simulation, everything outside the copy is set to perfect (the date works, the drive is short), so the result measures the words.
The rules always run, on every job, whether he names them or not.
All the rules that apply to a piece, turned into one list a fresh reader scores it against. 39 points on the home page.
Purpose over process. Every delivery opens with "Would I sign this?"
Three questions asked of every line: what does it mean to the reader, why do they care, does it follow the line before?
The order a page gets made in: purpose first, write to it, the line test, the verdict, his pass, Ray on top, emphasis last, simulation only to compare versions.
After his pass, the copy goes through Ray's rulebook for words and moves, without touching his emphasis or adding facts.
Bold and highlights go on at the very end, only on results and payoffs, a handful per page.
A private GitHub repository that holds every version of the instructions, skills and core documents in one place.
One skill per copywriter (Halbert, Kennedy, Brunson and others) holding that person's method, loaded when their seat writes.
His long spoken runs about slides or copy, saved word for word to a file before anything else is done with them.
A shared document where a lesson from one project is logged so the other projects can use it. Seen once it is an observation. Seen in a second project it is a pattern.