In partnership with
LUXE PROMPTING
LUXE PRACTICAL WORKSHOP
Your Brand Rules Should Outlive the Chat.
The next tool change should not force you to rediscover your brand voice. Google’s current guidance says personal-account Gems begin transitioning to skills in November 2026, with work and school accounts following in 2027. Whether you use Gemini or another assistant, this is a useful moment to separate your brand rules from the chat that happens to hold them.
The AI notetaker that gets the hard words right
Your AI is only as good as what you feed it. Feed it a transcript with your product names, acronyms, and numbers spelled wrong, and you spend the afternoon hand-fixing the output.
Wispr Flow Notetaker uses your dictionary and calendar, so product names, acronyms, numbers, and uncommon names come out spelled right. It pops up when your meeting starts and captures Zoom, Google Meet, Teams, and Slack huddles with one click, no bot joining the call.
Then your meetings show up inside Claude or ChatGPT through the built-in connector. No copy paste. Try Notetaker free on Mac and Windows.
The Short Version
- Keep durable voice rules separate from prices, dates and other changing business facts.
- Save a few approved examples with explanations of what makes them useful.
- Test the moved instructions against the same small set of tasks before relying on them.
A folder is not a finished brand system
Google’s migration instructions include preserving knowledge files and copying instructions. They also note differences in supported files. That is a reason to inspect your material, not a reason to assume every old attachment will behave identically after a move. Check the current guidance for your actual account type before changing anything.
Our suggested starting point is a short brand context document with a named owner and revision date. Put one current copy in a known location. Link to supporting material instead of burying every historical campaign in the main instructions. A person should be able to understand the rules without reading your entire chat history.
1. Separate voice from facts
Voice rules describe how you communicate: direct explanations, concrete examples, modest claims and the terms your audience recognizes. Business facts describe what is currently true: a product name, price, release date or offer. Store those facts in a separately dated reference so an expired promotion cannot become a permanent part of your voice.
2. Explain your examples
Choose two short pieces that genuinely represent the brand and one that misses it. Explain the difference in observable terms. “Uses a specific reader problem” is more actionable than “sounds premium.” Remove private customer details and any material you are not permitted to upload. More examples are useful only when they add a new distinction.
3. Make conflicts visible
State what should happen when references disagree. For example, the latest approved product sheet can govern factual names while the voice file governs tone. If no trusted source resolves a price conflict, the assistant should flag the question instead of choosing a plausible number. A confidence-sounding sentence is not a substitute for a current fact.
4. Replay three ordinary jobs
Try a product introduction, a customer explanation and a correction of outdated copy. Use the same inputs before and after moving the instructions. Compare factual accuracy, forbidden claims and tone separately. Keep the original setup intact until the replacement passes your checks. Record differences rather than declaring success because the settings page saved.
Keep maintenance deliberately small
Add a brief change note whenever a rule changes: what changed, why and who approved it. Review the examples when the positioning changes, not every time a single sentence is edited. If the file keeps growing, ask which instructions could be deleted without changing a good result.
The payoff is not a promise that every assistant will sound identical. It is a portable set of decisions you can inspect, revise and test. Start with one page and one real task. If another colleague cannot explain the brand from that page, refine the document before adding another automation around it.
Source Desk
Primary documentation checked October 26, 2026. The practical workflow is Luxe editorial guidance, not a measured performance claim. Google’s transition dates differ by account type; availability and supported files can change. This is not a migration test. Recheck product details before use.
A clearer brief. A more useful result.