| This is a great idea, I've been doing something similar at 2 levels: 1. .cursorrules for global conventions. The first rule in the file is dumb but works well with Cursor Composer: `If the user seems to be requesting a change to global project rules similar to those below, you should edit this file (add/remove/modify) to match the request.` This helps keep my global guidance in sync with emergent convention, and of course I can review before committing. 2. An additional file `/.llm_scratchpad`, which I selectively include in Chat/Composer context when I need lengthy project-specific instructions that I made need to refer to more than once. The scratchpad usually contains detailed specs, desired outcomes, relevant files scope, APIs/tools/libs to use, etc. Also quite useful for transferring a Chat output to a Composer context (eg a comprehensive o1-generated plan). Lately I've even tracked iterative development with a markdown checklist that Cursor updates as it progresses through a series of changes. The scratchpad feels like a hack, but they're obvious enough that I expect to see these concepts getting first-party support through integrations with Linear/Jira/et al soon enough. |