agentleFS
manuscomanusco/resonance/.cursor/rules/resonance.mdc

resonance / rules

Cursor rule38 starsChanged 24 days agoMITView on GitHub

Resonance operating standard and project memory

The file

Files
resonance.mdc
---
description: Resonance operating standard and project memory
alwaysApply: true
---

Follow the Resonance operating standard in `AGENTS.md` in full. At the start of every session, read the project memory before acting: `AGENTS.md`, `.resonance/01_state.md`, `.resonance/02_memory.md`. They carry the project's state and its accumulated lessons; load any linked leaf file relevant to the task, and never solve the same problem twice. Do not edit this file by hand; the Forge regenerates it.

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.