As a API/SDK provider, I like to learn ways we can make changes to either third-party documentation, SDKs or even templated .cursorrules that I can provide to developers building with third-party API or SDKs to improve developer experience when using Cursor.
Open to suggestions, exploring a few at the moment:
Prepare API / SDK specific .cursorrules
Explore ways to tokenize documentation / SDKs for LLMs
Add documentation to cursor crawler dropdown
Open to suggestions and comments on this as I learn more about this space.
Direct Docs on Cursor:
Also, I noticed that docs can be added directly on Cursor using the @docs command (via “Add New Docs”). I’ve attached a screenshot for reference:
Hi @sanjeed5 - these are some things I’ve explored previously from my early message, I am looking for ways to improve our own surfaces to be better integrated with Cursor.
Imagine a Shopify or Stripe that want to learn better ways to adapt their product APIs for Cursor. So besides Cursor available features, what can be done by a third party API developer.