Cursor Token Efficient Rules 1. Think before acting. Read existing files before writing code. 2. Be concise in output but thorough in reasoning. 3. Prefer editing over rewriting whole files. 4. Do not re-read files you have already read unless the file may have changed. 5. Test your code before declaring done. 6. No sycophantic openers or closing fluff. 7. Keep solutions simple and direct. 8. User instructions always override this file.
What Are Tokens and Why Do They Matter?
🎮 Imagine this:
Tokens are like arcade coins. Every word Claude reads or writes costs you a coin. If you ask “what time is it?” and Claude replies with “Great question! I love that you asked that. The current time is…” those extra words are coins thrown in the trash. You are paying for filler.
💡 The solution:
A file called CLAUDE.md with 8 rules that tell Claude: “stop talking too much.” It is like putting a sign on the machine that says “just give me what I asked for, no fluff.” You install it in 30 seconds and that is it.
- 8 simple rules
- 63% fewer words
- 30s to install
The 8 Rules Explained Simply
Each rule is an instruction Claude will follow across your entire project. Here is each one explained like you are five years old:
1. Read before writing
Before touching a file, Claude reads it first. Like reading a recipe completely before you start cooking so you do not mess up halfway.
Think before acting. Read existing files before writing code.
2. Be concise but deep
Claude gives you the direct answer without rambling. Like a doctor telling you what you have and what to take, not the whole history of medicine.
Be concise in output but thorough in reasoning.
3. Edit, do not rewrite
If only one line needs changing, Claude changes that line. It does not rewrite the whole file. Like fixing a loose button instead of making a new shirt.
Prefer editing over rewriting whole files.
4. Do not reread what you already read
If Claude already read a file, it will not read it again unless it changed. Like a restaurant menu. Once you know it, you do not reread it every time.
Do not re-read files you have already read unless the file may have changed.
5. Test before saying done
Claude checks that the code works before saying it is finished. Like a chef tasting the dish before serving it.
Test your code before declaring done.
6. Zero fluff or greetings
No “Of course! Great question!” or long goodbyes. Straight to the point. Imagine you pay per word, because you do.
No sycophantic openers or closing fluff.
7. Simple and direct solutions
Claude does not over-engineer. If you need a nail, it gives you a hammer, not a hammer factory.
Keep solutions simple and direct.
8. You are in charge
If you ask for something specific, that always overrides any rule. Claude works for you, not the other way around.
User instructions always override this file.
The Numbers Do Not Lie
Real users tested these 8 rules and the results speak for themselves. Same answers, but with much less unnecessary text:
- 63% fewer words overall
From 465 words on average to just 170 - 75% fewer words in code reviews
From 120 words to just 30 - 64% fewer words in explanations
From 180 words to just 65 - 16% total usage savings
Reported by real users