Create a prompt template

Creating a template takes a minute. The value comes from doing it at the right moment: immediately after a prompt has produced a good result, while you still know why it worked.

Where

Settings → POM AI → Prompt templates, available to administrators and editors. The page lists your saved templates and, below them, a form headed Add new template.

The three fields

Template title. How it appears in the dropdown inside the tools. Make it describe the job — Article skeleton, House rules — exclusions, Product image conventions — rather than being clever. Several people will choose from this list without opening the template.

Prompt text. Up to 4,000 characters. A counter below the field shows how many remain and turns the submit button off if you exceed it.

Contexts. Tick at least one:

• Post writer
• Texts generator
• Landing generator
• Full texts copywriting
• Image generator
• Image improver

The Landing generator context is retained for compatibility with existing templates, but no active tool currently consumes it.

Then select Save template. All three fields are required; saving with a missing title, empty prompt or no context returns an error asking you to complete them.

Choosing contexts

The matching is deliberately broad, so choose the narrowest context that is still correct:

• Save under Texts generator for anything that should appear across the available writing tools — it is also offered in the post writer and site-wide copy tool.
• Save under Post writer for something that only makes sense for articles.
• Save under Image generator for image conventions; it is also offered in the image enhancer.
• Save under Image improver for enhancement-only instructions, such as prompts that reference Image #2.

Ticking every context to be safe produces cluttered dropdowns and templates offered where they make no sense.

Writing the prompt text

Templates append to whatever is in the field, so write them as a starting point to be completed, not as a finished prompt.

Leave visible gaps. A line ending Must cover: … invites completion. A polished paragraph invites being used unedited.

Include the parts people forget. Exclusions are the classic case: Do not invent company history, size or founding date is the clause everyone omits and everyone needs.

Leave out what is automatic. Your business, tone, audience and language are already sent from the business description. Restating them wastes input and can conflict.

Leave out anything a control handles. Length, copywriting style, aspect ratio and quality profile are form controls, and the control wins.

Three templates worth having

House rules — context Texts generator

Do not invent company history, size, founding date or client names. Do not compare against named competitors. Do not use urgency or scarcity language. Refer to customers as "clients".

Article skeleton — context Post writer

Reader: … Goal: the reader should … Must cover: … Do not include: history or background sections.

Image conventions — context Image generator

Palette: warm terracotta, off-white and deep grey. Generous negative space. No text or lettering in the image. No visible logos.

Never put in a template

Templates are visible to everyone who can use the tools. Do not save:

• customer names or data;
• credentials of any kind;
• unpublished pricing, margins or strategy;
• anything under a confidentiality obligation.

See Keep sensitive information out of prompts.

After saving

The template appears immediately in the saved list, showing its title, its contexts and a short preview of the prompt.

Test it: open a tool whose context matches, select it from the dropdown, and confirm the right text lands in the prompt field. The status line confirms the template was appended.

A habit worth forming

The best moment to create a template is the moment a prompt works. Not later — later means someone else rediscovers the same wording by trial and error, paying credits to do it.

When you get a result you are pleased with, copy the prompt, save it as a template with the contexts where it applies, and tell the team it exists.

Next

• Use saved prompt templates — how they behave in the tools.
• Maintain prompt templates — keeping the list useful.