← Back to context

Comment by satvikpendem

2 days ago

> I have a codebase in Zig and it doesn't understand Zig at all.

> I have another which is embedded C using zephyr RTOS. It doesn't understand zephyr at all and even if it could, it can't read the documentation for the different sensors nor can it plug in cables.

If you use Cursor, you can let it index the documentation for whatever language or framework you want [0], and it works exceptionally well. Don't rely solely on the LLM's training data, allow it to use external resources. I've done that and it solves many of the issues you're talking about.

[0] https://docs.cursor.com/context/@-symbols/@-docs

The Cursor docs indexing works very well and it’s probably the biggest thing missing from Windsurf. The other key is to stop the response when you see something going wrong and go back to your first message to add more context, like adding docs or links to library source files (a url to Github just fine) or attaching more files with types and annotations. Restarting your request with more context works better than asking it to fix things because the wrong code will pollute the probability space of future responses.