Starter versions of the files my agents read first.
Three starter files to copy into your own project tonight. A rules file every agent reads first, one skill file for one job, and a list of the lines a check should stop before anything ships. Each one is filled in as an example, so you edit it instead of starting from a blank page.
If you use Claude Code or another AI agent for real work and want it to follow your rules. These files give it your rules, your way of doing one job, and a check before anything ships.
3 files
A rules file, a skill file and the check. Copy them, then fill in the blanks in square brackets.
6 lines
Kinds of line the check stops: a result with no evidence, a made-up client, a promise you can't keep, and three more.
What’s inside
- A rules file with Read first, Never and Always sections. The Never section is filled in for you to edit.
- A skill file for one job, writing a post caption: when to use it, the inputs, the steps and a checklist at the end.
- Six kinds of line a check should stop, each with an example and why, and a check prompt to run on any draft.
- Where to save each file in Claude Code, and where it goes in any other AI tool.
Where to save each file
Download the three files below. From the rules file and the skill file, copy only the part between COPY FROM HERE and COPY TO HERE. The check file is saved whole.
Claude Code: the rules file
- Save the part you copied from rules-file.txt as in your project's top folder, the root. Claude Code reads it at the start of every session.
- To check it loaded, type in a session and look for CLAUDE.md under Memory files.
Claude Code: the skill file
- Make a folder for the job inside . For the example job, that's .
- Save the part you copied from skill-file.txt in it as . Keep the line as the very first line, or Claude Code won't read the name and description.
- Type in a session to run it. For each new job, copy the folder and change the name, the description and the steps.
Claude Code: the check
- Save all of check-lines.txt in the top folder, next to CLAUDE.md. The rules file already tells the agent to read it before every job.
- In the check prompt at the end of it, replace the blank in item 5 with your approved prices, or write .
Any other AI tool
- Paste the rules file into the place for standing instructions. Tools call it the system prompt, custom instructions or project instructions.
- Paste the skill file at the start of the chat for that job, or add it under the rules.
- Some coding tools read a file called at the project root instead. Check your tool's own help page for the file name it reads.
The Never section, filled in for you to edit
These six lines are in rules-file.txt. Keep the ones that fit your project and change the rest.
Never invent a client or a result
No client, result, quote or testimonial unless it's on file. If one is needed, the agent writes and tells you.
Never edit the source files
The originals stay as they came in. The agent copies what it needs into a new file.
Never put a key in the code
Keys, tokens and passwords live in one file that is never shared or uploaded, such as .
Never publish without approval
Nothing is posted, sent or deployed without your approval in writing. The agent drafts it and hands it to you.
Never quote an unapproved price
Prices come only from your facts file. Anything else is a guess.
Never delete what it didn't make
The agent deletes only files it created in that job.
The lines a check should stop
All six are in check-lines.txt, with when to let a line through. Every example is made up on purpose. None of them is a claim.
A result with no evidence
- Example, made up on purpose
- Why it stops
- A result needs proof you can show, such as a report, a dated export or a screenshot.
A made-up client
- Example, made up on purpose
- Why it stops
- Unless that client is real, on file and agreed to be described, it's invented.
A promise you can't keep
- Example, made up on purpose
- Why it stops
- Nobody controls what customers do. Promise only your own work.
A number with no source
- Example, made up on purpose
- Why it stops
- It can't be checked, and readers repeat it.
A price that isn't approved
- Example, made up on purpose
- Why it stops
- A price or discount is a promise to every reader. Only approved prices go out.
A key or a password
- Example, made up on purpose
- Why it stops
- Anyone who reads it can use it. If one ever leaks, cancel it and make a new one.
Run the check before anything ships
A rules file is read, not enforced. Claude Code's own guide says it treats CLAUDE.md as context, not as settings it must obey. So the check runs as its own step, and then you read it.
The agent checks its own work
- The Always section tells it to run the check in check-lines.txt and tell you what it found. Read that before you read the draft.
Run it again, fresh
- Open a new chat. Paste the check prompt from the end of check-lines.txt, with the draft where it says. It lists every line that should stop, with the reason and a fix.
- In Claude Code you can type: .
Search for the obvious ones yourself
- Use your editor's search (Cmd+F on a Mac, Ctrl+F on Windows) for the words under SEARCH FOR THESE in check-lines.txt: client, %, $, price, key, password and the rest.
Fix, then check again
- Fix or cut every line it stops, and run the check again until it comes back .
Then you approve it
- Nothing goes out until you've read it yourself. The check catches lines. It doesn't know your business the way you do.
Add to them as you go
Claude Code's guide says to add to CLAUDE.md when the agent makes the same mistake a second time. Steps that belong to one job go in that job's skill file instead.
Keep each file short. The same guide says longer files take up more of the agent's context and are followed less reliably.
Take the files
The rules file
rules-file.txt
Read first, Never and Always, with the Never section filled in as an example. Copy the marked part and save it as CLAUDE.md, or paste it into your tool's system prompt.
DownloadThe skill file
skill-file.txt
One job, writing a post caption: when to use it, inputs, steps, an example and the checklist. Copy the marked part and save it as SKILL.md in its own folder.
DownloadThe check
check-lines.txt
Six kinds of line to stop, each with an example and why, the words to search for, and a check prompt to paste into a new chat. Save the whole file next to CLAUDE.md.
DownloadOpen a .csv in Google Sheets (File, then Import) or Excel.
The client, prices, roofer questions and bad lines in these files are examples, made up to show the shape. Nothing here is a result; it is three starter files.
Menu and file names in AI tools change. Go by the words on your own screen and your tool's own help page.
Want an AI operating system built for your company?
I do custom AI operating system builds for companies. Answer a few questions to see if yours is a fit.
See If You Qualify