Filed on behalf of Amr Elsayed.
Problem
As projects grow, providing adequate context to AI without breaking context window limits becomes impossible. AI needs to understand APIs, database schemas, components, and existing patterns but can't hold all this information.
From Amr
"The trick is in how to provide proper context without breaking the context window during the planning phase"
Requirements
AI should know at minimum:
- What does each API do?
- What is the purpose of each table/column in the database?
- What is each screen/page/component responsible for?
- How to use existing IP when building new features
Proposed Solution
- Implement incremental context loading strategies
- Create summarized project knowledge base
- Develop selective context inclusion based on feature requirements