Field Notes

Context Engineering Is Replacing Prompt Engineering

2026-05-125 min readAIDesignSystems

The frontier is moving away from clever wording and toward the design of what the model can see, retrieve, compress, and ignore.

Prompt engineering was always partly real and partly theater.

Yes, wording matters. Framing matters. Instruction clarity matters. But a huge amount of what people called prompting was really an attempt to compensate for deeper weaknesses in the system around the model.

The context was wrong. The files were missing. The tool output was too noisy. The conversation had become bloated. The useful evidence was trapped behind bad retrieval or buried inside a giant dump of tokens.

So people kept polishing the sentence as if sentence polish were the main lever.

That era is fading.

The more capable tools are getting, the more obvious it becomes that the durable advantage is not who can write the most ceremonial request. It is who can shape the informational environment around the model.

This is a much more interesting discipline.

Context engineering asks different questions:

  • Which sources should load automatically?
  • What should be summarized into a file instead of pasted into the thread?
  • Which tools deserve minimal outputs?
  • When should state be carried forward, and when should it be dropped?
  • How do we preserve signal without letting the conversation drown in its own exhaust?

That feels much closer to real systems design.

It also feels more adult. Prompt engineering encouraged a kind of sorcerer mindset, as if fluency with incantation were the path to leverage. Context engineering is less mystical and more architectural. It asks you to understand the task, the information surface, the failure modes, and the cost of confusion. In that sense it brings AI work back into contact with disciplines we already know: information design, interface design, knowledge management, and systems thinking.

It also has a useful side effect: it makes the human more honest. You can no longer pretend the model failed because the magic words were off by three degrees. Often the failure lives in the surrounding architecture. Bad context in, expensive confusion out.

This is one reason the newest agent products feel different. Their best ideas are not just in the model weights. They are in the harness. File references instead of pasted blobs. Tool outputs written to disk. Selective retrieval. Structured memory. More disciplined exposure to the world.

The practical result is that better AI use starts looking strangely similar to cleaning your room before trying to think. Name the folders. Reduce the clutter. Put durable things where they can be found again. Stop making the system re-live every previous conversation just to access one useful sentence. A lot of intelligence work, human or machine, improves when the surrounding environment stops behaving like a junk drawer.

In other words, capability is becoming environmental.

That is a healthier place to work from because it mirrors how people actually think. We do not perform well because someone delivered the perfect sentence into empty space. We perform well when the room is arranged well enough for thinking to happen.

AI is getting the same lesson.