Most people are debugging their wording. The real problem is their framing.
A guy in r/PromptEngineering spent six months rewriting the same prompt 12 times. Different words, same mediocre output. He tried shorter prompts. He tried longer prompts. He tried adding “think step by step” and “you are an expert” at the top like some kind of magic spell. Nothing moved the needle. Then he changed the framing entirely. Stopped treating Claude like a search engine. Started treating it like a new hire who showed up on Monday with a good attitude and zero context about the company.
Output doubled.
Here’s the thing about new hires: they don’t need you to script every sentence. They need a clear role. Your standards. A definition of “done.” They need to know what good looks like in your world, not in some generic universe. That’s exactly what most prompts are missing. No role. No standards. No sense of what failure looks like. Just a task floating in a vacuum, and then frustration when the output feels generic. It is generic, because you gave the AI nothing to anchor to.
The prompt is not broken. The onboarding is missing.
The old way vs. the new way
Old way: “Write me a caption for this post.”
New way: “You are my social media strategist for a creative agency in SW Florida. Our clients are local hospitality businesses. Our tone is warm, specific, and never corporate. Write a caption.”
Same request. Completely different output. The second one has a role, a context, a professional standard implied. The AI stops guessing what “good” means and starts performing against a real bar. It knows the geography. It knows the industry. It knows what tone to avoid. You gave it a job description instead of a to-do list, and now it can actually do the job.
Think about what happens when you onboard a real person at a company. You don’t walk up to them on day one and say “write a report.” You explain who the company is, who the audience is, what the company’s voice sounds like, what formats you use, and what gets flagged in review. The person then produces something that actually fits. The AI works the same way. It just onboards faster, costs less, and never asks for PTO.
🛠️ Three things that actually work
1. Give it a title, not a task
Don’t say “write a caption.” Say “you are my social media strategist. Write a caption.” Role first, task second. Every time. This one shift changes the register of the output. The AI is no longer filling in a blank. It is inhabiting a function. A strategist thinks about the audience, the goal, the platform, the brand voice. A task-executor just produces words. You want the strategist. Give it the title and it shows up differently.
This works for every use case. Not just social. “You are my legal editor reviewing contracts for a SaaS company” hits differently than “check this contract.” “You are my executive coach and I’m about to pitch a VC” gets you a different quality of pushback than “give me feedback on my pitch.” The role activates a whole different mode of thinking.
2. Stop pasting context every session
Set it once in a system prompt or a Project and let it persist. Pasting the same 300-word context block every session is just expensive repetition. Do it once, forget it exists, and let the AI remember who it is. More importantly, build the context block properly the first time. Include the audience, the voice, the format preferences, the things you always fix in edits. Think of it as an employee handbook. You write it once, it runs in the background forever, and every output reflects it without you having to remind anyone.
The people getting consistent, high-quality output from AI tools are not better at prompting. They are better at setup. They did the work upfront so they don’t repeat it endlessly downstream.
3. Define failure explicitly
“Never use the word ‘delve’. Never open with ‘Certainly’. No bullet lists when I ask for prose. No hedging language like ‘it’s worth noting that.’ Never summarize what you just said at the end.” Most people tell the AI what to do. The best users also tell it what NOT to do. That is where generic output disappears. The AI has defaults. Some of those defaults are annoying. You can turn them off, permanently, by naming them in the system prompt. This is not a trick. It is just good onboarding. Every good manager tells a new hire what they hate as clearly as they explain what they want.
None of this is complicated. It’s a mindset shift. From querying to onboarding. You are not typing into a search bar. You are briefing a collaborator. And a well-briefed collaborator does not need to be corrected twelve times before they understand the assignment.
Try the job description framing on your next prompt. Write two sentences of role and context before the actual request. You’ll feel the difference immediately.
Frequently Asked Questions
Q: What should I put in my “never do this” list?
Get specific about language you hate. Overused words like “unlock” or “delve,” opening phrases like “Certainly…,” formatting you never want (prose instead of bullets), and brand voice killers. The clearer your don’ts are, the better the AI understands what you actually want.
Q: Do I have to paste my context and role every single session?
Nope. Set it once in a system prompt or Project and forget about it. This persistent memory approach saves time and ensures consistency across all future chats without re-explaining yourself.
Q: Why do people struggle if this works so well?
Most people default to treating AI like a search engine and write detailed procedural prompts. The shift to thinking of AI as a new hire who needs context and standards, not scripts, is counterintuitive, but once you make it, the output quality jumps.
Q: Won’t newer AI models with thinking features make this approach unnecessary?
Newer models can infer context better, but being explicit about your role, standards, and what failure looks like still produces more consistent, personalized results and cuts down on iteration.
I stopped writing prompts and started writing job descriptions. My AI output doubled.
by u/Accomplished_Wrap705 in PromptEngineering