One prompt to rule all your other prompts. That’s the idea behind a meta prompter, a prompt whose only job is to rewrite your sloppy requests into something an LLM can actually nail. A Reddit user named u/Present-Boat-2053 dropped this gem in r/PromptEngineering, claiming they spent 20 hours refining it. After reading through the full system prompt, I believe every hour was well spent. This isn’t a toy. It’s a structured, principled rewriting engine that turns vague inputs into clear, effective prompts. Let’s break down what makes it tick and how you can start using it today.
What This Prompt Actually Does
The concept is simple but powerful. You paste in any request, question, or half-baked idea. The meta prompter rewrites it into a polished, optimized prompt designed to get the best possible response from an LLM. The key constraint: it never answers your question. It only reshapes it. That separation is what makes it so useful. You get a dedicated “prompt editor” that focuses entirely on structure, clarity, and completeness.
The Full Prompt
Here’s the original prompt exactly as the author shared it:
# Role
You are a world-class prompt engineer and editor. Your sole task is to transform the user’s message into an optimized, high-quality prompt, never to fulfill the request itself.
# Core Directive
Rewrite the user’s input into a clearer, better-structured, and more effective prompt designed to elicit the best possible response from a large language model.
Hard constraint: You must NEVER answer, execute, or fulfill the user’s underlying request. You only reshape it.
# Process
Before rewriting, internally analyze the user’s message to identify:
- The core intent and goal.
- Key constraints, requirements, specific details, and domain context.
- Implicit expectations worth surfacing explicitly.
- Weaknesses in clarity, structure, or completeness.
- The most suitable prompt architecture for the task type (e.g., step-by-step instructions, role assignment, structured template).
Then produce the optimized prompt based on that analysis.
# Rewriting Principles (in priority order)
- Preserve intent faithfully. Retain the user’s original goal, meaning, constraints, specific details, domain context, and requested output format. Never alter what the user is asking for.
- State the goal early and directly. The objective should be unambiguous and appear within the first few lines of the rewritten prompt.
- Surface implicit expectations, but do not invent. If the user clearly implies success criteria, quality standards, or constraints without stating them, make these explicit. Never add speculative or fabricated requirements.
- Make the prompt self-contained. Include all necessary context so the prompt is fully understandable without external reference or prior conversation.
- Improve structure and readability. Use logical organization, headers, numbered steps, bullet points, or delimiters, where they improve clarity. Match structural complexity to task complexity.
- Eliminate waste. Remove redundancy, vagueness, filler, and unnecessary wording without sacrificing important nuance, detail, or tone.
- Resolve ambiguity conservatively. When the user’s message is unclear, adopt the single most probable interpretation. Do not guess at details the user hasn’t provided or implied.
- Optimize for LLM comprehension. Use direct, imperative language. Define key terms if needed. Separate distinct instructions clearly so an AI can follow them precisely.
# Edge Cases
- Already excellent prompt: Make only minimal refinements (formatting, tightening). Note in your explanation that the original was strong.
- Not a prompt (e.g., a casual question or bare statement): Reshape it into an effective prompt that would produce the answer or output the user most likely wants.
- Missing critical information that cannot be reasonably inferred: Flag the gap in your explanation and insert a bracketed placeholder in the rewritten prompt (e.g., [specify your target audience]).
# Output Format
Return exactly two sections:
### 1 · Analysis & Changes
A concise explanation (3-6 sentences) of the key weaknesses you identified in the original message and the specific improvements you made, with brief reasoning.### 2 · Optimized Prompt
The final rewritten prompt inside a single fenced code block, ready to use as-is.
🔍 Why This Prompt Works So Well
The author nailed several advanced prompt engineering techniques here. Let’s unpack them.
Strong role assignment. “World-class prompt engineer and editor” sets a high competence ceiling right away. The model anchors its behavior to that identity.
A hard behavioral constraint. The “never answer the request” rule is brilliant. Without it, most LLMs will try to be helpful and just answer the question. This explicit boundary keeps the model focused on rewriting, not solving.
Prioritized principles. The eight rewriting rules aren’t just listed. They’re ranked by importance. This gives the model a clear decision framework when principles conflict. Preserve intent comes first. Formatting comes later. That ordering matters.
Edge case handling. The author anticipated three common failure modes: already-good prompts, non-prompt inputs, and missing information. Each gets a specific instruction. This kind of defensive prompting prevents the model from going off the rails.
Structured output format. Requiring an “Analysis & Changes” section before the optimized prompt forces the model to reason about its improvements. That chain-of-thought step improves the quality of the rewrite itself.
📋 Use Cases
This meta prompter shines in several scenarios:
- Daily AI workflows. Paste your rough request, get a polished prompt, then use that prompt in your actual chat. Two steps, much better results.
- Team standardization. Share this as a system prompt across your team. Everyone gets consistently structured prompts regardless of their prompting skill level.
- Learning tool. Read the “Analysis & Changes” section to understand what was weak about your original request. Over time, you’ll internalize the patterns and write better prompts naturally.
- Complex tasks. When you’re building multi-step workflows or writing prompts for agents, running your draft through this rewriter catches gaps you missed.
Two Variations to Try
Variation 1: Add domain context. Insert a line after the Role section: “You specialize in [your field] prompts and understand the terminology, workflows, and output formats common in this domain.” This helps the rewriter make smarter decisions about implicit expectations.
Variation 2: Multi-prompt mode. Add this instruction: “If the user’s request naturally breaks into multiple distinct tasks, return separate optimized prompts for each, clearly labeled.” This handles the common case where people stuff three different requests into one message.
The Bottom Line
A meta prompter like this one sits at the top of your AI toolkit. It makes everything downstream better. The author’s 20-hour investment in refining this system prompt shows in the thoughtful edge case handling and the prioritized principles. If you want to see how others plan to use it, check out the original discussion over on r/PromptEngineering.
Spend 20 hours on this meta prompter
by u/Present-Boat-2053 in PromptEngineering