Hi Cursor team & folks! How can we tweak our codebase to help Cursor with code completion and generation. Any templates or advice for .cursorrules? Should one identify key files (like READMEs, decision records, documentation, dependency & version files, and end-user test scenarios) to enhance model performance? Can we in them (or should we duplicate their content to .currsorrules?)
Can you publish a simple test harnesses that we can experiment with?!
I saw some posts about folks with .cursorrules suggestions, but how do we know what really works? Not sure we have any official, vetted or measurable results.
What size project (number of files, lines, or “tokens”) is too big for cursor to have context on. Would appreciate some tips here…
Thanks!