memory-sync

Persist session-derived context to the memory layer in CLAUDE.md.

5|Updated May 12, 2026
One-click install
npx skills add https://github.com/ramboz/jig --skill memory-sync-ramboz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-sync
Source: https://github.com/ramboz/jig/tree/main/skills/memory-sync
Command: npx skills add https://github.com/ramboz/jig --skill memory-sync-ramboz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist session-derived context to the memory layer, ensuring continuity across interactions.

Core Features & Use Cases

  • Persist session-derived context to memory (glossary, learnings, inbox) using deterministic file I/O.
  • Auto-surface capture at session end and self-healing of missing memory structures.
  • Supports adding terms, learnings, and inbox items, with a hot CLAUDE.md cache for frequently used terms.

Quick Start

When you want to save context, run memory-sync to persist terms, learnings, or notes to the memory layer.

Frequently Asked Questions about memory-sync

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

FAQPage Schema
How do I persist context across sessions so I don't lose my project learnings?

To persist context across sessions, you can save session-derived glossary terms, learnings, and inbox items to a memory layer using deterministic file I/O. This ensures your context survives between interactions without manual copying.

What is the best way to manage a glossary and keep frequently used terms in a hot cache?

Managing a glossary and hot cache involves adding terms to memory and promoting high-frequency terms to a hot cache. This approach automatically surfaces your most used definitions at the top level for immediate access.

How do I save notes and inbox items during a session without interrupting my workflow?

You can save notes and inbox items by running a memory synchronization process that applies idempotent writes. It features auto-surface capture at session end, allowing you to store context safely without interrupting your active workflow.

Do I need to manually create memory directories before saving session context?

You do not need to manually create memory directories before saving session context. The persistence layer includes self-healing of missing memory structures, automatically bootstrapping the required scaffolding for deterministic writes.

Can I bootstrap a shared memory scaffolding for my team to ensure context continuity?

You can bootstrap shared memory scaffolding for your team using a lightweight team-check workflow. This establishes a common persistence layer for glossary terms and learnings, ensuring project context continuity across different team members.