How to properly reference Cursor's vectorized documentation system in markdown files?

How To
1

I’m trying to understand how to properly reference and access Cursor’s vectorized documentation system, particularly from within markdown files.

Currently, I’m experimenting with syntax like:

@docs/category/topic

Questions:

  • Is there a definitive list of available documentation categories and paths?

  • How can I discover valid documentation paths (beyond intellisense suggestions in chat)?

  • What’s the correct syntax to ensure I’m accessing the vectorized documentation system rather than just static files?

  • Does the documentation reference syntax work differently in markdown files compared to direct chat interactions?

I’ve found that using @ with file paths works for linking files, but I’m specifically interested in accessing Cursor’s rich documentation feature. Any guidance on best practices or documentation about the documentation system itself would be greatly appreciated!

Current project setup:

  • Using markdown files to document various features

  • Need to reference official documentation programmatically

  • Want to leverage Cursor’s vectorized documentation capabilities

Thanks in advance for any help or pointers to relevant documentation!

2

If your docs are local Markdown files in your project directory, these are not ingested into the normal documentation system used for online, scraped docs. You can always @ either a subfolder of your docs or a specific file for the AI to have it as context, which will serve a similar purpose as the documentation system.