TL;DR: Forget abstract tone instructions. One character reference with emotional context does more work than a paragraph of “be concise, be direct.”
The Prompt
A Reddit user from r/PromptEngineering dropped this into their custom instructions and told everyone to thank them later:
Speak like MacGyver (the original, not that shit head in the remake) on a Wednesday, after receiving decaf when he had ordered a double red eye.
That single line packs more instruction than most people put in their entire system prompt. And it works because of what it communicates without saying it directly.
The post got traction not because it was clever, but because it was immediately legible. People read it and felt it. They understood exactly what kind of output that would produce before they even tested it. That instant recognition is the whole point. When a prompt makes you think “yeah, I know exactly what that sounds like,” you have already done most of the work.
Why Character-Based Prompting Beats Abstract Instructions
Abstract instructions fail because they are ambiguous. “Be concise” means different things to different models. “Be direct” could mean blunt, brief, or just less polished. The model has to guess at what you actually want.
Think about how many custom instructions look like this: “Respond in a clear, professional, and concise tone. Avoid unnecessary filler. Be helpful but not verbose.” That description fits a customer service bot, a legal assistant, a coding copilot, and a recipe generator equally well. It does not describe a personality. It describes a preference for fewer words, which the model then interprets differently depending on the task.
Character references bypass that problem entirely. You are loading a pre-trained personality into context. The model already knows MacGyver. You are just specifying the mood and the stakes.
Break down what this specific reference actually communicates:
- MacGyver = resourceful, practical, no fluff, solves problems with what is available
- Original, not the remake = specificity signals you want the real version, not a softened imitation
- Wednesday = mid-week drag, energy is not at its peak
- Ordered a double red eye, got decaf = mildly frustrated, running on fumes, wants results not conversation
The emotional context sharpens everything. The model reads that setup and understands: this person needs answers, not elegance.
Compare that to the alternative. If you wrote “be slightly frustrated and low on patience,” you would get something technically compliant but tonally flat. The emotional state described in the abstract has no texture. The emotional state described through a situation does. “After receiving decaf when he had ordered a double red eye” is a scene. The model can inhabit a scene in a way it cannot inhabit an adjective.
This is why fictional and cultural references punch above their weight in prompting. They carry implicit behavioral contracts. You say Hemingway, the model shortens sentences. You say Aaron Sorkin, it speeds up and starts writing in volleys. You do not have to explain any of it because the training data already did that work for you.
Use Cases
Where this kind of character prompting actually moves the needle:
- 🔧 Technical troubleshooting: a frustrated MacGyver finds the fix with what is on hand, not what is ideal. You get practical workarounds, not theoretical best practices that require three tools you do not have.
- 📋 Writing drafts: cuts filler phrases faster than “be concise” ever will. When the character would not say it, the model tends not to write it.
- 🧠 Brainstorming: gives you rough, practical ideas instead of polished generalities. The slight frustration in the persona pushes toward “what actually works” instead of “what sounds good.”
It also helps with consistency across sessions. Abstract tone descriptors drift. “Professional and concise” gets interpreted slightly differently depending on context. A well-chosen character reference holds more stable because there is a larger body of shared understanding anchoring it.
Prompt of the Day
Adapt this template for your own custom instructions:
Speak like [specific character, not the watered-down version] on [specific day or situation], after [specific frustration that creates urgency].
The more specific the setup, the more consistent the output. Vague characters produce vague personalities. Put them in a corner and they get interesting.
A few starting points if MacGyver is not your vibe: a seasoned ER nurse at hour eleven of a twelve-hour shift, a chess coach watching a student repeat the same mistake for the third time, a veteran detective who already knows where this is going. Each of those carries a distinct set of behavioral defaults. Pick the one that matches how you actually want your AI to treat your problems.
Try It This Week
Drop a character-based tone instruction into your custom instructions. Test it against your current abstract tone descriptor. See which one actually shifts the output in a way you can feel.
Run the same prompt through both versions. Ask for a quick explanation of something in your field, a short outline, a blunt assessment of an idea. You are not looking for a dramatic transformation. You are looking for whether one version feels more like talking to someone who gets it. If the character reference wins even half the time, it has already earned its place.
One line. That is the whole trick.
Add this to the end of your custom instructions, thank me later.
by u/Jasmar0281 in PromptEngineering