Claude Projects made more sense when I stopped thinking of them as folders
Heat trend
The percentage is based on available heat signal, not comment count or independent people.
A Reddit user shares a new perspective on Claude Projects, moving beyond the idea of them simply being chat folders. They define 'Knowledge' as what Claude should know, 'Instructions' as how Claude should work, and 'Prompt' as what is needed right now. The user is curious about what others have built and which Claude Projects are most useful and frequently revisited.
I used to think Claude Projects were basically just folders for keeping chats organized.
But while testing them, a better way of thinking about them clicked for me:
A Project can turn Claude into a specialist for one recurring job.
For example:
Job-search Project
- resume
- career history
- target roles
- achievements
- rules like “don’t invent experience”
Then you can drop in a job description and ask where you actually match, where the gaps are, and what needs changing.
Or an n8n Project:
- n8n docs
- workflow examples
- templates
- SOPs / rules
Then you’re not asking a completely general Claude every time. You’re giving it the context for that particular type of work.
The mental model I’m using now is:
Knowledge = what Claude should know Instructions = how Claude should work Prompt = what you need right now
I still wouldn’t use Projects for every random question.
But for work where I keep giving Claude the same background again and again, this makes much more sense.
Curious what everyone else has built — what’s the most useful Claude Project you actually keep coming back to?