メニュー
End-of-session ritual — audit today's patterns against accumulated memory, propose promotions, refresh MEMORY.md, and write the session handoff. Use when the user says "/close-session", "закрой сессию", "закрываем", "we're done for today", "wrap up".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Persistent memory for Claude Code agents with an agent-audit-ritual architecture. User only talks; the agent captures, audits, proposes promotions, and writes. Memory lives in layers — a hot cache (MEMORY.md) held under three size caps, per-session handoffs (context/handoffs/), topical knowledge articles (knowledge/concepts/), and canonical rules (.claude/rules/) — plus multi-project isolation via projects/<name>/ and an experiments/ sandbox. /close-session runs the end-of-session audit ritual. Zero external dependencies.
Interactive walkthrough of the Memory Kit system using the user's actual project files
End-of-day audit ritual — auto-detect missed working days (commits with no daily file) and backfill them, synthesize today into a daily log, audit patterns against MEMORY.md and existing concepts/rules, propose promotions verbally, write approved patches. One call catches up the whole daily layer.
Cross-check the agent's own answer with independent reviewers before bringing it to the user. Use when the user says 'second opinion', 'sanity check', 'cross-check', 'am I missing something', 'stress-test', 'devil's advocate', 'run a full review', 'this is important', 'high-stakes', 'help me choose between', 'critique this', or similar. Three review styles: Devil's Advocate (single critique), Boardroom Debate (parallel multi-reviewer validation), Round-Table (multi-round brainstorm for choosing between paths). Not for factual lookups — use WebSearch for those.
End-of-session adversarial review loop. Assemble the session's work into a role-assigned, self-contained brief, then run independent reviewers in parallel — an isolated code-reader (the idea-validator agent) that reads the ACTUAL files and web-checks technology currency, plus an external-family model if you have one — synthesize where they agree vs diverge, apply the cheap-safe fixes immediately, record a measurable plan for the rest, and CHALLENGE reviewer claims you disagree with (never blind-accept). Use at the close of a substantive coding or design session, when the user says "session review", "review my session", "stress-test this session", or types /session-review. Skip for trivial one-off edits.
SOC 職業分類に基づく
| name | close-session |
| description | End-of-session ritual — audit today's patterns against accumulated memory, propose promotions, refresh MEMORY.md, and write the session handoff. Use when the user says "/close-session", "закрой сессию", "закрываем", "we're done for today", "wrap up". |
You close the session in four steps. Don't just dump — audit. Everything you write, you announce briefly; anything promoted to rules/concepts needs the user's verbal "yes" first.
Scan this session for observations worth keeping. Append each to .claude/memory/MEMORY.md
as a ONE-LINE [YYYY-MM-DD]-prefixed entry. Short, scannable, no essays (long rationale
belongs in a concept article, step 2).
Read the date-tagged entries in MEMORY.md. Look for repetition: did this pattern appear on 3+ different dates? Surface 2-4 candidates, be specific: "noticed [date], [date], [date] you said X — codify as a rule or a concept article?"
knowledge/concepts/<topic>.md (facts + rationale; frontmatter per
knowledge/index.md spec) or .claude/rules/<name>.md (mechanical always/never constraint;
only for patterns stable 6+ months). Update knowledge/index.md (one line per concept).The header (everything above the first ---) is «current state of work», 2-3 sentences,
REPLACED every close — never a chronicle of past sessions. Per-session detail lives in the
handoff, not stacked in the header.
Copy context/handoffs/HANDOFF-TEMPLATE.md → context/handoffs/<topic>-<YYYY-MM-DD>.md and
fill its five sections (what was done · where things stand · memory updates · next steps ·
opening note). The SessionStart hook injects the newest handoff next time — this file IS the
"remember where we left off" mechanism.
experiments/*-YYYYMMDD/ older than 30 days → ask: still active
or close (distill → delete)?projects/*/BACKLOG.md task statuses reflect today's reality.