How to Use Claude Projects to Stop Repeating Yourself

The tax you are paying without noticing

Count how many times a week you type some version of this: I am an operations manager at a mid sized logistics firm, our tone is friendly but direct, the client is Harrow Foods, they hate jargon, please keep it under 200 words.

Thirty seconds a go. Fifteen times a week. That is not the real cost though. The real cost is that you never type it identically twice, so the output drifts, and you spend longer fixing the drift than you spent explaining yourself in the first place.

The fix is a concept rather than a button: put your standing context somewhere reusable, so every conversation starts already knowing who you are.

The concept first

Every conversation you start is amnesiac by default. It knows nothing about your job, your clients or your preferences until you tell it. Reusable context means writing that background down once, in a place the assistant reads automatically, so the conversation begins informed.

There are two levels of this, and you want both.

The first is instructions: a short standing description of your role, your audience, your tone and your hard rules. The second is reference material: the actual documents you keep quoting from, such as your style guide, your service list, last quarter's numbers or the template your team insists on.

What good standing instructions look like

The common mistake is writing them like a job description. Nobody needs your mission statement. What helps is anything that changes how the output should read.

Write yours by filling in the blanks below and pasting the result into your standing instructions.

ABOUT ME
I am a [role] at a [size and type of organisation].
The people I write to most: [who they are, and how formal they expect me to be].
What I am usually trying to achieve: [chase, inform, persuade, reassure].
HOW I WRITE
Sentence length: [short and plain / longer and considered].
Spelling: [British / American].
Words I never use: [list the ones that make you wince].
Default length unless I say otherwise: [under 200 words].
RULES THAT DO NOT BEND
Never invent a date, figure, price or name. Write GAP instead.
If my request is ambiguous, ask one clarifying question before writing.
Do not open with a compliment or close with an offer of further assistance.

Then add the documents

Instructions cover how you write. Reference files cover what you know. Attach the handful of documents you find yourself quoting from: the service descriptions, the pricing rules, the escalation policy, two emails that sound exactly like you.

Keep it lean. Ten well chosen documents beat a hundred, because a folder stuffed with three years of drafts makes it harder, not easier, to find the right answer. If a document is out of date, replace it rather than adding the newer one alongside.

Before I ask you anything, tell me what you already know about me and my work
from the instructions and files you have.
List it as: my role, who I write to, my tone rules, and the reference documents
you can see.
Then tell me the three most useful things I have NOT given you, that would make
your answers noticeably better.

That test is the whole lesson in one prompt. If the answer is thin, your context is thin, and you now know exactly what to add.

Separate workspaces beat one giant one

One workspace per recurring situation works better than a single everything workspace. A client, a report, a recruitment round. Each gets its own instructions and its own files, and none of them bleeds into the others.

CLIENT: [name]
What they do: [one line].
Who I deal with: [names, roles, and how they like to be addressed].
History that matters: [the complaint, the renewal, the thing not to mention].
Their preferences: [format, length, level of detail].
Recurring work I do for them: [the weekly report, the monthly invoice summary].
When drafting for this client, follow the tone above and never quote a figure
that is not in the attached documents.

Set this up once and the next lesson gets much easier, because scheduled work runs without you sitting there to explain the background.