serena-memory

Store and retrieve persistent project knowledge across sessions via Serena MCP memory operations.

3|1|Updated Apr 2, 2015
One-click install
npx skills add https://github.com/ktrysmt/dotfiles --skill serena-memory-ktrysmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: serena-memory
Source: https://github.com/ktrysmt/dotfiles/tree/main/.claude/skills/serena-memory
Command: npx skills add https://github.com/ktrysmt/dotfiles --skill serena-memory-ktrysmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores design decisions, coding conventions, learned patterns, and project-specific context so knowledge survives across sessions and is easily retrievable.

Core Features & Use Cases

  • Persist and categorize memories by adr/, conventions/, context/, patterns/, tasks/ per the memory naming convention.
  • Read, write, list, and delete memories via Serena MCP tools (memory operations).
  • Read code context and understand symbols with context tools.
  • Keep knowledge current by updating memories when decisions change and cleaning up outdated items.
  • Use cases include architecture decisions, coding conventions, project context, and task history across software projects.

Quick Start

Store a memory describing the latest ADR for the authentication flow.

Frequently Asked Questions about serena-memory

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

FAQPage Schema
How do I persist project context and architecture decisions across coding sessions?

You can persist project context and architecture decisions across coding sessions by using a memory system that categorizes entries into structured folders like adr/, conventions/, and context/ for reliable retrieval.

Do I need the Serena MCP memory system to store coding conventions?

Yes, storing coding conventions requires the Serena MCP memory system, which provides the read, write, list, and delete operations needed to manage structured knowledge entries.

What is the best way to manage task history and learned patterns for software projects?

Managing task history and learned patterns is best handled by categorizing memories into tasks/ and patterns/ directories, updating entries when decisions change, and cleaning up outdated items.

Can I organize architecture decision records using a structured memory management approach?

Yes, you can organize architecture decision records by applying a structured memory management approach that categorizes persistent knowledge into specific directories like adr/ for easy listing and retrieval.

How do I retrieve and update outdated business context memories during development?

You retrieve and update outdated business context memories by using memory list and read operations to locate entries in the context/ category, then applying write or delete operations to keep knowledge current.

Why does my project knowledge disappear between different development sessions?

Project knowledge disappears between sessions when it is not persisted, which can be resolved by writing context, patterns, and decisions to a persistent memory system before sessions end.