Knowledge card L3 · Workflows informational

Keep a Voice Guide in the Context for Long-Form Writing

What it is

Pinning a short, concrete voice guide — do's, don'ts, and two sample sentences — into the context so every part of a long piece sounds like the same author.

voice as a standing inputBrief + audience3Voice guide (always present)2Draft sections1
A short voice guide keeps every section sounding like one author.

Why it works

Over a long draft, tone drifts. A standing voice guide gives Claude a fixed reference to check every section against, which is far more reliable than re-describing the tone each time or fixing it in editing.

When to use it

Multi-section content that must hold a consistent voice: brand articles, documentation, a series. Best when several pieces should sound related.

When not to use it

One-off internal notes where voice doesn't matter, or creative work where you want the tone to shift deliberately.

Prompt

Write in this voice, and keep it consistent across every section:

Voice: <3-4 do's>. Avoid: <3-4 don'ts>.
Sounds like: "<sample sentence 1>" / "<sample sentence 2>".

Now draft: <section>.

Example

With a guide that says 'plain, concrete, no hype; avoid "leverage" and "seamless"', a six-section guide reads as one steady voice instead of six slightly different ones.

Advanced version

Turn the voice guide into a Claude Project instruction so it applies to every chat automatically — the same idea as a shared style guide for a team.

Common mistakes

  • Describing voice with adjectives only; give sample sentences Claude can pattern-match.
  • Re-explaining the tone in every message and getting a slightly different result each time.
  • Forgetting to forbid your specific pet-peeve words, so they creep back in.

Related