What problem does it solve?
It prevents agents from producing low-quality or incorrect results by ensuring they receive the right project rules, specs, source files, and the most relevant error or test feedback at the right time.
Core Features & Use Cases
- Context hierarchy: Prioritizes persistent rules files, then spec/architecture docs, then relevant source files, then iteration-level error output, and finally conversation history.
- Selective inclusion: Reduces hallucinations and drift by loading only the portion of docs and only the files needed for the current task.
- Confusion & incompleteness handling: Provides concrete patterns for surfacing conflicts and asking for missing requirements instead of guessing.
- Session management: Recommends restarting or summarizing when context grows stale or becomes too large.
- Trusted vs untrusted context: Establishes verification expectations for config, generated, external, or user-provided content.
Quick Start
Use context-engineering to set up a new project session by loading your project rules file (for example, CLAUDE.md), the relevant spec section, the specific source files to change, and only the latest failing test or error output.