Part 1 · Foundations
How models actually read your prompt
The concept
The model does not read your prompt the way a person does. It breaks your text into tokens (roughly ¾ of a word each, or 1–2 characters in Arabic) and predicts the next token over and over until it produces a complete answer. It has no memory between separate chats and no access to anything you didn't give it — it only sees what is inside the current context window, the working desk it can look at all at once. Modern models have very large context windows (hundreds of thousands of tokens — a few hundred pages), so length is rarely your problem; specificity is. Because the model is predicting the most statistically plausible continuation of your text, a vague, generic prompt sits in a region of "average writing on the internet," and you get back exactly that: average writing. A precise, detailed, constrained prompt narrows the space of plausible continuations to a small region where only good answers live.
Three practical consequences you should carry into every prompt:
- Vague in, vague out — mathematically, not metaphorically. "Write something good about our agency" has ten million plausible completions. "Write a 90-word LinkedIn post, first person, for the founder of an Egyptian production house, about why clients keep re-shooting bad briefs" has maybe a hundred. Better odds.
- The model cannot ask you what it doesn't know. It will not stop and say "I don't know your client's positioning." It will invent something plausible and confident. Missing context is not returned as an error — it is silently filled with a guess.
- Instruction-following is real but literal. Modern models are trained to obey explicit instructions. They obey what you wrote, not what you meant. "Keep it short" means whatever the model thinks short is. "Maximum 60 words" means 60 words.
There is also a fourth, subtler point: position matters. Instructions at the very start and the very end of a long prompt are followed most reliably. If you paste 20 pages of a contract and then ask a question, put the question both before and after the paste. Middle-of-the-pile instructions get the weakest attention.
Finally, on Arabic: Arabic consumes roughly 2–3× more tokens than English for the same meaning, and models are generally stronger in English on reasoning while being perfectly capable in Arabic on writing. The professional move is often: think in English, deliver in Arabic — i.e., let the model reason and structure in English, then instruct it to produce the final Arabic output. You get English-grade thinking with Arabic-grade prose.
Before → After
Write a tagline for a real estate client.
Why it fails: No client, no project, no audience, no language, no positioning, no length, no quantity, no tone. The model will hand you "Where Luxury Meets Life" — because that is the statistical centre of "real estate tagline."
You're a senior copywriter at an Egyptian ad agency.
Client: Rawasi — a mid-market residential compound in New Cairo.
Buyer: Egyptian families, 30–45, first serious home purchase, financing
over 7–10 years. They are anxious about developer delivery delays.
Positioning: "the developer that actually delivers on time."
Competitors all shout luxury; we want to sound trustworthy, not opulent.
Give me 10 taglines in Arabic, each 2–5 words, plus a literal English
gloss for each. No English loanwords. Avoid the words فخامة, رفاهية, حلم.
Then mark the 3 you'd defend in a client meeting and give me one line
on why for each.
Why it works: The plausible-continuation space is now tiny, and every constraint you set is a constraint the client would have set anyway.
Do this
Take the last prompt you typed into Claude or GPT that gave you a disappointing answer. Don't rewrite it yet. Just annotate it: circle every place where you knew something the model didn't. Client name, audience, deadline, brand rules, what you already tried, what you hate. Count them. That number is your baseline gap — Modules 2 and 3 close it.