Think of a prompt like a blueprint for a building. The AI is the construction crew. A Redditor over in r/PromptEngineering, u/Ornery-Dark-5844, laid out exactly why this matters and wrapped it all inside what they called an “arcane codex” of prompting principles. Strip away the theatrical mysticism and what’s left is one of the more clearly structured prompt engineering guides I’ve come across.
Here’s the breakdown, translated from dramatic to practical.
🏗️ Lay the Foundation: Role and Context
Every building starts with a foundation. In prompting, that’s Role and Context.
The principle the creator calls “Structural Clarity” is this: the AI doesn’t intuit, it interprets. It works with exactly what you give it. So give it the full picture upfront:
- Who is the AI supposed to be? (a copywriter, a data analyst, a product manager)
- What’s the specific situation it’s operating in?
- What exactly needs to get done?
- What should the output look like when it’s done?
The more specific the role, the sharper the result. “You are a direct response copywriter with 10 years writing for subscription businesses” outperforms “You are a copywriter” by a wide margin. The difference is the same as telling a contractor to build a two-bedroom apartment versus telling them to build something nice.
Skip this and you get the AI’s default mode: a generic, middle-of-the-road response that tries to serve everyone and satisfies no one. Foundation first. Always.
🧱 Build the Walls: Objective and Constraints
Walls give a building its shape. In a prompt, that’s your dominant objective and your constraints.
Here’s where most people lose control: they ask for three things at once, include two conflicting instructions, and then wonder why the response feels scattered. The framework’s answer is simple. Pick one primary objective. Stack any subtasks underneath it in a clear hierarchy. Define what success looks like before you hit send.
Think of it like a job description. The primary objective is the job title. Everything else reports to it. If your objective is “write a compelling subject line,” then tone, length, and format are all subordinate to that goal. Nothing in the prompt should contradict the top objective.
Constraints work in the same direction. Limiting your prompt produces better output, not worse. A river moves faster when it’s contained. Limit the scope, the word count, the format. The quality of the response goes up every time.
🪟 Add the Windows: Format and Output Anchoring
Windows let the right light through and block everything else. In a prompt, that’s your output format: the specific shape, tone, and depth of the response you’re asking for.
This step gets skipped the most. People define the task but forget the form. The result is a wall of prose when you needed bullets, or a five-paragraph essay when you needed one sentence. The Redditor calls this “Output Anchoring.” Whoever doesn’t define the form gets the unpredictable.
Before sending, lock these down:
- What shape should the output take? List, table, code block, paragraph?
- What tone fits the context? Technical, casual, persuasive?
- How much depth is appropriate? Quick summary or a full breakdown?
If you want a response you can paste directly into a document or email, describe that explicitly. “Format this so it can go directly into a client-facing report” changes the output dramatically compared to leaving format undefined.
🔨 The Master Blueprint
For complex prompts, the creator recommends this exact structure. Copy it directly:
[ROLE]
You are...
[CONTEXT]
The situation is...
[OBJECTIVE]
What needs to happen...
[CONSTRAINTS]
What to avoid or limit...
[FORMAT]
How the response should look...
[QUALITY CRITERIA]
What makes this response successful...This isn’t about writing longer prompts. It’s about writing structurally complete ones. A 60-word prompt built on this skeleton beats a 600-word wall of text every time. The structure is the shortcut.
📋 Three Places to Use This Right Now
This blueprint approach delivers fast, obvious results in a handful of common tasks:
- Cold email writing: Role = direct response copywriter. Context = B2B SaaS cold outreach. Constraints = under 60 words, no buzzwords. Format = subject line plus a 3-sentence body. Quality = must include one specific, verifiable pain point.
- Ad hook brainstorming: Role = direct response copywriter. Constraints = no benefit claims without supporting proof. Format = 10 options, numbered, each under 10 words.
- Competitor analysis summaries: Role = senior analyst briefing the CMO. Constraints = plain language, no jargon. Format = 5-point bullet summary, each point under 20 words.
The structure is the same in every case. What changes is the context you plug into it. Once you’ve run it a few times, filling out the blueprint takes under two minutes and saves you three rounds of frustrated back-and-forth with the AI.
One More Trick Worth Stealing
The author tucked this near the end of the codex and it’s the most practical note in the whole thing: reverse engineer prompts from outputs you love.
Found a response that nailed exactly what you needed? Work backwards. Ask yourself: what prompt would produce this specific result? Running that exercise repeatedly, on the outputs you already admire, is where real prompt fluency comes from. Not from collecting templates. From understanding the structure that built the results.
Keep a running doc of your best prompts alongside the outputs they generated. Patterns will emerge faster than you expect, and you’ll stop guessing at structure and start building it on purpose.
The full framework is in the original thread by u/Ornery-Dark-5844 over in r/PromptEngineering. The theatrical presentation is worth reading too. It’s genuinely fun when someone packages solid technique inside dramatic fiction.
📜 CÓDEX ARCANO DA ENGENHARIA DE PROMPT
by u/Ornery-Dark-5844 in PromptEngineering