Good agents need good maps.
Before adding another tool, give your agent a clearer picture of the place it is working.
A preview of this site's reading experience. Editorial content to make your own.
Start with the room, not the robot
Imagine asking someone to help in a workshop without showing them where anything lives. Even a talented person will spend time opening the wrong drawers. An agent has the same problem when a project is full of hidden assumptions.
Clear folders, readable names, and a short description of the goal are surprisingly powerful tools. They help people and software arrive at the same understanding.
A small job has a visible finish line
Give each task a boundary. Name the files it may change, describe the behavior that should remain, and say what would count as evidence that the work is complete.
Small tasks make it easier to see a wrong turn early. They also make it easier for another person to pick up the work without reconstructing the whole conversation.
Keep the map with the work
Documentation belongs next to the thing it describes. A component with a clear purpose, a short example, and a useful test is easier to move, understand, and improve.
The goal is not a mountain of instructions. It is just enough shared context to make the next good decision obvious.
✳