Custom templates

A template is a saved instruction that replaces the built-in register block for one kind of document: a release note, a customer apology, a weekly update.

Pro keeps up to 12. Free and anonymous have the feature off entirely — the gate is a plan entitlement, not a hidden route.

Limits

Name	60 characters
Instruction	1,500 characters
Templates per account	12 (Pro)

The instruction cap is not arbitrary. A template is rendered into the prompt in place of the register instruction; a long one crowds the correctness sections below it, the same failure mode the voice profile token budget guards against.

Writing one that works

Describe the shape, not the content.

Write a great release note that gets users excited about the new feature and highlights all the benefits in a compelling way.

One sentence saying what changed. One saying who it affects. A short list of what to do differently, if anything. No preamble, no closing line.

The first prompts for enthusiasm and gets tells. The second describes a structure and gets a release note.

A template does not turn off the fact rule. It cannot instruct the model to add a claim your draft does not contain.

API

Method	Path	Does
GET	/api/templates	List your templates
POST	/api/templates	Create one
PATCH	/api/templates/:id	Update name or instruction
DELETE	/api/templates/:id	Delete

Then send its id as templateId on a rewrite. register is still required — it is what the server falls back to if the template cannot be resolved, so a rewrite still happens rather than erroring.