AI Prompts settings — webhouse.app Docs

Customise the prompt templates the CMS uses for field generation, SEO optimisation, translation, and other AI features — per site.

Where it is

Settings → AI Prompts (/admin/settings?tab=prompts).

The CMS uses curated prompt templates for every AI-backed feature — generating a field, rewriting, translating, scoring SEO, optimising for GEO, summarising, extracting metadata. This tab lets you override the defaults on a per-site basis so the output matches your site's needs without having to build a custom agent.

Prompt categories

The tab lists every prompt slot the CMS exposes, grouped by purpose:

Content generation

Field generate — fills a single field given the rest of the document
Field rewrite — rewrites a field (shorter, longer, formal, casual, etc.)
Document generate — generates a complete document from a title + brief
Interactive generate — AI-builds a standalone HTML widget

Optimisation

SEO optimise — generates meta title, description, keywords, JSON-LD for a document
GEO optimise — restructures content to be answer-first, adds question headers, citations, statistics
Alt-text generate — fills alt for an image given its caption and filename

Translation

Document translate — document-level translation to a target locale
Field translate — single-field translation (used for UI strings in globals)

Research

Content research — gathers live web sources via web_search for a draft
Citation format — formats an external URL into a proper citation block

Moderation

Proofread — grammar, style, tone corrections (the inline proofreader)
Moderation check — flags potentially harmful content

What a prompt looks like

Each prompt has three parts:

System — fixed instructions about role, tone, output format. Seldom needs changing.
User template — the variable part, with placeholder tokens like {{field}}, {{title}}, {{brand_voice}}, {{locale}}, {{document_json}}
Example output — a worked example the model can anchor on (optional but helps)

Brand Voice is automatically injected as {{brand_voice}}; you don't need to duplicate it into every prompt.

Overriding a prompt

Find the prompt in the list. Each row shows the slot name and the current source (default or custom).
Click Edit.
Write your override. The editor shows the default text as a reference and highlights placeholder tokens.
Test runs the prompt against a sample document with your override. Verify the output looks right.
Save — takes effect immediately for all future AI calls on this site.

Overrides are stored in _data/prompts.json. They're included in site beams (so exported sites carry their prompt customisation).

Reverting

Each row has a Revert to default button that drops the override. The default text is shipped with the CMS and updated with each release — reverting means you follow any improvements the @webhouse/cms team makes.

When to override

Reach for this tab when:

A specific prompt is consistently producing output that misses your brand
You want to inject domain-specific constraints (e.g. "always include the product name", "avoid these legal phrases")
You're A/B testing tone strategies between two sites
You want to translate prompts themselves to match a non-English editor team

Don't override when you can solve the problem via Brand Voice — that's simpler, cheaper, and propagates to every feature automatically.