Prompt Templates

Keep the instructions you retype in a library, and append or insert them without typing them again.

Everyone has a paragraph they retype. Don't add comments explaining what the code does. Run the tests before you tell me it works. Match the existing file's style.

Prompt Templates hold those paragraphs once, and put them into your prompts two different ways.

The prompt template library in settings

Build the library

Go to Settings → AI → Prompt Templates. Add, edit, hide, or remove templates from that one page — each is a name and a block of instructions.

Hiding a template keeps it around without cluttering the picker, which is the right move for something you use twice a year.

Two ways to use one

Append it to every message

Turn a template on for a terminal and it's appended to what you send from that terminal. You choose exactly which templates are enabled, per terminal — a reviewer agent can carry your review checklist while the builder next to it doesn't.

This is the one for standing rules: house style, test discipline, what not to touch.

Insert it at the cursor

In Agent Input, type @ and open the Templates tab in the mention picker. Pick a template and it's inserted at the cursor, inline, as part of the message you're writing.

Inserting a template from the @ mention picker

This is the one for a block you need this time — a bug report skeleton, a release checklist, the shape of a commit message.

The picker's other tabs put files, agents, and open terminals into the same prompt — see Linked Terminals.

Templates worth writing first

TemplateRoughly
House style"Match the surrounding file. No new dependencies without saying why."
Verify before claiming"Run the tests and paste the output. Don't say it works if you didn't run it."
Review pass"Look for correctness first, then naming, then structure. Quote line numbers."
Explain, don't apply"Show me the diff you would make and wait. Don't edit files yet."

Next