Prompt templates

A template is a prompt that already works, for a task that comes up repeatedly. The library covers writing, coding, marketing, trading, SEO, business, and learning.

Using one

Click Templates in the message box, search, and pick one. It drops into the composer as editable text — it is not sent for you, and it is not locked. Fill in the bracketed parts, delete the parts that do not apply, and send it.

Every template also has a public page with the full prompt on it, so you can read one before you use it. They are linked from the templates index.

Why they are long

A good prompt is specific about the output, not just the topic. The templates here state the format, the length, the audience, and what to leave out — because that is what makes the difference between a usable draft and something you rewrite from scratch.

If a template feels over-specified for your case, cut it down. That is faster than building one up from a one-line question, and it is why they are handed to you as text rather than run for you.

Writing your own

Save any prompt you have had to retype. The test of a good template is whether it still works when a colleague uses it without asking you what you meant.

Two things worth putting in every one:

1. The shape of the answer you want. "Three options, one sentence each" beats

"some options".

1. What not to do. "No preamble", "do not explain the code, just fix it", "do not

suggest tools I did not ask about".

Templates and personas together

They solve different halves of the same problem. A persona is how to behave across a whole conversation; a template is what to do in one message. A code review conversation is best as the Code Reviewer persona plus whatever you paste. A monthly report is best as a template you fill in.