Start with writing you have the right to use
A voice guide describes the choices that make your writing recognizable: how you open a piece, explain an idea, vary sentence length, address readers, and decide when to be funny or direct. It is more useful than a vague instruction such as “sound like me,” because it gives you and an AI assistant concrete decisions to follow.
Collect a small set of your own finished pieces that represent the kind of work you want to create. If you write both informal newsletters and technical explainers, make separate guides or label the samples by purpose. Include a piece you feel captures your voice especially well and another that shows how you handle a difficult explanation. Avoid treating every old draft as a model; some habits are worth leaving behind.
Before pasting samples into an AI tool, check whether they contain private messages, client material, unpublished plans, or details about other people. Remove anything you do not need for the task. You can also build the guide yourself from notes and short excerpts rather than uploading complete documents. The goal is to identify your choices, not to hand over your entire archive.
Notice patterns instead of collecting adjectives
Read your samples with a question in mind: what do you repeatedly choose when several reasonable options are available? Mark openings, transitions, examples, endings, and places where you define a term. Notice whether you tend to state the point first or build toward it. Look at the kinds of comparisons you make and whether your paragraphs usually carry one idea or several.
Separate stable preferences from features of a particular assignment. A short sentence in a product announcement may reflect the format, not your voice. Likewise, a joke that worked once is not necessarily a rule to repeat. Look for patterns across pieces and make room for exceptions. Your guide should describe how you make choices, not force every paragraph into the same shape.
An AI assistant can help you inspect samples, but ask it to show its reasoning in a checkable way. For example: “Identify recurring features in these pieces. For each feature, point to a brief example from my text, explain when it appears, and flag anything you cannot infer confidently.” Review its observations yourself. If it calls your work “warm and engaging” without identifying what creates that effect, ask for a more precise description or leave the claim out.
Turn observations into usable instructions
Write the guide as a short working document. Give it a purpose, such as “plain-language essays for curious non-specialists,” then describe your audience and a few reliable habits. Useful entries are actionable: “Open with a concrete problem before introducing a concept” or “Define a technical term in everyday language, then use the term consistently.” Add preferences about rhythm, examples, humor, and endings only where your samples support them.
Include boundaries as well as preferences. You might write, “Do not manufacture personal anecdotes,” “Avoid grand predictions,” or “Do not add a joke to a serious explanation.” If you use distinctive phrases, decide whether the guide should preserve them or avoid repeating them too often. A voice is not a stockpile of catchphrases; it is a pattern of judgment about what belongs in a piece.
A compact guide is easier to apply than a long list of flattering descriptions. For each instruction, ask whether you could tell from a draft if it had been followed. Replace “be authentic” with something observable, such as “acknowledge a practical limitation before offering a recommendation.” Keep the guide editable. As your writing changes, you can revise it rather than preserving an outdated version of yourself.
Use the guide to draft, then test the result
When you ask AI for help, provide the voice guide alongside the task, audience, and material the draft must cover. Try a prompt such as: “Draft an introduction using this voice guide. Use only the facts in my notes. If a personal example would help, insert a placeholder instead of inventing one.” This keeps the assistant focused on your decisions without inviting it to fill gaps with plausible-sounding details.
Test the guide on a fresh topic rather than on a piece already included in your samples. Read the result aloud or compare it with a paragraph you would have written yourself. Where does it sound generic? Where has it exaggerated a habit, such as turning every sentence into a punchline? Revise the guide to address those failures, then test again. One successful draft does not prove the guide works for every format.
Keep final control of the writing. An AI draft may follow surface instructions while missing your intended emphasis or making an unsupported claim. Check facts against the material you supplied, restore nuance, and rewrite any passage that feels performative. The guide should make collaboration easier, not make editing optional.
Keep inspiration distinct from imitation
It is normal to admire another creator’s clarity, pacing, or structure. You can learn from those broad techniques without asking an AI tool to reproduce that person’s voice. Instead of requesting a draft “in the style of” a named writer, describe the outcome you want in your own terms: a clear opening, concrete examples, or a restrained ending. Then use your own work to decide how those techniques fit.
If a generated passage reminds you strongly of someone else’s distinctive phrasing, imagery, or recurring devices, revise it. The same applies when it echoes your source samples too closely: a voice guide should help produce new work, not recycle old sentences. Treat the guide as a record of choices you can make again, and leave room to make different choices when the subject calls for them.
