So it’s no secret that sometimes cursor can seemingly lose sight of it’s context. It will regenerate existing files and miss some parts of them resulting in deleted code. It will generate routines that already exist and leave you with essentially duplicate code, then get confused about which version it’s supposed to be using. If given too much info in a prompt it will get stuck. So I’ve been thinking about best practices to help with all this.
I’ve seen and used cursorrules and the cursor settings prompt enhancer as has been suggested in this forum and they definitely help.
Focusing in on context and file access, I’m wondering if it really does lose some context or if it’s some form of laziness. Around 500 pages is what sonnet should be able to manage and my apps aren’t that big.
What do you all think, losing context or something else at play.
Regarding access to files, starting a new composer often means even when I drag files into the composer it says something like I can see the like but please give me the contents of the file. Does anyone know how file access is supposed to work? Like are all project files supposed to be available at all times or only open files? Should dragging a file to composer make it’s contents available?
Hoping to nail a few of these annoying behaviours.