TL;DR: Instead of iterating on a prompt five times, ask the AI to rewrite your request into a proper system prompt first. One extra step, consistently better output.
There’s a small trap most people fall into with AI tools. You write a prompt, get something okay but not quite right, tweak it, still off, tweak again. Three rounds later you’re not sure if the output improved or you just lowered your standards.
Think about the last time you asked an AI to write something that actually mattered. Maybe a client email, a product description, a technical brief. Your first prompt was vague because you were figuring out what you wanted as you went. The AI filled in the gaps with guesses. Some of those guesses were fine. Some weren’t. So you patched the output manually or re-prompted with slightly different wording. That process works eventually, but you’re doing most of the heavy lifting, and the AI is just reacting.
A framework making the rounds on r/PromptEngineering addresses this at the root. Instead of you iterating on the prompt, you ask the AI to write its own instructions first.
The prompt is simple:
“I want you to [Task]. Before you start, rewrite my request into a high-fidelity system prompt with a persona and specific constraints.”
The model takes your rough ask, builds a detailed spec, then executes against that spec. You’re not just prompting. You’re having the AI architect its own working instructions before it touches your task.
What comes back in that spec step is usually more thorough than anything you’d write cold. The AI will define the tone, the format, what to include, what to skip, who the audience is. It’s surfacing all the implicit decisions that were previously invisible. And once those decisions are visible, you can review them before the work starts. If the persona is off or the format doesn’t match what you need, you catch it at the spec stage instead of after three rounds of drafting.
Why this actually works
LLMs have been trained on massive amounts of well-structured system prompts. When you ask one to write its own, it draws on that training to produce something more precise than most people would write manually. It’s the same reason asking Claude “how should I prompt you to do X?” often surfaces better approaches than just trying X directly.
There’s also a consistency benefit that’s easy to miss. When you write a prompt on the fly, it changes slightly every time. Your wording shifts depending on how you’re thinking that day. A generated system prompt is explicit and reusable. You can save it, refine it once, and run it across multiple tasks. Over time you accumulate a library of solid prompts for recurring work, which compounds in a way that any single output never does.
You’re using the model’s own knowledge of what good prompts look like to bootstrap better output from the start.
Use Cases
- 🧠 Complex writing tasks where tone and structure matter: define the persona before the first sentence. An AI told to “write like a senior strategist advising a founder” will approach the task differently than one given a vague “write this article.” The persona anchors every decision downstream.
- Code reviews: let the AI set its own reviewer constraints before it touches your codebase. It might define things like “flag anything that breaks single responsibility” or “prioritize readability over cleverness.” Those constraints make the review consistent and targeted rather than a grab-bag of observations.
- Research summaries: have it define depth, format, and scope upfront. Without scope definition, you’ll get either a PhD thesis or a tweet. The self-written prompt forces the AI to decide what level of depth is actually useful for your context.
- Customer-facing emails: establish voice, goal, and constraints before drafting. Is the goal to retain, to upsell, to apologize? Is the tone warm or professional? These decisions affect every sentence. Making them explicit upfront means you’re not discovering them through revision.
Prompt of the Day
I want you to [describe your task]. Before you begin, rewrite my request into a high-fidelity system prompt. Include a persona, specific constraints, output format, and any assumptions you’re making. Then execute against that system prompt.
A quick breakdown of what each piece does: the persona gives the AI a point of view to write from; the constraints set the guardrails (word count, what to include, what to avoid); the output format removes ambiguity about structure; and asking it to state its assumptions forces it to surface any gaps in your original request. That last one is underrated. If the AI says “I’m assuming this is for a technical audience” and it’s not, you catch that before a single word of the actual output is written.
Try it once this week
Pick one task where you’ve been getting inconsistent output. Run this meta-prompt first. Compare what comes back to what you normally get. That gap is the whole argument for the framework.
Pay attention specifically to the spec it generates, not just the final output. If the spec alone clarifies what you actually wanted, that’s the proof of concept. You’ll notice which parts of your original ask were ambiguous and which assumptions the AI was quietly making every time you ran it. That awareness alone changes how you prompt going forward.
The ‘Logic Architect’ Framework.
by u/Significant-Strike40 in PromptEngineering