Skip to content
Prompt Alchemy Lab
Example system

A reusable brand-voice prompt system for client content

A global Tone & Voice Rules block plus per-client Voice Profiles, assembled into one Blog Post Generator — update the shared rules once and every client's content inherits it.

Project Map · Client Brand-Voice System
Tone & Voice Rules Formatting Rules {{client}} Voice Profile Blog Post Generator
{{client}} {{topic}} {{audience}} {{word_count}}
Assemble copy into: ChatGPT Claude Gemini

See it work

Fill the variables with one real scenario — the system assembles into a paste-ready prompt.

Variables
{{client}}
= Northwind Logistics
{{topic}}
= cutting freight costs without slowing delivery
{{audience}}
= operations leads at mid-market shippers
{{word_count}}
= 900
Assembled prompt · the whole system
## Tone & Voice Rules

You are writing in a professional, human voice, never robotic, never salesy. Default to active voice and short-to-medium sentences (average 12-18 words); vary rhythm so the copy does not read like a template. Use contractions where natural (it's, we're, don't) unless the client's Voice Profile below says otherwise. Avoid corporate filler: no "in today's fast-paced world," no "unlock," "leverage," "seamless," "game-changing," or "revolutionize" unless the client explicitly uses that word themselves. Prefer concrete nouns and verbs over abstractions; show the reader something real before telling them an opinion about it. Do not stack hedges like "might," "could," and "perhaps" in the same sentence; take a position. One idea per paragraph, two to four sentences per paragraph for web reading. When in doubt between clever and clear, choose clear. This block sets the floor for every piece written for every client; a client's own Voice Profile only adjusts tone and vocabulary on top of it, and never overrides the ban on filler language.

## Formatting Rules

Structure every piece so a skimmer gets the gist in ten seconds and a reader gets full value within the 900 allotted. Open with a one-sentence hook that states the concrete benefit, never a throat-clearing intro like "In this article, we will discuss." Use H2s every 150-250 words to break up the piece; add an H3 only when an H2 section genuinely branches into sub-points. Use bullet lists for anything that is a set of parallel items (steps, features, criteria), never for a narrative argument. Bold sparingly: only the one phrase per paragraph a skimming reader would actually want. No emoji, no exclamation-heavy copy, no rhetorical questions as section headers. Close with a short, concrete next step, not a generic summary restating the intro. Keep paragraphs under four sentences. This block is identical for every client and every post; only the topic and word count change, so a reader can move between clients' content without noticing a different production process.

## Northwind Logistics Voice Profile

This is Northwind Logistics's specific voice, layered on top of the global Tone & Voice Rules; it never contradicts the ban on filler language, it only tunes register and vocabulary. Audience: operations leads at mid-market shippers. Describe here, in two or three concrete sentences, how Northwind Logistics actually sounds: formality level (for example "casual but credible, like a knowledgeable friend" versus "precise and technical, no small talk"), three to five words or phrases Northwind Logistics uses often and three to five the brand avoids, and one real example sentence pulled from Northwind Logistics's own published content as a north star. Note any hard constraints: regulatory language requirements, terms legal has banned, a house style on numerals or capitalization, or a preferred sign-off. If Northwind Logistics sells in more than one register, specify which register this project uses. Keep this block short and specific: it should read like brand-voice notes a new freelance writer would actually be handed on day one, not a mission statement.

## Blog Post Generator

Using the Tone & Voice Rules, Formatting Rules, and Northwind Logistics Voice Profile above as binding constraints, write a complete blog post for Northwind Logistics on the topic: cutting freight costs without slowing delivery. Audience: operations leads at mid-market shippers. Target length: 900 words, plus or minus ten percent. Before writing, silently plan a three-to-five point outline that supports one clear takeaway; do not show the outline, show only the finished post. Include a title under 65 characters with no clickbait, a one-sentence hook opening, body sections with H2s per the Formatting Rules, and a closing call-to-action appropriate to Northwind Logistics's funnel stage for this topic. Cite no statistic you cannot plausibly attribute; if you need a number and have no real source, describe the trend qualitatively instead of inventing a figure. When Northwind Logistics's Voice Profile conflicts with a generic best practice, the Voice Profile wins. Output the post only, no preamble like "Here's your blog post," and no notes after it.
Blog Post Generator — example output
Three Levers That Cut Freight Spend Without Slower Delivery

Freight costs climbed for most mid-market shippers this year, and the usual reflex — squeeze carriers on rate — barely moved the number. The bigger wins were structural: consolidating LTL shipments, renegotiating accessorials, and routing by lane instead of by habit. Here's how each one works, and which to try first.

Example output — illustrative. PAL builds the prompt; you paste it into ChatGPT, Claude, or Gemini to generate.

What’s inside this system

Every block below is the real prompt text — read it, expand it, copy it. No signup required.

Tone & Voice Rules

Global

Foundational block — no dependencies.

You are writing in a professional, human voice, never robotic, never salesy. Default to active voice and short-to-medium sentences (average 12-18 words); vary rhythm so the copy does not read like a template. Use contractions where natural (it's, we're, don't) unless the client's Voice Profile below says otherwise. Avoid corporate filler: no "in today's fast-paced world," no "unlock," "leverage," "seamless," "game-changing," or "revolutionize" unless the client explicitly uses that word themselves. Prefer concrete nouns and verbs over abstractions; show the reader something real before telling them an opinion about it. Do not stack hedges like "might," "could," and "perhaps" in the same sentence; take a position. One idea per paragraph, two to four sentences per paragraph for web reading. When in doubt between clever and clear, choose clear. This block sets the floor for every piece written for every client; a client's own Voice Profile only adjusts tone and vocabulary on top of it, and never overrides the ban on filler language.

Formatting Rules

Global

Foundational block — no dependencies.

Structure every piece so a skimmer gets the gist in ten seconds and a reader gets full value within the {{word_count}} allotted. Open with a one-sentence hook that states the concrete benefit, never a throat-clearing intro like "In this article, we will discuss." Use H2s every 150-250 words to break up the piece; add an H3 only when an H2 section genuinely branches into sub-points. Use bullet lists for anything that is a set of parallel items (steps, features, criteria), never for a narrative argument. Bold sparingly: only the one phrase per paragraph a skimming reader would actually want. No emoji, no exclamation-heavy copy, no rhetorical questions as section headers. Close with a short, concrete next step, not a generic summary restating the intro. Keep paragraphs under four sentences. This block is identical for every client and every post; only the topic and word count change, so a reader can move between clients' content without noticing a different production process.

{{client}} Voice Profile

Project

Foundational block — no dependencies.

This is {{client}}'s specific voice, layered on top of the global Tone & Voice Rules; it never contradicts the ban on filler language, it only tunes register and vocabulary. Audience: {{audience}}. Describe here, in two or three concrete sentences, how {{client}} actually sounds: formality level (for example "casual but credible, like a knowledgeable friend" versus "precise and technical, no small talk"), three to five words or phrases {{client}} uses often and three to five the brand avoids, and one real example sentence pulled from {{client}}'s own published content as a north star. Note any hard constraints: regulatory language requirements, terms legal has banned, a house style on numerals or capitalization, or a preferred sign-off. If {{client}} sells in more than one register, specify which register this project uses. Keep this block short and specific: it should read like brand-voice notes a new freelance writer would actually be handed on day one, not a mission statement.

Blog Post Generator

Project

Uses: Tone & Voice Rules, Formatting Rules, {{client}} Voice Profile

Using the Tone & Voice Rules, Formatting Rules, and {{client}} Voice Profile above as binding constraints, write a complete blog post for {{client}} on the topic: {{topic}}. Audience: {{audience}}. Target length: {{word_count}} words, plus or minus ten percent. Before writing, silently plan a three-to-five point outline that supports one clear takeaway; do not show the outline, show only the finished post. Include a title under 65 characters with no clickbait, a one-sentence hook opening, body sections with H2s per the Formatting Rules, and a closing call-to-action appropriate to {{client}}'s funnel stage for this topic. Cite no statistic you cannot plausibly attribute; if you need a number and have no real source, describe the trend qualitatively instead of inventing a figure. When {{client}}'s Voice Profile conflicts with a generic best practice, the Voice Profile wins. Output the post only, no preamble like "Here's your blog post," and no notes after it.

Copy the whole system

Every block above, assembled in build order — ready to paste into a new project in ChatGPT, Claude, or Gemini.

How the reuse works

Tone & Voice Rules and Formatting Rules are global blocks: write them once, and every client's Blog Post Generator inherits them automatically. Tighten a rule — ban a new piece of jargon, or shorten the average sentence length — in Tone & Voice Rules, and every client's content picks up the change the next time you generate. You never touch the four, ten, or forty client-specific generators individually.

Each client only needs its own {{client}} Voice Profile: the handful of sentences that make one client sound like themselves and not like your other twelve clients. Because Voice Profile is a separate, small, project-scoped block, onboarding a new client means writing one short profile, not rebuilding your whole prompt from scratch.

Blog Post Generator is the only block that actually produces a finished post, and it does so by pulling in the other three through USES. That is the whole reuse story in one diagram: two shared foundations, one client-specific layer, one generator that assembles them into paste-ready output. The same structure works whether the top-level context is a client or one of your own projects — the variables treat both the same.

More example systems

Create an account to clone this system

Sign up to clone this system and every other example system straight into your own workspace.

Get started