Inicio - Documentación - POM AI - 08 Prompts - Prompt recipes for writing

Prompt recipes for writing

Reusable clauses rather than whole prompts. Each one solves a specific, recurring problem with generated copy; combine two or three into a prompt of your own.

For complete worked prompts per tool, see Prompt recipes for better writing.

Clauses that fix a generic result

The reader has already decided to buy and is comparing two suppliers.

The reader has heard the term and does not know whether it applies to them.

The reader inherited this system from someone who has left and has no documentation.

Naming the reader's situation is the highest-value clause available. Two prompts identical except for this line produce genuinely different output.

Clauses that remove standard filler

Do not include a history or background section.

Do not open by restating the title.

No concluding summary.

Do not explain what <term> is; the reader knows.

Say each thing once.

Generated content has predictable habits. One clause removes each, and they compose well.

Clauses that protect you

Do not invent company history, size, founding date or client names.

Do not claim any certification, accreditation or award.

Do not compare against named competitors.

Do not state prices, delivery times or availability.

Do not make health, financial or safety claims.

The first belongs in almost every About, Services and company-page prompt. It is where generated copy most reliably invents a track record.

Standing rules like these belong in the relevant tone, vocabulary or restrictions profile field, so writing tools apply them automatically. Keep the prompt for what is specific to one piece of work.

Clauses that shape structure

Prefer fewer, deeper sections.

Structure it as an argument that builds to one recommendation, not as a list.

Each section should answer one question.

Follow every claim immediately with the evidence for it.

Must include a section on <topic>.

These matter most in the outline-driven tools, where the plan decides the article. See Prepare a long-form outline.

Clauses for the paragraph assistant

Their meaning depends on the mode you select.

Continue mode

Now explain the two options and when each applies.

Cover what this does not do, honestly.

Move from the explanation to what the reader should do next.

Rewrite mode

Remove the marketing language and state plainly what this does. Keep every figure and product name.

Lead with the conclusion, then the supporting detail.

Split the long sentences. Do not add or remove information.

Use active voice and name who does what.

Any destructive mode

Keep every figure, date and product name exactly as written.

That last clause measurably reduces the detail drift that rewriting causes. See Rewrite text.

Clauses for register

Describe behaviour, not adjectives:

Remove exclamation marks and superlatives; state facts plainly.

Address the reader as "you"; short sentences, everyday words.

The way a specialist explains something to a colleague, not the way a brochure sells it.

Make direct statements; no "we believe" or "we think".

Note that overall tone is a form control — the copywriting style selector — and the control wins. Use these to adjust one passage, not to fight the selector.

Combining them

A working prompt is usually one situation clause, one or two structure clauses and one or two exclusions:

Article on <topic>. Reader currently does this in-house and is deciding whether to outsource. Must cover cost, what they hand over, and what stays theirs. Prefer fewer, deeper sections. No history section, and do not claim any certification.

Four sentences, well inside every limit in the plugin.

Where to keep them

Save the clauses your team should always use as a template under Texts generator, which offers it across all the writing tools. See Create a prompt template.

Put the ones that should apply to everything in the matching structured profile field instead, and stop repeating them.