skills.rest
jsamuelsen11
jsamuelsen11COMMUNITY
Explore all skills by this author →
GitHub

memory-conventions

Persist and organize project context across sessions with memory file naming and hygiene guidelines.

Updated Feb 7, 2026
Search Tags:#memory#persistence#knowledge-management#session-context#git-commits#beads-notes
One-click install
npx skills add https://github.com/jsamuelsen11/claude-config --skill memory-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-conventions
Source: https://github.com/jsamuelsen11/claude-config/tree/main/plugins/ccfg-core/skills/memory-conventions
Command: npx skills add https://github.com/jsamuelsen11/claude-config --skill memory-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines when to persist context across sessions and how to organize longitudinal memory (memories, beads notes, and git commits) so knowledge survives beyond individual tasks.

Core Features & Use Cases

  • Establishes when to use Serena memories for cross-session decisions, beads notes for active context, and git commits for traceable changes.
  • Provides memory file naming guidelines, session start protocol, and memory hygiene practices to keep information current and accessible.
  • Supports design decisions, architectural rationales, and task progression across long-running projects, ensuring continuity for future teammates.

Quick Start

Enable the memory conventions to start persisting and organizing context across sessions using the recommended memory types.

Frequently Asked Questions about memory-conventions

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

FAQPage Schema
How do I persist project context across sessions?▼

To persist project context across sessions, apply established memory conventions that organize longitudinal memory, beads notes, and git commits so knowledge survives beyond individual tasks.

What is the best way to organize long-term memory for design decisions?▼

Organizing long-term memory for design decisions requires standardizing when to use Serena memories for cross-session decisions, beads notes for active context, and git commits for traceable changes.

When should I use beads notes versus git commits for session context?▼

Use beads notes for active session context and git commits for traceable code changes, while reserving Serena memories for cross-session design decisions to maintain proper memory hygiene.

How do I maintain memory hygiene in long-running projects?▼

Maintaining memory hygiene in long-running projects involves enforcing memory file naming guidelines, following a session start protocol, and applying practices that keep design decisions current and accessible.

Can I standardize knowledge management for architectural rationales without losing session context?▼

Yes, you can standardize knowledge management by persisting architectural rationales and task progression through structured memory file naming and hygiene practices, ensuring continuity for future teammates.

What are the limitations of relying on git commits for cross-session knowledge management?▼

Relying solely on git commits limits cross-session knowledge management because commits track traceable changes but lack the active context handling of beads notes and the longitudinal persistence of Serena memories.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
odylithodylith
34

odylith-session-context

Preserve and resume Odylith session context across turns.

Official
Intermediate
frznfrggfrznfrgg

onboard

Read memory-bank notes, review recent changes, and write context for AI coding agents.

Community
Intermediate
koasis89koasis89

note

Create and manage notes using OMX persistent memory features.

Community
Basic