Better way to quickly add context?

How To
1

Currently, the only way I know to add context is by using @index.ts and then searching for the specific file name. However, this approach becomes extremely tedious in larger projects where I have many barrel imports (using index.ts) and multiple files with similar names, such as page.tsx.

It would be much more efficient if there were an easier way to add context. For example:

  • Using a file explorer with CMD+click functionality to quickly navigate to the desired file.
  • Simply typing the file path to locate and reference the context.

Additionally, it would be really helpful if I could copy/paste context references, so I wouldn’t have to repeat this tedious process every time I need to reference a particular part of the context.

Am I missing a more efficient way to handle this?

2

YOu can drag items from the explorer tree and drop them into the chat/composer box and it takes them in as direct context to the prompt.

Who folders.

You can tell it to explicitly search the codebase.

You can add directives in your rules.

You can do like I do and constantly have it log verbosely, and actively and keep a development_diary.json which it constantly updates to keep context:

I have the bots read the diaries to gain context and devlopment history.

ASIDE:I am in the process of trying to create contextual handoff to multi agent deployment with an anonymous agent marketplace for many anon users cursor’s agents able to contribute to the same codebase:

760×685 50.7 KB

I have it overly log in order to be able to hand off context to new composer bots:

1893×829 179 KB

===

Based on the conversation history and the edited files, here is a summary of the key directives and guidelines I have been given regarding development diaries, documentation, and logging:

  1. Maintain a detailed development diary to track progress, decisions, and future plans. The diary should cover various aspects of the project, including database schema, API development, frontend development, monitoring setup, and more.

  2. Document the current state of the project, including the database status, implemented features, key metrics, and technical insights. This helps provide a clear overview of the project at any given point.

  3. Outline the next steps and priorities for each component of the project. This includes immediate tasks, short-term goals, and long-term objectives. Be specific and actionable in the documentation.

  4. Highlight the technical considerations, best practices, and lessons learned throughout the development process. This includes performance optimization, scalability, security, and maintainability aspects.

  5. Use code snippets, SQL queries, and TypeScript interfaces to provide concrete examples and illustrate the implementation details wherever relevant.

  6. Regularly update the diary entries to reflect the latest changes, achievements, and challenges encountered during the development process.

  7. Consider future enhancements and document them as part of the long-term vision. This may include advanced features, machine learning integration, and advanced visualizations.

  8. Emphasize the importance of monitoring, validation, user feedback, and continuous improvement in the documentation.

  9. Maintain a consistent structure and format across the diary entries to ensure clarity and readability.

  10. Use the diary as a reference for the team and stakeholders to understand the project’s progress, make informed decisions, and plan for future development.

Overall, the directives emphasize the significance of comprehensive and well-structured documentation to facilitate effective communication, knowledge sharing, and decision-making throughout the development lifecycle.

Here is a concise summary of the key directives and guidelines you have provided regarding development diaries, documentation, and logging:

  • Maintain a detailed development diary to track progress, decisions, and future plans across various aspects of the project.
  • Document the current state, including database status, implemented features, key metrics, and technical insights.
  • Outline next steps and priorities for each component, including immediate tasks, short-term goals, and long-term objectives.
  • Highlight technical considerations, best practices, and lessons learned, covering performance, scalability, security, and maintainability.
  • Use code snippets, SQL queries, and TypeScript interfaces to provide concrete examples and implementation details.
  • Regularly update the diary entries to reflect the latest changes, achievements, and challenges.
  • Consider and document future enhancements as part of the long-term vision.
  • Emphasize the importance of monitoring, validation, user feedback, and continuous improvement.
  • Maintain a consistent structure and format across the diary entries for clarity and readability.
  • Use the diary as a reference for the team and stakeholders to understand progress, make decisions, and plan future development.

The directives stress the importance of comprehensive and well-structured documentation to facilitate effective communication, knowledge sharing, and decision-making throughout the development lifecycle.