Context Engineering
As the task gets longer, the AI starts missing a newly confirmed requirement. What should the next turn include?
Keep the task for this turn first so the Agent can judge which other material is relevant.
Send only what the next turn needs; preserve older clues with a summary and file location.
Keep current requirements and rule carriers visible: Carry the goal, protected scope, and confirmed decisions into the next turn; project rules files (like AGENTS.md, .cursorrules) preserve conventions across separate chats.
Replace repetition with a summary: Keep new decisions and open questions, but reduce repeated chat and old logs to conclusions that still matter.
Read the original only when needed: Large originals do not need to be resent every turn, but their paths and sources must remain available.
You can say this to an AI Agent
This task is long, and you have started missing a newly confirmed constraint. Before continuing, prepare a working context with the current goal, protected scope, approved decisions, relevant files, and open issues. List repeated logs and obsolete attempts as material to exclude, while keeping paths for on-demand retrieval. Show me the result for confirmation before proceeding.
Select page elements for precise AI edits
Click a button, text, or card, note the change, then copy its exact location to AI.
Open Selector Pro website↗