Learn what a Claude workspace is, what files go inside it, and why it makes Claude dramatically more useful. A plain-language guide for non-developers.
Every time you open Claude, it knows nothing about you. Not your role, not your company, not your tools, not how you like things done. You explain yourself, get a mediocre response, explain more, and eventually get something usable. Then tomorrow you do it again.
A workspace is a directory on your computer, usually named .claude/, that contains several types of files. Each type does something different. Everything connects through CLAUDE.md, the brain of your workspace.
The difference between Claude with and without a workspace is the difference between a stranger and a colleague. A stranger needs everything explained. A colleague just gets to work.
Everyone who uses Claude Code more than occasionally. The workspace system isn't a developer feature. It's a productivity feature.
You have two options. Build it manually by creating files and writing instructions from scratch. This takes a few hours if you know what you're doing.
No. A workspace is just a folder of text files. The Froject generates one for you without any coding.
In the root of your project directory, or in any folder where you run Claude. Claude automatically detects and loads it.
Yes. Since it's just files, you can commit it to Git, share it via a ZIP file, or use The Froject's URL sharing feature.
Yes. In co-work mode, Claude Desktop reads your workspace files. You get skills, commands, and context. Terminal mode gives you full access to everything.