Claude Projects made more sense when I stopped thinking of them as folders
热度趋势
百分比基于当前可用热度信号，而非评论数或独立用户人数。
一位Reddit用户分享了对Claude Projects的新看法，超越了将其视为简单聊天文件夹的观念。他们将“Knowledge”定义为Claude应该知道的内容，“Instructions”定义为Claude应该如何工作，而“Prompt”则定义为当前所需。该用户对其他人构建了什么以及哪些Claude Projects最有用且经常被重新访问感到好奇。
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?