Context Engineering

James Phoenix
James Phoenix

The art of structuring information for LLM agents to maximize both token efficiency and comprehension.


Articles

Foundations

Agent Patterns

Prompting Techniques

Context Management

Verification & Testing

Quality Gates & Linting

Development Workflows

Error Handling & Debugging

Model & Provider Strategy

Infrastructure & Tooling

Philosophy & Identity

Planning & Refinement


Core Principles

  1. Own your context window – Structure information deliberately, don’t rely on framework defaults
  2. Deterministic beats non-deterministic – Use code to control what you can, reserve LLMs for decisions
  3. Small, focused agents – Scope agents to 3-20 steps; performance degrades with context growth
  4. Progressive disclosure – Load only relevant context for the current task
  5. Backpressure on output – Compress verbose output; only show errors in full

Key Insight

“Most ‘AI agents’ in production aren’t pure agentic systems. They’re predominantly deterministic code with targeted LLM decision-making.”


Sources


Related

Topics
Agent ReliabilityContext EngineeringCost OptimizationInformation TheoryLLM Mechanics

Newsletter

Become a better AI engineer

Weekly deep dives on production AI systems, context engineering, and the patterns that compound. No fluff, no tutorials. Just what works.

Join 306K+ developers. No spam. Unsubscribe anytime.


More Insights

Cover Image for How to Automate Agentic Engineering Failure-Mode Detection in the SDLC

How to Automate Agentic Engineering Failure-Mode Detection in the SDLC

**Every engineer running Claude Code is already writing a diary of where the SDLC breaks**: every stalled task, every abandoned plan, every loop they gave up on and finished by hand. Nobody uses that diary, because using it means a human reads a colleague’s session, and that is a trust violation no team will accept. Here is how to turn that diary into a working pipeline anyway, without a single person ever reading a transcript.

James Phoenix
James Phoenix
Cover Image for Lights-On vs. Dark Software Factories

Lights-On vs. Dark Software Factories

The difference between the two is not how much code agents write. It’s who verifies it.

James Phoenix
James Phoenix