← All Conversations
July 12, 2026

Don't use Claude wrong ever morning

Claude Projects memory context productivity

Summary

We need to produce a summary 250-500 words, covering core insight, arguments, tools/techniques, actionable takeaways. No preamble, no labels. Just the summary text. We must ensure length between 250 and 500 words. Let's aim ~300-350 words. We need to capture: problem of Claude sessions resetting, solution: Claude Cowork using Projects, CLAUDE.md and memory.md, hierarchical rules, workstations, benefits, actionable steps: create master rule file, memory file, set up workstation projects, use plain text, etc. Let's craft ~340 words. Check word count. We'll count roughly. Write: "Most users treat Claude like a stateless chatbot, re‑explaining context each session, which wastes time and prevents the AI from learning personal preferences. The article argues that this is unnecessary because Claude’s Projects feature (called Claude Cowork) lets you give the model persistent context through plain‑text files. The core insight is that a two‑file system—CLAUDE.md for permanent rules and memory.md for a running notebook—creates a hierarchical knowledge base that Claude reads at the start of every session. By layering workstation‑specific files (e.g., Email HQ, Newsletter HQ, Personal Finance) on top of the master rulebook, the AI inherits your voice, workflow rules, and project details without repeated prompting. This transforms Claude from a stranger into a long‑term partner akin to Jarvis, enabling tasks such as routing screenshots to the correct folder, drafting emails in your tone, building spreadsheets from raw statements, and preparing meeting briefings with minimal effort. The article outlines how to implement the system: create a CLAUDE.md file containing your overall preferences, writing style, and task‑handling guidelines; start a memory.md file that Claude updates as you work; then set up separate Project folders for each major area of your life, each with its own workstation rules that stack onto the master file. Because the files are plain text, no coding or developer assistance is required. Actionable takeaways include: (1) adopt the Claude Cowork workflow by creating these files today; (2) define clear voice and style guidelines in CLAUDE.md; (3) let memory.md capture corrections and preferences so they persist; (4) organize workstations around recurring domains (email, newsletters, finance, etc.) and add project‑specific rules as needed; (5) regularly review and refine the files to compound improvements. By doing so, users can cut repetitive prompting, achieve consistent outputs, and unlock the full productivity potential of their Claude Pro subscription." Now count words. Let's count quickly. Most(1) users2 treat3 Claude4 like5 a6 stateless7 chatbot,8 re‑explaining9 context10 each11 session,12 which13 wastes14 time15 and16 prevents17 the18 AI19 from20 learning21 personal22 preferences.23 The24 article25 argues26 that27 this28 is29 unnecessary30 because31 Claude’s32 Projects33 feature34 (called35 Claude Cowork)36 lets37 you38 give39 the40 model41 persistent42 context43 through44 plain‑text45 files.46 The47 core48 insight49 is50 that51 a52 two‑file53 system—CLAUDE.md54 for55 permanent56 rules57 and58 memory.md59 for60 a61 running62 notebook—creates63 a64 hierarchical65 knowledge66 base67 that68 Claude69 reads70 at71 the72 start73 of74 every75 session.76 By77 layering78 workstation‑specific79 files80 (e.g.,81 Email82 HQ,83 Newsletter84 HQ,85 Personal86 Finance)87 on88 top89 of90 the91 master92 rulebook,93 the94 AI95 inherits96 your97 voice,98 workflow99 rules,100 and101 project102 details103 without104 repeated105 prompting.106 This107 transforms108 Claude109 from110 a111 stranger112 into113 a114 long‑term115 partner116 akin117 to118 Jarvis,119 enabling120 tasks121 such122 as123 routing124 screenshots125 to126 the127 correct128 folder,129 drafting130 emails131 in132 your133 tone,134 building135 spreadsheets136 from137 raw138 statements,139 and140 preparing141 meeting142 briefings143 with144 minimal145 effort. The146 article147 outlines148 how149 to150 implement151 the152 system:153 create154 a155 CLAUDE.md156 file157 containing158 your159 overall160 preferences,161 writing162 style,163 and164 task‑handling165 guidelines;166 start167 a168 memory.md169 file170 that171 Claude172 updates173 as174 you175 work;176 then177 set178 up179 separate180 Project181 folders182 for183 each184 major185 area186 of187 your188 life,189 each190 with191 its192 own193 workstation194 rules195 that196 stack197 onto198 the199 master200 file.201 Because202 the203 files204 are205 plain206 text,207 no208 coding209 or210 developer211 assistance212 is213 required.214 Actionable215 take

Hey

Let me tell you what my normal mornings used to look like.

I would wake up, open 6 different tabs. Check emails. Open Notion. Look at my newsletter draft. Switch back to email. Forget what I was doing. Start over.

Every single day.

I was using Claude too. But here is the embarrassing part. I was using it exactly like Google. Type a question. Get an answer. Close the tab. Next session, Claude remembered nothing. I remembered nothing. We were strangers every single morning.

I thought this was just how AI worked.

I was wrong.

A few days ago I came across Jeff Su's Cowork setup and it broke something in my brain. Because he wakes up, opens Claude, and in one session it reviews his expenses, finishes his newsletter draft, and routes tasks to the right folder without him explaining anything.

Claude remembers his projects. His voice. His rules. His context.

That is not a chatbot. That is Jarvis.

And almost nobody I know is using Claude this way.

The problem most people have with Claude (and do not even know it)

Every time you open a new Claude session, it starts fresh.

No memory of what you worked on yesterday. No knowledge of your writing style. No idea what projects you are running. You have to re-explain yourself. Every. Single. Time.

So you keep prompting Claude with the same context over and over. "I run a newsletter. My audience is non-technical. Write in a casual tone." Again. And again. And again.

This is the equivalent of hiring a personal assistant and firing them every evening. Then hiring a new one every morning and spending 30 minutes re-training them before any real work can happen.

Most people accept this as normal. It is not normal. It is just how most people use Claude.

Jeff Su figured out the fix. And it is so simple it almost feels like cheating.

What Claude Cowork actually is (and why people keep sleeping on it)

Claude Cowork is not a feature most people stumble into.

You can pay for Claude Pro every month, use it daily, and still have no idea Cowork exists in any meaningful way. Because Anthropic does not advertise it loudly. There is no pop-up. No tutorial that forces you to engage with it.

So people open Claude, type their prompt in the chat window, and move on. Completely missing the thing that would 10x their results.

Cowork is where you build Projects. And inside those Projects, you can give Claude permanent context. Files it reads every session. Rules it follows without being reminded. A voice profile it uses whenever it writes for you.

The difference between using Claude in a chat window versus using Claude inside a properly set up Project is the difference between texting a stranger and briefing a business partner who has worked with you for two years.

The architecture that makes this work

Here is what Jeff Su built, and what I think is the real unlock.

Two files. That is the whole system.

CLAUDE.md is a master rulebook. You write your preferences, your workflow rules, your voice guidelines, and how you want Claude to handle different types of tasks. Claude reads this at the start of every session. It becomes the operating system.

memory.md is a running notepad. Claude updates it as you work. Corrections you made once get saved. Preferences you mentioned once do not need to be repeated. It is how the system compounds over time.

Then you layer workstations on top of this. Email HQ. Newsletter HQ. Personal Finance. Each one has its own rules that stack on top of the master rulebook.

The result is a three-level hierarchy. Root rules that apply everywhere. Workstation rules for each area of your life. Project rules for specific tasks inside those areas.

When Claude writes an email inside this setup, it reads your root voice file first, then layers email-specific rules on top. The output sounds like you because it is literally following your documented voice, not guessing.

This is not complicated to build. Jeff does the whole thing with plain text files. No code. No developer needed.

[10 AI Stocks to Lead the Next Decade](https://sendercircle.com/r.php?id=2666)

AI is fueling the Fourth Industrial Revolution and these 10 stocks are front and center.

One of them makes $40K accelerator chips with a full-stack platform that all but guarantees wide adoption.

Another leads warehouse automation, with a $23B backlog – including all 47 distribution centers of a top U.S. retailer – plus a JV to lease robots to mid-market operators.

From core infrastructure to automation leaders, these companies and other leaders are all in The 10 Best AI Stocks to Own in 2026.

[Free now.](https://sendercircle.com/r.php?id=2666)

[Click here to Grab it before the paywall locks. ](https://sendercircle.com/r.php?id=2666)

Download Now for FREE (https://sendercircle.com/r.php?id=2666)

The moments that make this feel like actual Jarvis

Once the system is live, here is what becomes possible.

You screenshot a framework or a template you found online. You paste it in and say "figure out where this belongs." Claude reads the context of your workstations and routes it to the right folder. You do not think about it.

You say "draft a follow-up email from my last meeting." Claude pulls the context, finds the relevant project, loads the right workstation rules, and writes in your voice. You review and send. The whole thing takes 2 minutes instead of 20.

You drop 12 months of credit card statements into Claude and say "build me a spending tracker." Claude creates a full spreadsheet with categories, monthly summary, and yearly overview. You correct one thing once. It never makes that mistake again.

You say "I am going to a client meeting tomorrow, prepare a briefing." Claude already knows your client history, your communication style, and what projects are active. It produces something useful because it has the context to do so.

This is the version of Claude that most people paid for and never unlocked.

Why people are missing this right now

There are three reasons almost nobody in my network is doing this yet.

First, Cowork looks intimidating from the outside. "Projects," "files," "CLAUDE.md" sounds technical. People assume you need to know how to code. You do not. Jeff Su does this entire setup with markdown files. If you can type in Notepad, you can build this.

Second, people are addicted to the instant gratification of the chat window. You get an answer in 10 seconds. It feels productive. But it is shallow productivity. You are solving the same problems again and again instead of building a system that eliminates them.

Third, nobody talks about the setup phase. They show you the output. "Look, Claude wrote this email." Nobody shows the 2 hours of initial setup that made that possible. So people assume the magic just happens, get disappointed with basic Claude, and go back to the chat window.

The setup is the work. But you only do it once. And then Claude does the work forever.

How to actually start today

Do not try to build everything at once. Jeff's advice is very clear here.

Start with one workstation. Pick the area of your life where you repeat the most work. For most people in my audience, that is email or content creation.

Create a folder. Drop in a CLAUDE.md with 3 to 5 rules. Write your voice principles in plain English. Open that folder inside Cowork and star it so every session defaults there.

Run one task inside it. See the difference.

Then build the next workstation. And the next.

The system compounds because every correction you make gets saved. Every preference you log becomes permanent context. The person who starts this week is already ahead of the person who starts next month.

My final thoughts

I will be honest with you.

I put off setting this up for months. It felt like extra work on top of already too much work. I kept telling myself I would do it when things slowed down.

Things never slow down. You know this.

The 2 hours I spent setting up my Cowork OS saved me more time in the first week than I expected. Not because Claude became smarter. Because I stopped re-explaining myself. I stopped losing context between sessions. I stopped starting from zero every morning.

The version of Claude that most people are using is like buying a sports car and only ever driving it in first gear. It moves. But it is not doing what it was built to do.

Cowork is the full gear range.

And it is sitting there inside your Claude subscription, ready to go, waiting for you to actually use it.

Start this weekend. One workstation. One [CLAUDE.md](https://CLAUDE.md) file. Five rules.

That is all it takes to go from chatbot to Jarvis.

Stay curious, talk to you tomorrow.