Meta context

[pearl lintel]

When a project is getting bigger and you need to clean the context the agent is not aware enough of the structure and starts making mistakes. (this is my experience, might be another cause)

It would be a great idea if the agent would keep a Meta Context that views the app that is being build from a birds eye view. Just knowing how all parts interact and where different functions have their place in the app.

When cleaning up, this meta context would be read and the agent but be much more aware of the complete overview of the app.

And, showing this to a user visually, could improve their prompts to the agent which increases their success rate when building. This leads to happy customers and more customers.

[slim fable]

After clearing I give it the summary as noted in the videos and use this time to optimize the code so it knows all code here is the prompt i used
Review the provided codebase structure and files (e.g., frontend with App.css, index.js; backend with admin_dashboard_test.py, backend_test.py; config files like package.json, Dockerfile, etc.). Identify potential areas for streamlining and removing redundant or unused files, code, or configurations while ensuring the current functionality remains intact. Provide specific suggestions (e.g., unused imports, duplicate files, unminified assets) without modifying the code directly. Focus on improving efficiency and organization, and flag any potential risks or dependencies that should be preserved.