Claude Projects: how to organise long-running work and context
Claude Projects are workspaces that group related chats with a shared knowledge base and custom instructions. You upload files such as briefs, style guides and research, write instructions once, and every chat in the project starts with that context. Projects suit ongoing work on a client, product or topic, and on Team and Enterprise plans they can be shared with colleagues.
What is a Claude Project?
A Project is a space in the Claude app that holds everything for one piece of ongoing work. It has three parts: a knowledge base of files you upload, custom instructions that tell Claude how to behave in this project, and the chats you have inside it. Every new chat in the project starts with the instructions and can draw on the files, so you do not need to paste the same brief or style guide again. For the wider set of Claude features, see what Claude is.
When should you use a project?
| Situation | Use a project? |
|---|---|
| A one-off question | No, a normal chat is fine |
| Ongoing work for one client | Yes, one project per client |
| Developing a product over months | Yes, with specs and decisions |
| A recurring report | Yes, with the template and data notes |
| Research on a topic over weeks | Yes, with sources and summaries |
How do you set one up?
- Name it clearly: Use the client, product or topic name so it is easy to find.
- Write instructions: Describe the audience, goal, tone, formats and any rules Claude must follow.
- Upload key files: Add the current brief, style guide, product facts and examples of good work.
- Start a test chat: Ask Claude to summarise what it knows about the project to check it read the files.
- Refine: Adjust instructions after the first few chats based on what Claude got wrong.
What makes good project instructions?
Instructions work best when they are short and specific. Put detailed procedures that apply across projects into Claude Skills instead, so they can be reused.
How should you manage project files?
- Upload the current version only and delete outdated drafts
- Name files clearly, for example “Brand guide v3 (current)”
- Prefer text-based files that Claude can read easily
- Add a short “project summary” document that you update as decisions are made
- Connect live sources through connectors rather than uploading copies that go stale
Connecting Claude to Google Drive, SharePoint or other tools is covered in how to connect Claude to your apps.
How do teams use shared projects?
On Team and Enterprise plans, projects can be shared with colleagues, with view or edit permissions. Shared projects mean everyone drafts from the same brief and the same rules, which reduces inconsistency. Agree who owns each project, who can change its instructions and when it should be archived.
What projects work well for a design or marketing team?
- Client workspace: Brand guide, past work and contact notes for one client.
- Design system: Component docs, tokens and writing guidelines for consistent specs.
- Research synthesis: Interview notes and survey data for a study.
- Content calendar: Brand voice, audience and themes for social and blog content.
- Proposal writing: Service descriptions, pricing rules and case studies.
- Product spec: Requirements, decisions and open questions for one feature.
Design teams can pair a design-system project with our guide to design systems that work.
How do you keep a project useful over time?
Projects drift as work changes. Once a month, open each active project and check three things: are the instructions still right, are the files current, and is there a short summary of recent decisions? Archive projects for finished work so they do not clutter the list or get used by mistake. When a project gets very large, split it, for example into separate projects for strategy, design and content, each with its own focused instructions and files.
How do Projects compare with memory and custom instructions?
| Feature | Scope | Best for |
|---|---|---|
| Custom instructions | Every chat you have | Personal preferences such as tone and language |
| Memory | Facts Claude remembers about you across chats | Personal context that rarely changes |
| Projects | Chats inside one project | Work for one client, product or topic |
Use all three together: general preferences in custom instructions, stable facts in memory, and work-specific context in projects. That keeps each layer small and easy to maintain.
What are the limits?
- Project knowledge has size limits that vary by plan
- Files are snapshots; they do not update unless you replace them
- Long projects can collect outdated instructions; review them regularly
- Do not store sensitive data your policy does not allow in AI tools
How UIUX Studio helps
We help teams set up Claude workspaces, from project structures and instructions to skills and connectors that keep context current. Talk to our Agentic AI & Automation team.
Frequently asked questions
What is a Claude Project?
A workspace that groups chats with shared files and custom instructions.
Are Projects free?
Projects are available on Claude plans; limits and sharing depend on your plan.
Can I share a project with my team?
Yes, on Team and Enterprise plans, with view or edit permissions.
Do project files update automatically?
No. Uploaded files are copies; use connectors for live sources.
How many projects should I have?
One per client, product or long-running topic is a good rule.