Repository navigation
Add MemorySync persistent memory cursor rule #377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mdhaseeb343q-pixel
wants to merge
2
commits into
PatrickJS:main
Choose a base branch
from
mdhaseeb343q-pixel:mdhaseeb343q-pixel-patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| description: Scoped persistent memory guidelines for Cursor AI to capture and recall architecture decisions, API conventions, and project constraints across sessions via MemorySync MCP. | ||
| globs: ["**/*"] | ||
| alwaysApply: false | ||
| --- | ||
| # MemorySync Persistent Memory for Cursor | ||
|
|
||
| This rule guides Cursor AI in maintaining persistent, scoped project memory across conversation restarts using the MemorySync Model Context Protocol (MCP) server. | ||
|
|
||
| ## Connection Setup | ||
| Ensure the MemorySync MCP server is configured in `.cursor/mcp.json` or Cursor Settings > Features > MCP: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "memorysync": { | ||
| "url": "https://mcp.memorysync.io/mcp" | ||
| }, | ||
| "memorysync-docs": { | ||
| "url": "https://docs.memorysync.io/mcp" | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## When to Save Memories | ||
| Automatically invoke memory storage when the user or project establishes durable decisions: | ||
| - **Architecture Decisions:** Choice of libraries, state management patterns, routing conventions. | ||
| - **Project Conventions:** Date formatting (e.g., strict UTC ISO-8601), naming styles, error handling structures. | ||
| - **Bug Fixes & Gotchas:** Non-obvious edge cases resolved, pinned package workarounds, deprecated API replacements. | ||
| - **Environment & Secrets:** Key configuration variables needed (never store plaintext secrets or private tokens). | ||
|
|
||
| ## When to Recall Memories | ||
| At the start of new tasks, feature implementations, or refactoring: | ||
| - Query MemorySync for existing decisions scoped to the current project or workspace (`project_id`). | ||
| - Respect recalled decisions rather than guessing or re-implementing contrasting patterns. | ||
| - Cite the memory record ID when applying a recalled rule (e.g., `Applied architecture constraint from memory #mem_...`). | ||
|
|
||
| ## Documentation Search | ||
| When encountering unfamiliar SDK APIs or framework features: | ||
| - Use `memorysync-docs` to search live, verified documentation before generating speculative implementations. | ||
|
|
||
| ## Reference | ||
| - Official Cursor Guide: [docs.memorysync.io/guides/cursor](https://docs.memorysync.io/guides/cursor) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.