Most people treat AI voice calibration like a magic trick, hoping a single sentence like “write in a witty tone” will solve everything. But the reality is that an algorithm cannot mimic your psychology if you haven’t taken the time to download your brain into a format it can understand. This incredible post from an AI professional outlines a rigorous, 47-minute protocol that solves the “generic voice” problem once and for all.
💡 The “Deep Interview” Mechanism
The core of this strategy isn’t about writing better prompts; it’s about submitting yourself to an interrogation. The expert behind this method suggests that we are terrible at describing our own writing styles because we edit our thoughts as we type. To bypass this internal filter, the author created a process involving a 100-question interview that captures your raw cognition.
The secret sauce here is the medium of communication. Instead of typing your answers to the AI, this industry pro insists you must speak them out loud. By using a voice-to-text tool (the post suggests Wispr Flow), you capture the stuttering, the phrasing, and the stream-of-consciousness logic that defines your actual personality. Typing leads to polished, safe answers. Talking leads to honesty. This raw data forms the foundation of a “Taste File” that effectively clones your decision-making process for the AI.
📌 The Power of Negative Definition
One of the most profound takeaways from this innovator’s guide is the concept that your “voice” is defined more by what you reject than what you prefer. Most users waste their context window telling ChatGPT what they like, using vague terms such as “professional,” “clear,” or “engaging.” These are subjective words that mean different things to different models.
This savvy professional argues that 80% of your personality file should consist of refusals. You need to explicitly document the things you would never say. Do you hate the word “delve”? Put it in the file. Do you despise starting sentences with “In today’s fast-paced world”? Document that. By building a fence around the language you hate, you force the AI into the narrow corridor of the language you actually use. This negative definition creates a much sharper, more distinct profile than positive affirmation ever could.
📌 Granularity is the Only Metric That Matters
When you do describe what you want, you must move from qualitative feelings to quantitative rules. The post’s author highlights a critical step where the AI pushes back on your answers. If you say you like “simple writing,” the AI should ask, “Simple how?”
You have to be prepared to answer with extreme specificity. The creator gives a brilliant example of translating “simple” into executable code: “3 sentences max per paragraph. No semicolons. No words over 3 syllables if a shorter one exists.” This transforms a vague artistic preference into a rigid constraint that the Large Language Model can strictly follow. The specificity is the taste. Without these hard metrics, the AI will simply default to its training data, which is the definition of generic.
📌 The Dynamic .md Ecosystem
Finally, the technical execution of this strategy is just as important as the philosophy. This talented creator advises against keeping this information in a loose collection of notes. Instead, you must consolidate your entire “brain dump”—the interview answers, the refusals, the specific metrics—into a single Markdown (.md) file.
This file becomes your portable brain. The author recommends uploading this file to the “Project” or “Knowledge” section of your AI tool (specifically mentioning Claude here) rather than pasting it into every chat. The workflow is simple but disciplined: you start every single session with the command “Read [yourname].md first.” Furthermore, this isn’t a static document. As your style evolves or as you discover new “cringe triggers” in AI outputs, you must update the file. It is a living operating system for your digital twin.
⚠️ The Friction Barrier
The only real downside to this method is the friction involved in the setup. As the original poster bluntly states, “Most people won’t sit for 47 minutes.” It requires significant mental energy to answer 100 probing questions about your own psychology. It feels tedious, and listening to your own rambling answers can be uncomfortable. However, this barrier to entry is exactly why it works. If it were easy, everyone would do it, and everyone would sound the same. You have to be willing to do the hard work upfront to enjoy the automated ease later.
The 47-Minute Protocol
Here is the step-by-step breakdown of the expert’s method:
- Preparation: Download Claude and select the Opus 4.5 model (or your most capable available model).
- The Prompt: Locate the specific 100-question interview prompt (linked in the original post).
- The Interview: Answer every single question out loud using a voice-to-text tool like Wispr Flow to ensure total honesty.
- The Refusal Audit: Focus 80% of your energy on defining what you reject and would never say.
- The Stress Test: When the AI asks for clarification, provide specific constraints (syllable counts, sentence lengths), not vague adjectives.
- The Artifact: Save the entire transcript and rule set as a single .md text file.
- The Deployment: Upload this file to your AI’s “Project” feature.
- The Maintenance: Update the file every 3-4 months as your taste changes.
The Critical Don’ts:
- Don’t skip the interview; there are no shortcuts.
- Don’t be vague (e.g., “I like clarity”).
- Don’t forget to list at least 10 words you would never use.
- Don’t expect the AI to read your mind without this data.
The Critical Do’s:
- Always use “Projects” to store the file context.
- Always turn on “Extended Thinking” capabilities.
- Always document refusals alongside preferences.
- Always start your prompts by referencing your .md file.
This is the difference between a tool that writes for you and a tool that writes like you. It takes less than an hour, but it saves you hundreds of hours of editing down the line.
Check the link below to get the full interview prompt from the author!