agentleFS
Sign inStart free
synamcpssynamcps/synamcps-server/.cursor/rules/syna-brain-memory.mdc

synamcps-server / rules

Cursor rule4 starsChanged 8 days agoApache-2.0View on GitHub

Persist SynaMCPs logic/UI session memory to syna-brain MCP

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

The file

We split this syna-brain-memory.mdc into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a session finishes meaningful SynaMCPs server logic or visual/UI changes, or when the user asks to remember / save chat context, apply …

    line 8
  2. Distinctive:

    Do not store secrets (tokens, private keys, env values).

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
syna-brain-memory.mdc
---
description: Persist SynaMCPs logic/UI session memory to syna-brain MCP
alwaysApply: true
---

# Syna-brain second memory

When a session finishes meaningful **SynaMCPs server logic** or **visual/UI**
changes, or when the user asks to remember / save chat context, apply
`.cursor/skills/save-syna-brain-memory/SKILL.md` and write a summary to the
**user-syna-brain** MCP (`knowledge_save`) as second brain memory.

Also save when wrapping up a design that future sessions should not re-derive
(securebus, data objects, auth, admin UI, MCP tools).

Do not store secrets (tokens, private keys, env values). Prefer searchable
titles and durable facts over full raw transcripts.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free