A prompt is everything you hand to a language model in one call: instructions, context and the question itself. The model answers by continuing exactly that text, and nothing else.
No jargon, no math
A prompt is the complete text you give the model in a single call, and the model does one thing with it: it continues it. That text usually stacks three layers: a system prompt with the rules of engagement, any context you choose to paste (documents, data, earlier messages), and your actual request. The model has no task menu and no memory of yesterday: it answers from exactly what is in front of it, matching the patterns your text suggests. This is why the same model feels psychic with one prompt and useless with another. Vague input gets a generic answer, because a generic answer is the safest pattern match. Missing context gets invented or ignored. And anything you leave out of the window simply does not exist. Writing a good prompt is less about magic words and more about doing the framing the model cannot do for itself: who is speaking, what material is on the table, what shape the answer must have.
Prompt engineering is the practice of writing prompts so a language model performs a task reliably: clear instructions, the right context, worked examples of the desired output, and tests against real cases before you trust it.
ReadThe system prompt is the standing instruction a language model receives before any user message: it defines the model's role, tone, limits, output format and the tools it may use, and it shapes every answer in the conversation.
ReadThe context window is the model's working memory, measured in tokens: everything in a single prompt (instructions, documents, the conversation so far) must fit inside it, and anything beyond the limit is simply invisible to the model.
Read§ 03
We design and ship AI systems with permissions, logs and human approval. It starts with a 30-minute scoping call.