Building a Brand Voice Gem You Reuse Across Every Piece of Content
If you've ever pasted the same three sentences about your brand's tone into a Gemini chat for the fifth time this month, tone description is the wrong thing to be re-typing. A Gem does that description once, permanently, and then applies it every time you open it, whether you're writing a product email, a social caption, or a customer apology.
The distinction that matters here is between describing a voice and encoding one. Describing it is what you do in a regular chat: "keep it friendly but professional, not too corporate." Encoding it means giving Gemini actual examples of your best writing, explicit rules about what to avoid, and enough structure that a new team member could read the Gem's instructions and understand your brand's voice almost as well as you do.
Note
This builds on the general approach in setting up a Gem you'll actually reuse. This article applies that same discipline specifically to brand voice, which is one of the highest-value uses of a Gem because the same voice gets applied across dozens of different content types.
What goes in the instructions versus the Knowledge files
A Gem has two places to put information: the instructions box, where you write direct behavioral rules, and the Knowledge files, where you attach reference material Gemini can pull from. For a brand voice Gem, the split should be deliberate.
The instructions should hold the rules: sentence length preferences, words to avoid, how formal or casual to default to, how the brand handles humor, how it opens and closes different content types. The Knowledge files should hold the evidence: three or four pieces of writing that actually represent the voice at its best, so Gemini has real examples to pattern-match against instead of only abstract adjectives.
This split matters because adjectives alone are weak signal. "Friendly but professional" describes a huge range of actual writing. A real paragraph that's friendly but professional, that you're personally proud of, narrows that range enormously, and Gemini uses it as a reference the same way a new hire would use a style guide's examples section, not just its rules section.
A full worked template
Here's what the instructions field of a real brand voice Gem might look like, for an invented mid-size B2B project management software company called Ridgeline PM, positioned as the plain-spoken alternative to bloated enterprise tools:
You are writing in the voice of Ridgeline PM, a project management software company. Our audience is operations and project managers at mid-size companies, people who are busy and skeptical of marketing fluff, and who have usually been burned by a more complicated tool before.
Voice rules: Write like a knowledgeable colleague, not a marketer. Avoid hype words that promise more than the sentence delivers, like "effortless," "transformative," and "next-level." Prefer short, direct sentences. If a sentence needs a semicolon, split it into two sentences instead. Use "you" and address the reader directly. Avoid "our valued customers" or third-person distancing. Humor is fine in social captions and blog intros, but never in product emails about billing, outages, or account changes, and never in a customer service reply where someone is already frustrated. Every piece of writing should include one concrete detail (a number, a specific scenario, a real example) rather than staying abstract throughout. Default length: shorter than you think it should be. Cut the second draft by at least 20%. When something has gone wrong on our end, say so plainly in the first sentence, don't bury the apology under three sentences of context first.
Before producing final copy, ask me what the piece is for (channel, audience, goal) if I haven't already said, rather than guessing.
”Alongside those instructions, the Knowledge files would include: a blog post the team considers a strong example of the voice, a customer email that got a genuinely good response, and a one-page written brief describing the target customer in plain language (not a formal persona document, just how the team actually talks about who they're writing for).
Why this beats a saved prompt for this specific job
Brand voice is exactly the kind of task where the comparison in Gems vs. a saved prompt tips clearly toward a Gem. A saved prompt you paste in every time works fine for something you do occasionally. Brand voice gets invoked constantly, across many different content types, often by more than one person on a team, and it benefits enormously from attached reference examples rather than just a description. That combination, high frequency plus real reference material, is what a Gem is actually built for.
Pasting a tone description each time
- Fine for occasional, one-off writing tasks
- No attached examples, only adjectives to go on
- Drifts as the description gets retyped slightly differently each time
A dedicated brand voice Gem
- Voice rules and real writing examples live in one place, permanently
- Anyone on the team gets the same consistent output
- Easy to update once when the voice evolves, instead of everywhere
Putting it to work on a real piece of content
Once the Gem exists, using it is just a normal conversation, but the difference shows up immediately in how little context you have to supply. A prompt like this, sent to the brand voice Gem rather than a plain chat:
Write a launch announcement email for a new integration with Slack. Audience is existing customers. Keep it to about 150 words.
”comes back already sounding like the brand, with no need to re-explain tone, because the Gem already knows it. Compare that to sending the identical prompt to a fresh chat with no Gem: you'd get competent copy, but generic, and you'd spend the next few messages nudging it toward the voice you actually wanted.
Proving the voice holds across two unrelated content types
One good output doesn't prove a Gem is actually doing its job. The real test is whether the same Gem produces a recognizably consistent voice across two pieces of writing that have nothing structurally in common: a product description meant to excite someone, and a customer service reply meant to calm someone down. If the voice only shows up in one of them, the Gem is thinner than it looks.
Here's the Ridgeline PM Gem asked for a short product description of a new feature:
Write a two-sentence product description for our new feature that lets managers set automatic reminders for overdue tasks. This is going on our features page.
”Illustrated output: product description, Ridgeline PM Gem
Now here's the same Gem, same conversation, handling a customer service reply about a billing mistake:
A customer was charged twice for their monthly subscription due to a billing system glitch. Write a short reply acknowledging the mistake and letting them know the duplicate charge is refunded.
”Illustrated output: customer service reply, same Gem, same conversation
Notice what carried over even though the two pieces share no structure at all: short, direct sentences with no semicolons, no third-person distancing like "valued customer," the mistake stated plainly in the first sentence rather than buried under hedging, and zero hype words in either one. The product description gets a small dose of dry, colleague-to-colleague voice ("stop being your problem to remember"), and the billing reply stays serious with no attempt at humor, exactly as the instructions specify for that situation. That's the actual evidence a brand voice Gem is doing more than repeating adjectives back at you: the same rules produce recognizably the same brand whether the content type is trying to sell something or apologize for something.
Keeping it from drifting
A brand voice Gem isn't a one-time build. Revisit it every few months: swap in a newer example if the voice has evolved, tighten a rule that keeps getting ignored, and remove a rule that turned out not to matter in practice. The biggest mistake teams make is building the Gem once, being thrilled with it for a month, and then never updating it as the brand's actual writing moves on, so the Gem quietly becomes a slightly outdated version of the voice instead of the current one.
Tip
If more than one person on your team writes brand content, share the Gem rather than letting each person build their own version. A single shared Gem is also a de facto style guide, one that updates itself the moment you edit the instructions.
If you haven't built a Gem before at all, the Complete Beginner's Guide to Gemini walks through the basic setup mechanics this article assumes you already have in place.
Official sources
Checked on September 21, 2026. Features, plans and names change often, so the vendor's own pages are the final word.