The Browser-Tab Ceiling
For six workshops every system you built lived in a browser tab. Open the tab, type the prompt, copy the answer, paste it where the work happens, fix what did not fit. Every round trip was on you.
That tab is the ceiling. A standard you have to paste is a standard you will eventually stop pasting, and the day you stop is the day the system goes stale. CLAUDE.md breaks the ceiling by putting your standards inside the repo, permanently.
CLAUDE.md Is Your Standards, Permanent
CLAUDE.md is one markdown file that lives in your repo. Claude Code reads it automatically, before it does anything. Four blocks is enough to start.
The Copy-Paste Pack
The starter file, the loop that shipped a real app live, and the dial that controls how much you hand over.
The CLAUDE.md Starter Template
[Two lines: what this project is and who it is for. Enough that the agent never has to guess intent.]
## Standards
[The checklist you enforce. The things you check first. The mistakes you see most. The bar a piece of work clears before you sign off. This block IS your judgment.]
1. [the standard you check first]
2. [the mistake you see most often]
3. [what "done right" looks like to you]
4. [keep going. specifics beat vagueness.]
## Conventions
[How you name things, structure work, and style output. This is what makes the work look like yours, not generic.]
- Always work inside the project directory unless explicitly told otherwise.
- [your naming, structure, and style rules]
## Commands
[How to run it, test it, build it. The agent cannot verify its own work if it does not know how to run the tests.]
- Run: [command]
- Test: [command]
- Build: [command]The Source-Rank-Ship Loop
Three prompts, run inside Claude Code. The loop only works inside the repo: the output is a file, the ranking reads it, the spec sits next to it, nothing is pasted.
[your domain, e.g. Excel for small businesses]. Use [your scanner or search tool]. Return raw posts, the top subreddits, and a count.[the raw output file]. These are real complaints. Find the top five worth building for. For each: the pain, who has it, the strongest quote. Rank by how many people feel it times how concrete it is.[the picked app]. Single-file HTML, no backend. Write tests for the logic. Then review your diff against CLAUDE.md and fix anything you would reject.The Three Modes
Pick the mode for the job. Shift the dial with shift-tab inside Claude Code. You can always say "change direction X, Y, Z" no matter which mode you are in.
Keep It Sharp
One file compounds. Every surprise in the output is a missing line you add once.
Every Surprise Is a Missing Line
On stage, Claude Code built the demo app in the wrong folder, because the working directory was never written into CLAUDE.md. One line fixed it forever: always work inside the project directory unless explicitly told otherwise.
Run this loop every time the output surprises you and the file gets sharper every week. Within a month the agent is working in your style, against your standards, without you pasting a thing. That is the shift from asker to builder.
Do One Thing After This
Install Claude Code. Open it in a project you care about. Drop in the starter template from above. Fill the four blocks. Then ask it to build one small thing. Watch it plan, test, and ship. That is how tonight becomes real. Not by thinking about it. By building.
You are not pasting answers any more. You are shipping them.