Persona keeps your output aligned to a consistent editorial voice instead of relying on one-off prompt phrasing.
What Persona Does
Use persona when you need:
- Stable tone across repeated runs.
- A recognizable editorial voice.
- Better consistency between writers, editors, and campaigns.
- A final publish-time check that the article still sounds like the intended voice.
Where Teams Configure It
Persona is configured in Studio and then reused by workflows and campaigns.
Typical flow:
- Create or open a persona in Studio.
- Add direct configuration such as tone, style, domains, and editorial preferences.
- Optionally use Extract Persona from a long writing sample.
- Save the persona and select it in a workflow or campaign.
Extract Persona From Writing
The extraction tool is designed to take a large sample of existing writing and infer as much of the persona configuration as it can safely justify.
It is best at filling:
- Description
- Base style
- Archetype
- Knowledge domains
- Characteristics
- Capabilities
- Editorial preferences
- Some background specialization fields
It stays conservative for biography-style fields such as:
- Origin story
- Personal history
- Influences that are not clearly evidenced
That means extraction is best-effort completion, not unrestricted invention.
How Persona Is Applied During Content Creation
Persona is not only a final rewrite step.
Current behavior is:
- Writer applies persona guidance while generating the draft.
- Editor reinforces persona during editing.
- An optional dedicated
personastep can do an explicit personalization pass when your workflow includes it.
Practical meaning:
- Persona can shape the draft as it is written.
- The dedicated persona step is optional, not the only way persona is used.
Campaigns and Persona
Campaigns can enable persona and select a persona for the run.
That lets campaign-driven article generation reuse the same voice across related topics without manually re-describing the style every time.
Final Persona Evaluation
Publish owns the final article-level persona verdict.
At publish time, PromptPress stores:
metadata.persona_evaluation_summary- publish processing status for persona review
Current evaluation model is:
- workflow steps can record persona alignment signals
- publish is the canonical final summary the UI should trust
What Good Persona Usage Looks Like
- One clear persona per workflow or campaign.
- Distinct editorial intent between personas.
- Real writing samples for extraction instead of short fragments.
- Final human review before publish for high-stakes content.
Common Anti-Patterns
- Creating too many overlapping personas that differ only slightly.
- Using persona as a substitute for factual review.
- Expecting extraction to invent biography details safely.
- Assuming a high persona score means the article is factually correct.