Three words changed how one Redditor prompts every AI model he touches. The original poster, u/Tomjhzhang, calls it the AIM method: Actor, Input, Make. It takes about ten extra seconds to write, and most people skip it entirely.
Here’s the breakdown he shared in r/PromptEngineering: tell the AI who it is, tell it who you are, then tell it what to build. Nothing revolutionary on paper. But most people jump straight to step three, and that’s exactly why their outputs feel flat.
Quick Start
Before your next prompt, add two sentences in front of the request. One assigns the AI a role. One gives it your background. Then ask for what you actually want.
The One-Line Trap
Here’s how most people prompt, according to the post: “write an article about gpt6astra.” Short, direct, and missing everything the model needs to do the job well.
The AI has no idea who it’s supposed to sound like. It doesn’t know your skill level, your audience, or why you’re asking. So it defaults to generic, and you get competent, forgettable text that reads like it came from nowhere in particular.
The AIM method attacks that gap directly. Instead of one sentence, you write three, stacked into a single prompt:
“You are a great content creator and writer, and I’ve written several articles on medium about AI but I’m unsure about how to write well. Write an article about gpt-6-astra, the newest ai model, and introduce it to reader”
Same request underneath. Completely different setup around it.
Why the Extra Two Sentences Matter
- 🎯 Actor sets the frame. Telling the model “you are a great content creator” pulls it toward a specific register and vocabulary, instead of a flat neutral tone.
- 🎯 Input gives it your context. Mentioning you’ve written before but struggle with clarity tells the AI exactly what to fix, not just what to produce.
- 🎯 Make is the part everyone already does. It’s the actual ask, unchanged from how you’d normally write it.
The author’s point isn’t that any single piece here is new. Role prompting and context-setting have both been around for a while. The real contribution is bundling all three into a habit you remember. It beats a technique you read once and forget by the next chat window.
Not Everyone’s Sold, and That’s Worth Noting
The comments push back hard, and the disagreement is worth sitting with. One commenter called role assignment “outdated advice” that “doesn’t seem to have any effect on giving a better result.” Another said assigning roles never made sense to them because the model “already knows everything.”
Both points have merit. Modern models are better at inferring intent than they used to be, and a role label alone won’t rescue a vague ask. But the AIM method isn’t really selling the role assignment in isolation. It’s selling the habit of adding context before you hit enter. That context, your background, your goal, your skill gap, is the part skeptics aren’t arguing against.
A third commenter summed up the real value nicely. Slapping a name on basic habits makes them easier to remember for anyone who normally fires off one-liners. That’s the actual pitch here, not a secret trick nobody knew.
How to Use It This Week
- Pick a prompt you’d normally write as a single line.
- Add one sentence assigning a role that fits the task, like writer, analyst, or coach.
- Add one sentence describing your situation: what you know, what you’re stuck on, what you need.
- Write your actual request exactly as you would have before.
- Compare the output against what a bare one-liner gives you on the same task.
Run that comparison two or three times on prompts you’d send anyway. That’s the only way to know if the extra two sentences earn their keep for your use cases, whatever the comment section thinks.
The method isn’t limited to writing tasks either. Ask for code and the Actor line might be “you are a senior backend engineer,” with the Input line noting your stack and experience level. Ask for a workout plan and the Actor becomes a coach, with the Input covering your current fitness and injury history. The shape stays the same across domains: role, context, then the ask.
One caution worth flagging: don’t let the habit turn into padding. If your role and background lines don’t actually change what the model needs to know, they’re just extra words. The method works when the Actor and Input lines carry real information the model would otherwise be guessing at. It fails the moment they turn into copied boilerplate stapled onto every prompt.
If you want a fast reference, save the acronym somewhere you’ll actually see it. Actor, Input, Make. Three quick additions, one prompt, better odds of getting what you asked for on the first try!
The original thread has more back-and-forth worth reading, plus a free prompt pack the author is offering to anyone who asks in the comments. Worth a scroll if you want the full debate.
Frequently Asked Questions
Q: Does assigning a role (the “Actor”) actually improve AI responses?
This is debated. Some users find that setting a role helps the AI understand their needs better, while others argue that AI already has broad knowledge and role assignment doesn’t meaningfully change results. The real value may be in clarifying your intent to the AI and yourself, whether through role assignment or simply being explicit about your background and goals.
Q: Is the AIM method actually new, or just a renamed version of what people already do?
It’s largely a framework for organizing what many experienced prompters already do intuitively. As one commenter noted, AIM just gives a memorable name to a pattern people have been using. If you’re already including context and clear instructions, you’re probably already using the AIM method without calling it that.
Q: Can I skip the Actor step and just use Input and Make?
Yes, many users get excellent results by focusing on Input (your background) and Make (what you need) without the Actor step. Experiment with skipping it to see if it meaningfully changes your results. The Actor step seems most helpful when you want the AI to adopt a specific perspective or tone.
Q: Who is the AIM method best for?
It’s most useful for people who tend to write short one-liner prompts and need a structure to follow. If you already provide detailed context and clear instructions naturally, you may not notice much difference. It’s a helpful mental model for beginners or anyone looking to level up their prompting consistency.
The AIM method to prompt AIs
by u/Tomjhzhang in PromptEngineering