memory-playbook

sigridjineth's avatarfrom sigridjineth

Cross-session persistence for user preferences, implementation guide for Memory feature.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 15, 2025
[Memory and Context Management]

When & Why to Use This Skill

The Memory Playbook skill provides a comprehensive implementation guide for enabling cross-session persistence in Claude. It solves the challenge of fragmented conversations by allowing the agent to remember user preferences, historical context, and workflow states across separate sessions, facilitating long-term relationship building and personalized user experiences.

Use Cases

  • User Preference Persistence: Automatically remembering specific user settings such as dark mode preferences, metric unit usage, or preferred communication styles across different visits.
  • Workflow State Tracking: Maintaining the current status of multi-step processes, such as tracking which stage of an onboarding sequence or project milestone a user has reached.
  • Relationship Context Management: Storing high-level professional details like 'Enterprise customer' or 'Technical buyer' to ensure every interaction is tailored to the user's profile.
  • Historical Interaction Recall: Referencing specific details from past discussions, such as previously mentioned budget constraints or technical issues, to provide continuity in long-term support or consulting.
namememory-playbook
descriptionCross-session persistence for user preferences, implementation guide for Memory feature.

Memory Skill

When to Use

  • Questions about remembering across sessions
  • "What if user comes back tomorrow?"
  • Cross-conversation persistence
  • User profile/preference storage
  • Long-term relationship building with users

Key Feature: Memory

Memory lets Claude remember information across separate conversations.

Core Capabilities

  1. Cross-session persistence: Remember user context between visits
  2. Structured storage: Organize memories by category
  3. Selective recall: Retrieve relevant memories for each conversation
  4. Privacy controls: User-managed memory deletion

Memory vs Context Editing

Feature Context Editing Memory
Scope Within one conversation Across conversations
Lifetime Session Persistent
Use case Long single chats Returning users

Common Use Cases

  1. User preferences: "John prefers dark mode, uses metric units"
  2. Past interactions: "Last discussed budget concerns on Dec 1"
  3. Workflow state: "User is in step 3 of onboarding"
  4. Relationship context: "Enterprise customer, technical buyer"

Response Guidelines

  1. Clarify the need: Within-session or cross-session?
  2. If cross-session: Recommend Memory
  3. If within-session: Context Editing is sufficient
  4. Combine both: For power users, use both together