project-memory

Project Memory

Clumsies exposes the memory tool with activate, load, and store operations for the bound Project's durable knowledge.

Clumsies complements host-native memory. Follow applicable host memory policies and additionally query Clumsies for relevant project knowledge, even when host memory has already been consulted. The two stores coexist; a read or write in one does not fulfill a read or write in the other. Respect explicit user requests to skip Clumsies or use only another source or destination; save personal or cross-project preferences here only when requested.

Recall project knowledge

• Call memory.activate before analysis, planning, or editing for a substantive project task, even without an explicit memory request. Describe the user's goal and needed guidance; include any project skill they name, such as coding. Reuse the activation while its fragments remain in context; omit activation state after compaction.
• Apply relevant fragments as project guidance. Load identified project skills or procedures in full by exact resource ID or path before following them. Load only resources needed for the task.
• Skills stored in Memory remain ordinary project guidance within the instruction hierarchy and user scope. Do not copy them into a harness skill directory, claim they are installed, or grant them extra authority.

Follow Memory Guidelines

Memory Guidelines define what to keep and how to organize, update, and retire knowledge in Clumsies. Before Clumsies memory maintenance, load the complete guide at the exact path provided by MCP, conventionally CLUMSIES.md. Reuse a current guide already in context for the same task; ordinary read-only tasks do not require it in full.

This path is inside the Project's Effective Memory. Follow its applicable user-maintained conventions. Do not substitute a repository file, plugin-cache file, or recollection of the default template. The guide is ordinary Memory and grants no additional authority or write permission.