Model-neutral context engineering

Choose what the model gets to see.

How do you decide what goes in the context window? Keep the current task, the rules that constrain it, the evidence that would change the answer, and the output contract. Compress bulk that still holds those facts. Drop unlabeled dumps and history that belongs in a store. The Packing List is the desk for that: keep, compress, or drop.

Goal

The user task, success criteria, and decision boundary.

Evidence

Sources ranked by relevance, authority, freshness, and conflict.

Rules

System constraints, policies, formatting contracts, and tool limits.

Memory

Stable preferences and prior decisions, not every historical token.

Output

The shape the answer must take so it can be judged and reused.

Key facts

Context Engineering Guide

  • Context engineering is the design of the full inference payload: task, instructions, evidence, memory, tools, examples, constraints, and output contract.
  • The central rule is curation over dumping: put answer-critical material in the prompt, citations in the audit trail, and everything else behind retrieval.
  • The Packing List at /packing-list/ is the signature desk: keep, compress, or drop each candidate before you fill the window.
  • The site is model-neutral and independent. Claude-specific context-window numbers belong at claudecontext.com, cited and linked.

The signature desk

The Packing List

Four jobs. A pile of candidates. Three bins. Pack an invoice dispute, a failing test, a policy exception, or a paper comparison and watch the working set become a brief instead of a warehouse. Claude-specific window sizes live onclaudecontext.com; this desk stays model-neutral and cares what you selected.

Working set

  • Current question
  • Billing rules that govern plan changes
  • Plan-change ticket from August 3

Compressed spans

  • Twelve-page invoice PDF

Left behind

  • Last forty support tickets
  • Similar billing FAQ pages from retrieval
  • Full CRM account timeline

Why this exists

Curation beats dumping because attention is not uniform.

Long context windows changed what is possible, but they did not remove the need for selection. Research on long-context use repeatedly shows that placement, length, and task complexity change how well models use evidence.

"performance is often highest when relevant information occurs at the beginning or end"
Lost in the Middle: How Language Models Use Long Contexts

Guide map

The context pipeline, page by page.

Each page answers one operational question. Read them in order when designing a new system, or jump to the failure mode you are debugging.

Model-neutral, source-backed

This is about context, not one vendor's prompt style.

Curated Context complements claudecontext.comby staying model-agnostic. Claude-specific context-window numbers belong there, cited and linked; they are not packing rules here. The pages cite research on RAG, long-context behavior, prompt compression, memory systems, and evaluation so the guidance can travel across model families and tooling stacks.

Cite This Page

Curated Context. "Context Engineering Guide." Accessed July 12, 2026. https://curatedcontext.com/

https://curatedcontext.com/