Audit and repair a Basic Memory knowledge tree — misplaced rendering inputs, missing or inconsistent frontmatter, notes absent from the graph, and file names that break the project convention. Use when the user asks to check, audit, clean up, or migrate existing documentation.
A project rule for using a memory-bank/ folder as structured project memory. Before working, the agent must read specified context files and follow a staged workflow from task definition through building and archiving.
The .cursor/notes folder contains notes about this project. The notes form a knowledge base about the project to be used by the AI Agents working on the project. They should help you when working with the same code again in the future.
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
Persistence rule: Decisions live in ADRs, multi-step work lives in plans, deferred work lives in backlog, retrospection lives in evals. Chat memory is session-scoped and lost when the conversation ends. If you find yourself relying on chat memory to track a decision, plan, or follow-up — write the document instead.
BeeWeave skill-based framework for building and maintaining knowledge bases. Use these rules whenever engaging with the vault, wiki, ingestion, or knowledge management.
The main goal of this MCP is to save tokens in complex Antigravity tasks by allowing OpenCode to refine prompts and perform preliminary analysis before sending the final instructions to the main model.