Saved Styles
Your presets, not the model's
Tone, format, and constraints are repeatable. Saved Styles let users define a reusable preset — "shipping-style update", "executive memo", "casual reply" — and apply it to any new task with a single click. Each style is an editable definition, not a magic phrase.
Framing
The problem
Tone and format have to be re-described every run; team consistency depends on memory.
The pattern
Let users define and save a style as a first-class object, applied to any task with one click.
Why chat breaks here
Chat treats every prompt as fresh — repeating "shipping-tone, 3 bullets, no jargon" eight times a day is the failure mode.
Risks
Style sprawl can confuse new users; weak naming makes presets unreadable.
Avoid when
The product has only one author or one consistent style and presets add no leverage.
Use when
Teams or solo authors repeat the same tone and format across many short tasks.
DOPE evaluation
- Directability
- Styles are first-class objects: edit a rule, fork a variant, share across the workspace — one click swaps the entire register of the output
- Observability
- The active style card sits beside the task with its rules in plain sight ("bullet points only, no marketing voice") — the constraints in force are readable, not remembered
- Predictability
- A style is a stored definition, not a magic phrase — applying "Shipping update" yields the same register on the eighth run as on the first
- Explainability
- Each card declares its rules as inspectable plain language, so why the output came out terse and bulleted traces to a rule you can point at
In the wild
- Notion AI Custom Instructions (Notion) — Workspace-saved voice and brand prefs the agent uses across all generations, plus per-team prompt templates. The style is infrastructure, not a memorised phrase.
- Grammarly Brand Tones (Grammarly) — Custom style guides and brand tone profiles, multiple profiles assignable to teams or groups. Enterprise-grade saved styles.
- Writer.com Voice (Writer) — Upload samples → derive a voice profile → apply across the team. Brand-voice as a first-class object, not a per-prompt instruction.
FAQ
When should I use the Saved Styles pattern?
Teams or solo authors repeat the same tone and format across many short tasks.
When should I avoid the Saved Styles pattern?
The product has only one author or one consistent style and presets add no leverage.
What problem does Saved Styles solve?
Tone and format have to be re-described every run; team consistency depends on memory.
Why is chat the wrong fit for this?
Chat treats every prompt as fresh — repeating "shipping-tone, 3 bullets, no jargon" eight times a day is the failure mode.
Related patterns
- Extends: Persona Switcher — A style with refusal behaviour becomes a persona. Persona is the full contract; Saved Styles is the lighter, faster one.
- Often paired with: Templates — Templates fix the structure; Styles fix the voice. A repeatable output needs both.
- Alternative to: Tone of Voice — Direct manipulation in the moment vs reusable preset for the team. Live dial vs saved object.