Short answer: most people treat Claude as a smart stranger they brief from scratch every morning. The best practice that matters most is giving it a written, dated record of your business that every session reads first. Prompt tips are worth a little; that is worth a lot.
The pain: Claude forgets your company
You explain your customers, your pricing and your tone on Monday. On Tuesday, in a new chat, Claude has no idea. A Project remembers some of it, but only inside that Project. Claude Code has its own memory files. A teammate's Claude knows nothing about yours. So you re-explain, or you paste, and the answers drift.
Anthropic's own numbers show what memory is worth: on their benchmark, Claude Opus 5.5 scored 0.66 without memory and 0.84 with it [1].
Seven habits that get more out of Claude
- Write your company down once. One folder of short files: who you are, how you write, your customers, your prices, your decisions. Each fact dated.
- Make every session read an index first. Keep it short. Claude Code loads only the first 200 lines of its memory index [4]; ours is 39.
- One topic per chat. Recall degrades as a conversation grows [3]. Start fresh when the subject changes.
- Match effort to the task. Lower effort for routine work makes your usage limits last [2].
- Turn off tools you aren't using. Connectors are token-intensive [2].
- Correct with a file, not a chat. When Claude gets something wrong twice, fix the fact in the folder, so the fix sticks for every future session.
- Review the folder on a schedule. Memory that's never cleaned goes wrong quietly. Strike changed facts instead of leaving them beside the new ones.
Habits 1, 2, 6 and 7 are the ones almost nobody does, and they are the ones that compound.
Do it yourself, or have it done
You can build and keep that folder yourself. Or Chet can do it for you: Chet sets up the folder (we call it Start) from your own documents, grades your Claude setup, and fixes what breaks. $99 a month, cancel anytime.
Maximize Claude with Chet: https://www.coworkers.global/get-chet?utm_source=blog&utm_medium=internal&utm_campaign=chet&utm_content=claude-best-practices-cta
FAQ
What's the single best Claude tip? Stop re-explaining your business. Write it down once, in one place every Claude session reads.
Are better prompts the answer? They help one chat. A shared record of your company helps every chat, Project and tool.
Does this work in Claude Code and Cowork too? Yes. A plain folder of files works anywhere Claude can read files.
Sources
- Anthropic, components of agent memory: https://anthropic.com/research/components-of-agent-memory
- Claude Help Center, how usage and length limits work: https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work
- Claude Platform docs, context windows: https://platform.claude.com/docs/en/build-with-claude/context-windows
- Claude Code docs, memory: https://code.claude.com/docs/en/memory
Regards,
Charles Stack
Founder, Coworkers.Global
Coworkers.Global is not affiliated with Anthropic. Claude is a trademark of Anthropic, PBC.