The Legal Consultant's Guide to Claude Projects and Custom Instructions

If you're pasting the same background — your jurisdiction, your practice area, your firm's tone — into every new Claude conversation, you're doing repetitive work that a five-minute setup eliminates permanently. Claude's Projects feature (with custom instructions and reference files) is built exactly for this, and almost no lawyers use it.

What a Project actually does for you

A Project is a persistent workspace with its own instructions and its own set of reference files that every conversation inside it can draw on. Set it up once for, say, "Contract Review" or "Client Intake," and every new chat inside that project already knows your jurisdiction, your preferred tone, and whatever reference documents you've uploaded — a fee schedule, a glossary of firm-specific terms, a template.

Custom instructions worth setting

Here's the instruction block I use for a general legal-consulting Project. Adjust the bracketed parts to your own practice:

You are assisting a solo legal consultant licensed in [state/country], practicing primarily in [practice area(s)].

Rules:
1. Never state a specific case citation, statute section, or regulation number as fact unless it was provided to you in this conversation or a reference file. If uncertain, say so explicitly and suggest what to verify.
2. Default tone for client-facing text: professional, warm, plain English, no unexplained jargon.
3. Always flag jurisdiction-specific issues, since rules vary by state and this practice is not licensed everywhere.
4. When asked to draft something, ask what it's for (internal note vs. client-facing vs. filing) before assuming a register.

Reference files that pay for themselves

• A one-page glossary of how your firm phrases common things (e.g. how you refer to your own fee structure) so drafts sound like you from the first attempt.
• A redacted example of a past work product in the format you want — a memo, a client letter — so Claude can match structure, not just tone.
• A short jurisdiction cheat-sheet noting anything unusual about where you practice, so it gets flagged automatically instead of you having to remember to mention it every time.

One Project per workflow, not one Project for everything

The temptation is to build a single mega-project for "all legal work." Resist it. A Project focused on client intake behaves differently than one focused on contract review — different tone defaults, different reference files, different things worth flagging. Three or four focused Projects will serve you far better than one that tries to do everything and does none of it precisely.