Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Customisable Prompts

Every tone in Patera (built-in or custom) is structured as three editable prompt fields. Rewrite any of them. Save. The AI will draft against your wording the next time you hit generate.

This is the level of control you usually need your own backend to get.

The three fields

Open the tone editor via the cog next to the tone selector in AI Actions. The modal is titled Response Settings. Pick a tone in its list and you'll see three sections:

Hook

"How the reply opens: angle, stance, framing."

The Hook governs the opening move of the reply. Is it a question? A counter? A wry observation? A direct affirmation? Most of a reply's perceived voice lives in its first six words. The Hook is where you write the rules for those six words.

Shape

"Body length, sentence structure, voice."

The Shape governs the body. Length caps. Sentence patterns to prefer or avoid. Tense and person. Whether to repeat key phrasing from the parent tweet or never echo it. Whether to admit uncertainty or stay confident.

Export

"Output rules: emoji policy, hashtag policy, char limit."

The Export governs the final shape of the string the model returns. Emoji allowed? Hashtags? Markdown? Trailing punctuation? Hard char limit? The Export is where you pin all the formatting rules.

How sophisticated can these get?

Engagement Farmer's shipping Hook runs roughly 1,900 words. Per-word constraint logic: if the word "wild" is about to be used, twelve separate conditions (a through l) need to evaluate true first. You can write prompts at that level of specificity. Or you can write a one-line Hook like "open with a question, never with agreement" and ship.

There's no upper bound. Whatever you can fit in a textarea, you can put in a tone.

Other things you can customise

The tone editor also exposes:

Execute All interval

The min/max delay (in seconds, 0-30) between posts when you hit Execute All on a queue. Sliders plus numeric inputs. The actual delay is sampled randomly from this range for each post. A wider range looks more human; a tighter range drains the queue faster. The same bounds govern every dispatch path that drains the Execute Queue.

Per-tone label and ID

You can rename any tone (24-char limit). Renaming a built-in is fine. Your custom label sticks; the underlying ID stays so prompt history maps correctly.

Reset to default

Every built-in tone has a Reset to default button. It only appears once you've changed the label or one of the prompts and one click restores all three fields plus the label to the shipping version. So if you've been iterating on Engagement Farmer's Hook for a week and want the original back, the button is there. Built-in tones can be edited and reset but never deleted. Custom tones have no default to reset to, so they show a Delete button instead. For the full list of built-ins and how custom tones and the Random meta-tone fit together, see Tones.

What is stored where

All customisation lives in localStorage under patera-tones-v1. Wiping browser data wipes your prompts (built-ins auto-restore on next load; custom tones do not). Cross-device sync is not yet available.