IICTPIICTP

Blog / Guides

Applied AI26 October 20265 min read

Prompt engineering in 2026: beyond prompts, context engineering

Writing a good prompt matters, but in a real system the prompt is only part of what the model sees. Context engineering is the wider job: deciding everything that goes into the model’s context for a given call.

In this post
  1. What goes into context
  2. Principles
  3. Test the prompt like software
  4. Treat outside text as untrusted
  5. Sources and further reading

What goes into context

  • Instructions and role.
  • The user’s request and recent conversation.
  • Retrieved documents and tool results.
  • Examples of the desired output.
  • Constraints and output format.

Principles

  • Be specific. State the task, the audience and the format.
  • Show, don’t just tell. A few good examples beat a long description.
  • Keep it relevant. More context is not better context; irrelevant text can mislead the model.
  • Order matters. Put the most important instructions where the model will weigh them.
  • Version it. Prompts are code: review, test and track them.

Test the prompt like software

Keep a set of inputs with expected qualities, run every prompt change against it, and look at regressions as well as improvements.

Treat outside text as untrusted

Documents and web pages can contain instructions aimed at the model. Separate trusted instructions from untrusted content, and never let retrieved text widen what the system is allowed to do.

Sources and further reading

  1. Anthropic. Prompt engineering overview. docs.anthropic.com.

IICTP is a new independent credential and is not ISO/IEC 17024 accredited.

Keep reading

← All posts

Where do you stand?

Find the credential that fits the work you do.