Last updated: June 2026

Claude Projects:Set Up a Workspace That Knows Your Style

Claude Projects are self-contained workspaces inside Claude.ai that combine a knowledge base of uploaded files, a set of custom instructions, and their own chat history. You set your audience, voice, and rules once, and every chat in the project follows them automatically. For writers, that means you stop re-explaining your style in every conversation. Projects are available on free and paid plans; free accounts can create up to five.

Most guides to Claude Projects are written for developers managing code. This one is written for writers managing voice, clients, and deadlines.

Jump to Setup See Writer Workflows

What is a Claude Project?

A Claude Project is a workspace inside Claude.ai that holds three things together: a knowledge base of files you upload, custom instructions Claude follows in every chat, and the chat history for that workspace. Anthropic describes Projects as "self-contained workspaces with their own chat histories and knowledge bases."

The problem a project solves is repetition. Without one, you open a fresh Claude chat and re-explain who your audience is, what tone you want, how long the piece should be, and which words to avoid. You do that every single time. A project lets you define all of that once. Every new chat inside the project inherits it.

Think of it as the difference between briefing a new freelancer on every job and having one writer who already knows the brand. The knowledge base is their reference shelf. The custom instructions are their standing brief. The chat history is their record of past work for you.

Projects are available to all Claude users, including free accounts, though some capabilities differ by plan. We cover the plan differences below so you know what you actually get.

The Two Building Blocks: Knowledge and Instructions

Everything a project does well comes from these two parts. Get them right and the rest follows.

Project Knowledge (the reference shelf)

The knowledge base is where you upload documents that define good output: your style guide, your best past articles, audience research, product facts, a glossary. Claude reads these to ground its writing in your real standards instead of generic advice.

Claude's context window is 200K tokens, roughly 150,000 words or about 500 pages. On paid plans, Anthropic says RAG mode can "expand capacity by up to 10x," so Claude retrieves only the relevant parts of large knowledge bases rather than loading everything at once.

Writer move: upload three of your strongest pieces, not thirty mediocre ones. Claude imitates what it sees. Feed it your best.

Custom Instructions (the standing brief)

Project instructions are the rules Claude follows in every chat inside the project. Anthropic notes you can "define project instructions for each project to further tailor Claude's responses," from tone to perspective.

These hold far more than profile-level instructions (project instructions support roughly 8,000 characters versus about 1,500 for your account profile), so you can be genuinely specific about voice, structure, and constraints.

Writer move: profile for identity and default tone; project instructions for the domain-specific rules of this client, newsletter, or series.

Why It Matters: One Prompt, Before and After

The same request, written for a blank Claude chat versus a properly configured project. The project absorbs everything you would otherwise have to type every time.

Weak: blank chat, every detail crammed in

Write me a blog post about email marketing for small businesses. Make it sound professional but friendly. Around 800 words. Don't be too salesy. Our audience is non-technical owners. Use short paragraphs and a clear takeaway at the end. Avoid jargon like "leverage" and "synergy"...

Strong: inside a configured project

Draft an 800-word post on email marketing for our audience.

The audience, tone, length, paragraph style, banned words, and takeaway format all live in the project. You only type what is unique to this piece.

How to Set Up a Claude Project (Step by Step)

Setup takes about ten minutes and you do it once per recurring job. Here is the order that works.

Create the project and name it for the job

In the Claude.ai sidebar, click Projects, then Create project. Name it after the recurring job it serves, not the topic. "Weekly Newsletter" or "Acme Corp blog" beats "Writing" because you will reuse the workspace for every instance of that job.

Add custom instructions (the voice and the rules)

Open the project, find the instructions panel, and write the rules Claude should follow in every chat here: who the audience is, the tone, the structure, the words to avoid, and how you want drafts delivered. This field holds far more than profile instructions, so be specific. Treat it like onboarding a new ghostwriter.

Upload your knowledge base

Add the documents that define good output: your style guide, two or three of your strongest published pieces, your audience research, product fact sheets, and any glossary of terms. Claude reads these to ground its writing in your actual standards rather than generic best practice.

Start a chat and request work

Open a new chat inside the project and give it a normal request: "Draft a 700-word post on X for our audience." The draft arrives already shaped by your instructions and knowledge. Iterate in that chat, and start a fresh chat for the next piece. All of them inherit the same setup.

Tip: once a project produces work you are happy with, duplicate it as the template for the next client or series. You inherit the structure and only swap the specifics, which is far faster than building from scratch each time.

A Fill-in-the-Blank Custom Instructions Template

Paste this into your project instructions and replace the bracketed parts. It covers the things Claude most often gets wrong when it does not know your context.

You are writing for [PUBLICATION / CLIENT].

AUDIENCE: [who reads this, their level of expertise, what they care about].

VOICE: [e.g. direct, warm, plain-spoken. First person or second person. Contractions allowed?].

STRUCTURE: [opening style, paragraph length, use of subheads, how every piece should end].

WORD COUNT: default to [N] words unless I say otherwise.

ALWAYS: [non-negotiables, e.g. one clear takeaway, concrete examples, short paragraphs].

NEVER: [banned words and habits, e.g. no "leverage", "unlock", "game-changer", no fluffy intros].

DELIVERY: give me the draft only, no preamble, unless I ask for options.

For more reusable starting points you can drop straight into a project, see our guide to using Claude and the broader prompt template library.

Four Claude Project Workflows for Writers

Each is one project you set up once and reuse for every instance of that job.

The newsletter project

Set up: Knowledge base: last 5 issues, subscriber persona, your section structure. Instructions: word count, voice, banned phrases, sign-off format.

Payoff: Every issue starts from your established format and voice. You spend your time on the idea, not re-teaching Claude your house style.

The client voice project

Set up: One project per client. Knowledge base: their brand guidelines, three approved past pieces, their product list. Instructions: their tone, their audience, their no-go words.

Payoff: You switch clients by switching projects, and the voice switches with you. No more cross-contaminating one client's tone into another's draft.

The book or long-form project

Set up: Knowledge base: your outline, character or argument notes, completed chapters. Instructions: POV, tense, style constraints, what is canon.

Payoff: Claude keeps continuity with what you have already written instead of contradicting earlier chapters or drifting in tone.

The repurposing project

Set up: Knowledge base: a long-form source piece plus your platform rules. Instructions: how a LinkedIn post, a thread, and a newsletter blurb should each be shaped.

Payoff: Drop in one article and pull out five platform-native variants that already match how each channel should sound.

The Mistake Most People Make With Claude Projects

The common failure is treating the knowledge base like a junk drawer. People upload every document they own, assume more context is better, and then wonder why drafts feel muddled.

Claude imitates what you give it. Upload thirty average articles and you get average writing back. Upload your three best pieces and a tight style guide, and the output sharpens. Curate the knowledge base the way you would curate a portfolio.

The second mistake is expecting a new chat to remember decisions made in another chat. Within a project, each chat is separate; what carries across is the knowledge base and instructions, not the conversation. If a decision matters long-term (a naming convention, a positioning call), write it into a file and add it to the knowledge base so it persists.

A related point: Claude Projects are about persistent context, not the in-chat interactive previews. If you want those rich previews of drafts, documents, or code, that is a separate feature covered in our guide to Claude Artifacts.

What You Get on Each Plan

Projects exist on every plan, but the capacity and collaboration features differ. Here is the breakdown based on Anthropic's documentation.

Capability	Free	Pro / Max	Team / Enterprise
Create projects	Up to 5	Yes	Yes
Custom instructions	Yes	Yes	Yes
Enhanced knowledge (RAG)	No	Yes (up to 10x capacity)	Yes
Share / collaborate	No	No	Yes

Plan capabilities and limits change. Confirm current details against Anthropic's support documentation before relying on them. For help choosing between Claude plans, see our Claude Pro vs Max vs API comparison.

A Project Is Only as Good as Its Instructions

The custom instructions field is where most writers lose the gains. If your prompts are vague, your project produces vague work. PromptWritingStudio teaches you to write the precise, repeatable prompts that make a workspace like this genuinely save you hours.

Grade Your Prompt Free

Frequently Asked Questions

Common questions about Claude Projects, answered for writers

What is a Claude Project?+

A Claude Project is a self-contained workspace inside Claude.ai that bundles three things together: a knowledge base of files you upload, a set of custom instructions Claude follows in every chat, and the chat history for that workspace. Instead of re-explaining your style guide, audience, and context in every conversation, you set it once and every chat in the project inherits it. Anthropic describes Projects as having "their own chat histories and knowledge bases."

Are Claude Projects free?+

Yes, partly. Per Anthropic's documentation, Projects are available to all users, including free accounts, and free users can create a maximum of five projects. However, enhanced project knowledge with RAG (the retrieval system that lets Claude search across large uploaded knowledge bases) is only available on paid plans: Claude Pro, Max, Team, or Enterprise. So a free user can build a project, but the document-search capacity is more limited.

How big can a Claude Project knowledge base be?+

Claude's context window is 200K tokens, which is roughly 150,000 words or about 500 pages of text. On paid plans, Anthropic says RAG mode can "expand capacity by up to 10x" so Claude retrieves only the relevant chunks of your uploaded files rather than loading everything at once. For writers, that means you can upload a full back catalogue of past articles, a brand style guide, and reference material without blowing the limit.

What is the difference between Claude Projects and custom instructions?+

Profile custom instructions apply to every chat across your whole account and have roughly a 1,500-character limit. Project instructions apply only to chats inside that one project and support far more (around 8,000 characters). The practical split: put your identity and default tone in your profile, and put domain-specific rules (this client's voice, this newsletter's format, this series' constraints) in each project.

Can I use Claude Projects for writing instead of coding?+

Yes. While developers use Projects for codebases, the feature is just as useful for writers. Upload your style guide, three of your best past articles, and your audience notes; set custom instructions describing your voice and structure rules; then every draft, outline, and edit you request inside that project comes back already aligned to your standards. You stop re-teaching Claude your style on every single chat.

Do Claude Projects remember previous chats?+

Each project keeps its own chat history, so you can return to past conversations within that workspace. However, a brand-new chat does not automatically read the content of your other chats. What every new chat does inherit is the project's knowledge base and custom instructions. If you want continuity of decisions across chats, record those decisions in a file and add it to the knowledge base.

Can I share a Claude Project with my team?+

Sharing and collaboration features are limited to Team and Enterprise plans, where you can grant permission-based access and let multiple people contribute to the same project. On Pro and free plans, a project is private to your account. A common workaround for solo writers and small teams is to document the project's instructions and knowledge files so they can be recreated by a collaborator.

More Claude Guides for Writers

Keep building your Claude setup with these companion guides and tools.