Currently, we have a collection named tech_description that is used for retrieving context based on user input.
The goal is to store tech stacks along with their real-world problems.
For example:
- With ReactJS, we want to capture concepts such as lazy loading, pagination, prop drilling, in-memory frontend, vulnerabilities, etc.
- With PostgreSQL, we might capture issues related to scaling, indexing, deployment, etc.
Acceptance Criteria
- Define the structure for
tech_description to store information and support context retrieval.
- Update prompts to clearly differentiate between user-driven question generation and auto-generation.
- Write new prompts that support
tech_description.
- Add functionality to update, delete, and add
tech_description entries in ChromaDB, using an authorized endpoint with admin access.
Currently, we have a collection named
tech_descriptionthat is used for retrieving context based on user input.The goal is to store tech stacks along with their real-world problems.
For example:
Acceptance Criteria
tech_descriptionto store information and support context retrieval.tech_description.tech_descriptionentries in ChromaDB, using an authorized endpoint with admin access.