Feature request for product/service
Cursor IDE
Describe the request
Vibe coding is all about communicating/scaffolding an intention to the LLM and having it execute on it. Where the LLM “loses the script” is where it trails off, becomes context-blind, etc. But if Cursor had a single window or pane that communicated both to the LLM and to the user that THESE are the PRIMARY DEVELOPMENT DOCS for each of the components of the app that need consistent referencing, then this would be great. This would be more than great… it would position Cursor as the ultimate cutting-edge in vibe coding.
These primary docs would be:
- Uneditable by the LLM
- Referred to like rules
- Automatically correspond to certain files in the app, such that each file is nested under a reference doc
Something like this would help keep the LLM from losing the script, and make it less of a project management job for the vibe coder because the LLM would know what doc to refer to, to ask clarifying questions about (the LLM could even suggest manual edits to the user based on clarifications), and to use as a kind of natural language single-source-of-truth.
Cursor, I know you’re busy. But you finally delivered on my “don’t cross out archived chats” and “make chats pinnable” requests. Now I’m asking for a big one. I believe in you. Now… onward.