memory-system-assembler

To design a Claude Code memory system, audit open-source memory repositories to identify reusable patterns, then cherry-pick and assemble those patterns into a structured memory design tailored to your workflow using phased rollout plans.

The Claude Code memory layers consist of in-context, CLAUDE.md rules, Memory files, Hooks, Scheduled compaction, External store, and Agent-managed layers, which structure memory persistence and integration across sessions and projects.

The best way to structure memory files and hooks is to enforce phase-based memory planning using artifact templates and integration with file paths like ./memory/ and session hooks, ensuring coherent memory assembly across projects.

Yes, you can audit open-source memory repos to identify reusable patterns that match your workflow, then cherry-pick those patterns to redesign and optimize your existing Claude Code memory system for ongoing use.

Yes, the memory system assembler supports onboarding, memory redesign, and ongoing optimization by guiding phase audits, repo audits, and pattern cherry-picking to assemble a personalized Claude Code memory system.

Assembling a Claude Code memory system generates artifact templates, assembly plans, and phased rollout prompts that guide the integration of cherry-picked open-source memory patterns across your sessions and projects.