How I structured 50 legal AI prompts so they are actually reusable

I do a lot of contract drafting, NDA review, and client communication work. Started using AI for it about a year ago. The dirty secret: the quality gap between a bad prompt and a good one in legal work is enormous.

A bad prompt produces generic legalese that needs total rewriting. A good prompt produces a usable first draft. The difference is almost never the model — it is the structure of the ask.

Here is what I figured out.

The core pattern: role + constraints + output format

Every legal prompt that works for me has three parts:

[ROLE]: You are a [practice area] attorney reviewing [document type].
[CONSTRAINTS]: Jurisdiction: [STATE/COUNTRY]. Client type: [INDIVIDUAL/BUSINESS].
Assume: [KEY ASSUMPTION]. Do not: [THING TO AVOID].
[FORMAT]: Output a [FORMAT] covering [SPECIFIC SCOPE]. 
Flag any [RISK TYPE] with a one-sentence plain-English explanation.

The "do not" line does most of the work. Without it, models default to maximally hedged, disclaimer-heavy output. Telling the model what to skip sharpens the response significantly.

The 50 prompts by category

Client intake (8 prompts)

• Conflict check memo (takes client name + matter description, flags potential conflicts)
• Non-engagement letter (3 variants: conflict, scope mismatch, capacity)
• Retainer clause explainer (translates fee language into plain English for the client)
• Initial consultation summary

Legal research (9 prompts)

• Case summary (input: raw case text, output: issue/holding/reasoning in 200 words)
• Jurisdiction comparison (same legal question across two states)
• Deposition outline generator
• Statute plain-English summary
• Counter-argument spotter (reads your draft argument, surfaces the opposing view)

Drafting (10 prompts)

• NDA redline reviewer (flags one-sided clauses with explanations)
• Contract summary (for clients who will not read the full agreement)
• Settlement agreement first draft
• Interrogatory response set
• Cease and desist (3 tones: firm, aggressive, de-escalating)

Client communication (8 prompts)

• Case status update email
• Bad news delivery (structure: fact → context → options → next step)
• Fee dispute response
• Client boundary-setting email

Practice management (15 prompts)

• Google Business Profile bio
• LinkedIn post series (5 prompts, one per week of content)
• SOP draft (input: process description, output: numbered SOP with decision points)
• CLE tracker summary
• Year-end business review

The most useful single prompt

The contract summary for clients:

You are a [PRACTICE AREA] attorney. A client has asked you to explain this contract 
in plain English. They are [SOPHISTICATED/NON-SOPHISTICATED]. 
Do not use legal jargon. Do not add hedges or disclaimers — 
I will add those separately. 

Summarise the following sections in 2-3 sentences each:
- Parties and purpose
- Key obligations (each party)
- Payment terms
- Termination triggers
- Anything unusual or one-sided

Flag any clause that a [CLIENT TYPE] should negotiate before signing, 
with a one-sentence plain-English reason.

[PASTE CONTRACT HERE]

Clients read this. They do not read a 40-page agreement.

One important note

None of this replaces legal judgment. Every output needs attorney review before it goes anywhere. The prompts are for generating usable first drafts, not final work product.

Full pack of 50 prompts (PDF + Markdown, copy-paste ready with bracket placeholders): https://pirateprentice.gumroad.com/l/sklcrpo ($29 one-time).

If you build legal tech or use AI for your own legal paperwork — what prompts have you found that actually work? Always looking for patterns I have not tried.