engineering was a technique for obtaining simple outputs from simple inputs To achieve more complex outputs, we need context management techniques for more complex inputs Context Engineering: Bringing Engineering to Prompts 9
AI models have context windows of 200k to 1M tokens Components: ・System Prompt ・Memory documents ・Tool information (e.g. MCP) ・User Prompt (Prompt Engineering) ・Conversation (LLM input, output) .etc Context Engineering for Agents 10
・Expanded context windows Challenges ・Context Distraction ・Multi-turn conversation Issue ・Lost in the middle ・Context Window Overflow .etc… Even with expanded context windows, not all problems are solved. Instead of waiting for AI evolution, we need to think context engineering Cline v3.25 Context Engineering: Bringing Engineering to Prompts 11
List) Clear prioritization Task granularity adjustment Provide only relevant information Information segmentation Limit information sources Discard/compress unnecessary context Periodic reminders of important information External memory file creation Create guardrails outside context Automated execution scripts .etc… Too much to do!!! Context Engineering for Agents Context Engineering for AI Agents: Lessons from Building Manus 13
it’s difficult for individuals and teams to set up development environments while being conscious of these approaches🤔 Kiro supports context engineering 14
specification Requirements definition (requirements.md) Design specification (design.md) Task list (tasks.md) AI agents provide planning design templates and execution support 【Context Engineering Benefits】 Reduce irrelevant information to counter Context Distraction Appropriate execution granularity to prevent Lost in the middle and Multi-turn issues 16
for Agents Context Engineering 12 Factor Agents: Own Your Context Window Cline v3.25 Kiro in Context Engineering Context Engineering for AI Agents: Lessons from Building Manus Claude Code Spec Oikon’s documents: Kiro Steering Kiro and AI Tools Trends in AI Coding Tools X Post 21