memory-synclisted

Persist new context, terms, learnings, and settled lightweight decisions. Use when the user says remember this, save this for later, add to glossary, note this down, or at the end of a session to consolidate what was learned — that goes to the memory layer (CLAUDE.md hot cache, docs/memory/, docs/inbox.md). Also use to record a decision, remember this decision, or write this decision down when the call is a lightweight one shipped outside a spec slice: UI strings, visual and CSS choices, sizes, copy, or translation fixes. Those go to docs/decisions/lightweight-decisions.md via decisions.py. Also auto-fires at session end to surface capture-worthy items. Do not use for updating specs or code comments — those have their own workflows. For a load-bearing or architectural decision, one with rejected alternatives worth recording, or any decision the user wants written up as an ADR, use `/jig:adr-workflow` instead.
ramboz/jig · ★ 4 · Web & Frontend · score 73

Install: claude install-skill ramboz/jig

> Spec 002 (memory layer) is fully closed — all four slices DONE: 002-01 > (explicit-sync), 002-02 (lookup-pattern), 002-03 (auto-detect-hooks), > 002-04 (reconciliation-integration). 002-04's reconciliation integration > is now the Memory-sync gate in the spec-workflow reconciliation checklist. ## What this skill does Persists session-derived context to the memory layer via a deterministic helper. Claude makes the *what / where* decisions; `memory.py` does the file I/O, idempotency, and self-healing of missing memory structure. ## When to invoke - User says "remember this", "save this for later", "add this to the glossary", "note this down", or similar (→ persist flow below). - User explicitly invokes `/jig:memory-sync`. - An unknown capitalized reference appears in the conversation (→ lookup-pattern flow below). - Session-end consolidation (after slice 002-03 auto-trigger ships). - **The session settled a non-spec shipped decision** — a UI string, visual/CSS choice, translation correction, or scoped brand/icon call made *outside* a spec slice (→ lightweight-decision flow below). This is the forcing function for out-of-spec work, which has no reconciliation phase to catch it. ## Lookup-pattern flow When you see a capitalized reference, acronym, or project-specific term you don't recognize, follow this flow **before asking the user**: ``` seen unknown reference X ↓ python3 memory.py lookup "X" . ↓ exit 0 → use the printed definition; do not ask ↓ exit 2 →