
Copy a prompt that worked in one assistant, paste it into another, and the output can feel like an entirely different job. Same words. One returns four tight paragraphs. Another hands back a bulleted essay plus an offer to expand section three. A third answers the question you asked but quietly drops the constraint you cared about most.
A prompt is not a spell. It is a brief, and every assistant reads briefs with its own habits. The practical fix is not to learn three separate writing styles. It is to keep one strong prompt and learn a short translation routine for tone, length and formatting. Ten minutes of setup, reusable for months.
Why one prompt behaves three different ways
Assistants differ in ways you can observe in a single sitting. How they were tuned to be helpful, how chatty their defaults are, and how strictly they follow structural instructions all shift the result. Some fill silence with extra options. Some treat "short" as two paragraphs; others treat it as six sentences. Some default to headings and bold text even when you wanted prose.
None of that makes your prompt wrong. It means your instructions carry an unstated delivery spec — the part you assumed you did not need to say, because your usual assistant guesses correctly. Move the prompt and the guess changes.
The core prompt worth porting
Start with a brief that has all the substance and almost none of the style. Substance travels; style needs tuning.
You are a technical editor. Rewrite the notes below for a small business owner who has never used accounting software. Explain one idea per paragraph, define any term a beginner would stumble on, and keep every number from the original. Do not add advice that is not in the notes. End with one question that tests whether the reader understood the main point. Notes: [paste notes]
That prompt survives a model switch, because it names the audience, the job, the constraints and the finish line. What it does not name is how long the answer should be, how it should look, and what voice to use. Those are your three adjustment dials.
Reading each assistant's defaults
Run your core prompt unchanged in each tool once, then note what it did without being asked. Keep a one-line note per assistant; patterns show up fast.
ChatGPT
Usually eager and structured. Expect headings, bullet lists and a closing offer of next steps. Helpful when you want options, noisy when you want one clean answer. Lines like "give me one version only" and "no lists" land well here.
Claude
Often leans toward prose and longer explanations, with careful hedging on ambiguous points. It tends to follow explicit formatting rules closely, including negative ones such as "do not use bullet points." If an answer feels padded, tighten the word budget rather than adding more instructions.
Gemini
Tends toward compact answers and bullet-heavy summaries, and may fold in current information when the question invites it. It can be terse enough to drop the connective explanation between steps, so a line like "add one sentence of context between steps" often helps.
Treat these as starting observations, not laws. Model updates shift behavior, and your own examples will teach you more than any general list.
The five-minute adaptation routine
- Run the core prompt unedited. Judge the output against what you actually needed, not against how polished it sounds.
- Name the single biggest gap. Too long, wrong register, or wrong shape. Fixing one thing at a time keeps you from guessing which instruction did what.
- Add one delivery line. Placed at the end: "Write about 200 words, in plain paragraphs, no bullet points, second person."
- Rerun with the same input. Same notes, same question, so the comparison is fair.
- Save the version that works. One snippet per assistant, labeled with the date you last checked it.
Most prompts need two or three rounds of this. If a fourth round still misses, the brief is probably ambiguous rather than the assistant being stubborn.
Tone, length and formatting: the three dials
Tone
Name the audience and the register in the same breath: "for a skeptical finance manager," "as a patient tutor," "like a colleague explaining it at a desk, contractions fine, no exclamation marks." Abstract adjectives such as "professional" or "friendly" mean different things to different models. Concrete audience plus one or two prohibitions works better.
Length
Give a number and an anchor. "About 250 words — roughly the length of a short email" removes more ambiguity than "keep it brief." If the content cannot fit, say what to cut first: "trim examples before steps." Also state whether going under is acceptable; many models pad upward to look thorough.
Formatting
Say what you want and what you refuse. Useful lines include:
- "Plain paragraphs only — no headings, no bold, no bullet points."
- "Use at most three headings; everything else in prose."
- "Number the steps; no preamble before step one."
- "Reply in markdown because I am pasting this into a document."
- "No summary at the end; stop after the last step."
Formatting instructions are cheap and usually obeyed. They are the fastest way to make three outputs look like they came from one writer.
What should stay constant
Keep the substance of the brief identical across every version: the role, the audience, the source material, the facts that must survive, the definition of done, and any hard constraints such as "do not invent figures." Change only the delivery layer — tone, length, formatting. If your facts start drifting between versions, you are no longer comparing assistants; you are comparing two different jobs.
One more habit worth building: ask the assistant to restate the brief in two lines before it writes. That catches a misread instruction in seconds instead of after a thousand words. For prompts touching medical, legal or financial decisions, treat the output as a draft for a qualified professional, not as the answer itself.
Build a small translation layer
Store your core prompt once, then keep a three-line addendum for each assistant — the delivery sentence that reliably gets you the shape you want. When a model updates and the output shifts, you revise one line. That is the whole method: one brief, three accents.
Photo: kaboompics / Pixabay


