Prompt Engineering vs Context Engineering
People often think context engineering is a new name for prompt engineering. Prompt engineering is about the words in one prompt. That is the task, the examples and the format. Context engineering is about all that goes in the window each time. That takes in files, search results, tool output and the chat so far. In agents, most of that text was never typed by a person.
Prompt Engineering
You write a prompt, test it and fix it. You stop when the answers are good.
Prompt engineering is the work of writing and testing prompts until a model gives good answers every time. You try a prompt, read what comes back, and change the wording, the examples or the format. Then you test it again on many inputs, not just one. Small changes can make a big difference. It is how teams get steady results from a model without training it.
Context Engineering
Picking what a model sees for each task, and in what order.
Context engineering is choosing all that a model sees in its context window for each request. That covers the rules, the chat so far, files, search results and what tools sent back. The window has a limit, and models use some parts better than others. So the job is to put in what helps, leave out what does not, and set it in a good order. It grew out of prompt engineering. Apps now feed models far more than one prompt.
In one line
- Prompt Engineering
- You write a prompt, test it and fix it. You stop when the answers are good.
- Context Engineering
- Picking what a model sees for each task, and in what order.