Starting prompt library

Deliberately a small library. A hundred prompts is a worse resource than six you understand well enough to change.

Why prompt lists usually disappoint

A prompt written for someone else's business produces output for someone else's business. What transfers is the structure: role, context, audience, examples, constraints, and what to refuse.

The six patterns worth having

The recurring client update

Context on the matter or job, the audience's knowledge level, what changed, what happens next, and the tone your business actually uses.

The chasing sequence

Three escalating requests for the same missing thing, polite throughout, each usable without the previous one being read.

The long-document question set

Named questions rather than “summarise”, with a requirement to cite a location for each answer.

The notes-to-report pattern

De-identified notes in, a structure the recipient expects out, with gaps flagged rather than filled in.

The quote or scope

Your inclusions, your exclusions, your terms, and the sentence that prevents the argument in month three.

The complaint response

Acknowledge, state what happened, state what changes, and nothing else. Written from facts you supply, not invented.

Turning a pattern into something reusable

A prompt you retype is a prompt you’ll stop using. Once one works, it belongs in a held setup — reusable setups covers that, with the tool-specific mechanics under Projects and custom setups.

Before you paste in an example

Examples are the most powerful part of any brief and the easiest place to leak client information. De-identify them once, properly, and reuse the clean versions.

Why this is short on purpose

Long prompt libraries teach copying. A team with fifty prompts has fifty things to search through and no way to tell which one is nearly right; a team with six and an understanding of why they work adapts them to the seventh job themselves.

Each one here follows the same structure, which is the actual lesson: what the document is for, who reads it, the three or four facts only you hold, and a good past example to match.

How to turn one of these into your own

Take the closest one and run it on a job you did last week, where you already know what good looks like.
Compare the output to what you actually sent. The gap is the missing context, not a prompting flaw.
Add the two or three facts that were missing, and attach the example you sent.
When it produces something you'd send, move it into a reusable setup so nobody types it again — see reusable setups.

Nothing in a shared prompt or setup should contain client information. The never list applies to prompts as much as to documents, and shared prompts are the place it gets forgotten.

If you'd rather this was done on your real documents than on examples, that's a workflow build.

Start an enquiry

Get a training plan built for your business. Nine questions about how your business actually runs. You get a plan ordered for your work, a reading on where you're exposed, and one clear place to start. No account needed. Build your plan.