most of the time cursor does a pretty good job of understanding the context and content of the different embedded references, at least with gpt-4. the purpose of this post is to unearth best practices for prompt engineering that are specific to cursor.
for example, let’s say that i have documentation, a style guide, and an example. what are the best practices for labeling those
@ differently so that the llm understands the appropriate context? i’ve been doing something like this:
using the style guide @style-guide, and following the example @example, write a @Hugo layout template that does …
any thoughts on this approach? (as additional nuance, this might return very different results with or without the “full codebase context” (cmd + return))
any cursor-specific prompting tricks that others are willing to share?