Claude Projects: Set Up A Workspace That Knows Your Work
The short version
- Claude Projects are workspaces that hold instructions and reference files, so every chat inside starts with that background.
- Make one project per client, product or repeating job. Mixing jobs in one project muddies the answers.
- The instructions field is where most of the value is. Write it like a briefing, with rules for tone, format and what to do when unsure.
- Keep the knowledge files lean and current. Old versions sitting next to new ones cause wrong answers.
Claude Projects solve the most annoying part of using an AI assistant: explaining your situation again every time you open a new chat. A project is a workspace with its own instructions and its own files. Any chat you start inside it already knows who you are, what the work is and how you want it done. If you use Claude for the same kinds of tasks every week, a project will save you more time than any single prompt trick.
Here’s how to set one up, what to put in it, and a few setups that work well for non-technical people. If you’re new to the tool itself, start with how to use Claude AI.
What A Project Holds
Every project is built from these pieces:
- A name and short description, so you can find it in the sidebar.
- Project instructions: standing guidance Claude follows in every chat within the project.
- Project knowledge: documents and text you upload for Claude to draw on, such as a style guide, a price list, a client brief or past examples.
- The chats themselves, grouped together so the work for one client or job stays in one place.
Treat each new chat as starting from the instructions and files. Don’t count on it recalling details from a different chat in the same project. If a decision matters going forward, add it to the instructions or the knowledge files.
Setting Up Claude Projects Step By Step
- Open Claude and find Projects in the left sidebar. Create a new project.
- Name it for one job, like “Monthly client newsletter” or “Dental clinic client.” Add a one-line description.
- Write the project instructions (more on this below).
- Upload your knowledge files. Start with three to five that you’d otherwise paste in again and again.
- Start a chat inside the project and give it a real task. Check whether it used the files and followed the rules.
- Adjust the instructions based on what went wrong. Repeat until the first answer is usually close to right.
Project features and limits can vary by plan, so check what your account offers in the sidebar.
Write Instructions That Do The Heavy Lifting
The instructions field is short on screen and huge in effect. Cover who you are, what the project is for, the format you want, and rules for uncertain cases. Here’s an example for a real estate agent’s listing project:
“I’m a residential real estate agent. In this project you write property listing descriptions and social posts for my listings. Use the style guide and the three sample listings in project knowledge as your model. Listings are 150 to 200 words, lead with the best feature, and end with the neighborhood. Never mention schools by quality, never describe who the home is ideal for, and never guess at square footage or features I didn’t give you. If key details are missing, ask before writing.”
Notice the rules for what not to do and what to do when details are missing. Those two lines prevent most of the problems people complain about.
What To Put In Project Knowledge
Good knowledge files are specific, current and short enough to be useful. Strong candidates:
- A one-page style guide: words you use, words you avoid, tone and formatting.
- Two or three examples of your best past work, clearly labeled as examples.
- Reference facts: price lists, service descriptions, product specs, team bios.
- Client or project briefs: goals, audience, deadlines, past decisions.
- Procedures you want followed, written as steps.
Leave out old versions. If last year’s prices sit next to this year’s, Claude may quote the wrong ones. Keep sensitive personal data out too, unless your plan and your company’s rules allow it. If your procedures aren’t written down yet, our guide on writing SOPs with AI gets them on paper quickly.
Five Claude Projects Worth Building This Week
The newsletter desk
Upload your last six newsletters and a list of topics. Each month, paste in rough notes and ask for a draft in the usual structure.
One project per client
For freelancers and consultants, put each client’s brief, brand guide and meeting notes in their own project. Switching clients becomes a click.
The long document reader
Upload a lease, a funding agreement or a policy manual and ask questions across it. Ask Claude to quote the section it relied on, then check that section yourself. For legal or financial documents, treat the answers as a reading aid and have a professional confirm anything that matters.
The job hunt
Your resume, a list of target roles and your best cover letter go in. Paste each new job post and ask for a tailored cover letter and five likely interview questions. Add a rule to the instructions that Claude must never invent experience or skills that aren’t on your resume. Then read each letter before sending, since a wrong claim in a cover letter can cost you the interview.
The team FAQ
Upload your handbook and common questions. On a team plan, a shared project lets colleagues ask the same source. Spot check answers weekly; our guide to spotting AI mistakes shows what to watch for.
Keep Your Projects Healthy
Once a month, open each project and ask: are the files current, and did any chat go wrong in a way a new rule would prevent? Update both. Archive projects you no longer use so the sidebar stays short. A small set of well-kept Claude Projects beats a pile of half-built ones.
Master Claude, Projects Included
AI For Getting The Most From Claude covers Projects in depth, along with working through long documents, careful reasoning and getting drafts that sound like you. You get a worked example of a full project build, ready-to-use instruction templates, a prompt pack and a cheat sheet.
