This is so interesting. As an Obsidian user I tried to retrain my brain into a no folder structure and just tag everything. It didn't stick. Now with Cowork a folder/project structure is imperative!
So glad you wrote about this topic. You need structure and organization to get real results out of Claude.
I use a different approach where the workspace = cowork project and that’s the full context for the session, e.g. sales, mktg, accounting, etc.
I think both approaches work, I just need to scale more while keeping structure.
We should connect and share our approach one if those days.
Ps: I defined naming conventions and workspaces structure in system md files so it can be enforced -I actually have a skill that audits everywhere for compliance and fixes on the fly 😉
Hi Frank, How do you suggest implementing this structure in a situation where you advise multiple clients? Do you have a separate Workspace for each client or do you have one Workspace with seperate Projects folders for each client? Note that the underlying assumption is that I am providing similar outcomes for each client. Cheers
Folder systems work because Claude reads structure before it reads intent. A well-named directory is cheap prompt engineering: it tells the model what matters without spending a single token explaining it.
I kinda stumbled into this same realization. The folder structure helps but the thing that actually made a difference for me was having Claude maintain a running project log in the folder — just a markdown file where it notes what it did last session. Saves me from re-explaining context every time.
I do something similar but per-project, one folder with a http://CLAUDE.md that just points to the other files instead of dumping everything into context. Cuts down on Claude re-reading stuff it doesn’t need for the task at hand.
This is so interesting. As an Obsidian user I tried to retrain my brain into a no folder structure and just tag everything. It didn't stick. Now with Cowork a folder/project structure is imperative!
BRAVO! An affirming and relevant post indeed. Logical, methodical, effective, and efficient framework, indeed!! Thank you.
So glad you wrote about this topic. You need structure and organization to get real results out of Claude.
I use a different approach where the workspace = cowork project and that’s the full context for the session, e.g. sales, mktg, accounting, etc.
I think both approaches work, I just need to scale more while keeping structure.
We should connect and share our approach one if those days.
Ps: I defined naming conventions and workspaces structure in system md files so it can be enforced -I actually have a skill that audits everywhere for compliance and fixes on the fly 😉
Hi Frank, How do you suggest implementing this structure in a situation where you advise multiple clients? Do you have a separate Workspace for each client or do you have one Workspace with seperate Projects folders for each client? Note that the underlying assumption is that I am providing similar outcomes for each client. Cheers
A solid folder system for Claude is such an underrated productivity hack. Organization really changes how well AI works.
How do i implement this into my Claude projects, I saw the other post on https://artificialcorner.com/p/cowork-setup?utm_source=substack&utm_medium=email
But I dont see instructions on how to set this up?
I would appricate if you can let me know how, like what prompts/commands to use and so on
This is good stuff! I'm glad I came across this post because this is exactly what I'm dealing with right now.
Folder systems work because Claude reads structure before it reads intent. A well-named directory is cheap prompt engineering: it tells the model what matters without spending a single token explaining it.
I kinda stumbled into this same realization. The folder structure helps but the thing that actually made a difference for me was having Claude maintain a running project log in the folder — just a markdown file where it notes what it did last session. Saves me from re-explaining context every time.
This info is amazing. THANK YOU for giving it to us.
I do something similar but per-project, one folder with a http://CLAUDE.md that just points to the other files instead of dumping everything into context. Cuts down on Claude re-reading stuff it doesn’t need for the task at hand.
This is helpful thank you
Excellent Job! You bring true value.
Is this approach applicable to other AI platforms? i.e. ChatGPT, Grok, etc.