serena-memory

Manage persistent Markdown memories via the Serena MCP server.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/sachmata/serena-skills --skill serena-memory-sachmata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: serena-memory
Source: https://github.com/sachmata/serena-skills/tree/main/skills/serena-memory
Command: npx skills add https://github.com/sachmata/serena-skills --skill serena-memory-sachmata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines project knowledge management by providing a robust system for creating, retrieving, and maintaining persistent memories across development sessions.

Core Features & Use Cases

  • Persistent Storage: Store project conventions, architectural decisions, style guides, and other crucial information.
  • Organized Access: Memories are organized by topic using forward slashes, with an option for global, cross-project memories.
  • Use Case: Maintain a global/typescript/style-guide memory that all developers can reference, ensuring code consistency across multiple projects.

Quick Start

Use the serena-memory skill to write a new memory named 'build/commands' with the content '## Build Commands\n- Build: npm run build\n- Test: npm test'.

Frequently Asked Questions about serena-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store persistent project conventions across development sessions?

Persistent project conventions are stored as Markdown-formatted memories using the Serena MCP server, enabling creation, reading, and editing of architectural decisions and style guides across sessions.

What's the best way to manage project knowledge so it survives across sessions?

Managing project knowledge is best done by organizing persistent Markdown memories by topic using forward slashes, with a 'global/' prefix for cross-project information, ensuring structured access and survival across sessions.

Can I share style guides across multiple projects using a global memory?

Yes, you can share style guides across multiple projects by creating a global memory using the 'global/' prefix, such as 'global/typescript/style-guide', ensuring consistency and accessibility for all developers.

How do I create a new memory for build commands?

To create a new memory for build commands, use the memory creation tools to write a memory named 'build/commands' with Markdown content detailing the build and test commands for your project.

Does the memory system support listing and renaming existing memories?

Yes, the memory system supports listing and renaming existing memories, along with reading, editing, and deleting Markdown-formatted memories organized by topic using forward slashes.

When should I not use a 'global/' prefix for my project memories?

You should not use a 'global/' prefix for project-specific memories, as it is reserved for cross-project information; local memories should be organized by topic using forward slashes without the prefix.