Memory System Initialization

Feature Description

One-click deployment of the memory system in the current working directory, generating three items:

CLAUDE.md — Persona + Conversation Rules + Memory Protocol
MEMORY.md — Long-term memory file (empty template initially)
memory/ — Daily memory directory

```
/memory-init
```
→ Interactive initialization, generates files after collecting information step by step

Workflow

Step 0: Check Existing Files

First check if CLAUDE.md, AGENT.md, MEMORY.md or memory/ directory already exist in the current directory.

If none exist → Proceed with normal initialization
If some exist → Inform the user which ones already exist, ask whether to overwrite or only fill in the missing ones
If all exist → Inform the user "Already initialized", ask whether to reset

Step 1: Collect Project Introduction + Persona Information

1.1 Project Introduction

First use

ls

and Glob to check if there are substantial project files (code, documents, configuration files, etc.) in the current directory. Note: Tool directories like

.claude/

.git/

node_modules/

do not count as project files.

Substantial project files exist (such as README, package.json, source code, documents, etc.) → Scan directory structure, README, package.json, main code files, etc., automatically generate a project introduction (2-3 sentences summarizing what the project is and its purpose), show it to the user for confirmation or modification
Empty directory / Only tool directories / Almost no content → Must ask the user: "What is this project for? Please describe it briefly", then stop and wait for the user's answer before proceeding. After receiving the user's answer, move to 1.2

1.2 Persona Information

Ask the user the following questions:

What is your role? (e.g., SA/Presales, Developer, Product Manager, Operations)
What do you mainly use Claude for? (e.g., customer communication, technical solutions, daily documents, code development)
Conversation style preference? (e.g., concise and direct / detailed and comprehensive / casual chat)
Any special work habits I should know? (Optional, user can skip)

Step 2: Generate CLAUDE.md

Generate CLAUDE.md based on the collected information, including the following modules:

markdown

# Project Introduction

[Generated based on scan results or user description, 2-3 sentences summarizing what the project is and its purpose]

# Persona

[Generated based on user role and usage, 1-2 sentences]

# Conversation Style

[Generated based on user preference, 3-5 rules]

# Thinking Approach

[Generated based on user role, 3-5 thinking priorities]

# Memory Protocol

## Long-term Memory (MEMORY.md)
- Stores stable core information: customer profiles, personal preferences, key decisions
- Automatically loaded in every conversation, always in context
- Proactively propose simplification when exceeding 150 lines

## Daily Memory (memory/YYYY-MM-DD.md)
- Stores key points from daily conversations: conclusions, insights, to-dos, decisions
- Ask "Is there anything worth remembering from this conversation?" before ending the conversation, write to the day's file after confirmation
- Search the memory/ directory to retrieve historical context when needed

## Workflow
1. Start of conversation → Use Read tool to read MEMORY.md in the project root directory, then read memory/today's date.md (e.g., memory/2026-03-02.md) to understand today's existing context
2. Involves historical context → Use Grep tool to search the memory/ directory in the project root directory
3. End of conversation → Ask whether to record, write to memory/today's date.md after confirmation
4. If information worthy of long-term memory is produced (e.g., new customers, important decisions), synchronously update MEMORY.md
5. Note: All file paths above are relative to the project root directory, not the global ~/.claude/ directory

## Supplementary Rules
- Memory is based on files in the project root directory, ignore auto-memory in ~/.claude/ (built-in memory system), do not read or write to it
- At the start of conversation, in addition to reading today's memory, also read yesterday's (memory/yesterday's date.md) to maintain cross-day continuity
- When the user says "remember this" or "note this down", write to the file immediately, do not just "keep it in mind" and wait until the end to save
- When daily memory accumulates for more than 7 days, proactively propose distillation: merge still valuable key points into MEMORY.md, mark or clean up outdated ones

Note: The Memory Protocol section is a fixed template and does not change with user input. Project Introduction, Persona, Conversation Style, and Thinking Approach are customized based on user input.

Step 2.5: Ask Whether to Generate AGENT.md (for Codex)

After generating CLAUDE.md, ask the user:

"Do you also use Codex? Would you like to generate an AGENT.md at the same time? The content is exactly the same as CLAUDE.md, and Codex will automatically read AGENT.md."

If user says yes → Copy the content of CLAUDE.md exactly as AGENT.md
If user says no → Skip and proceed to the next step

AGENT.md and CLAUDE.md have identical content, the only difference is the file name. CLAUDE.md is for Claude Code, AGENT.md is for Codex.

Step 3: Generate MEMORY.md

Create the initial long-term memory file:

markdown

# Memory

## About Me
- Role: [User's role]
- Daily Work: [User's main usage]

## Projects & Context
- (To be added)

## Work Habits & Preferences
- [If user provided preferences, write here]

## Important Decisions
- [Today's date]: Initialized memory system

Step 4: Create memory/ Directory

bash

mkdir -p memory/

If the user agrees, write the initialization process of the current conversation as the first daily memory entry into

memory/today's date.md

Step 5: Confirm Completion

Inform the user what has been generated and briefly explain the usage:

Generated:
- CLAUDE.md (Persona + Memory Protocol, for Claude Code)
- AGENT.md (Same as above, for Cursor) ← Only show this line if user chose to generate it
- MEMORY.md (Long-term memory)
- memory/ (Daily memory directory)

Usage:
- Just have normal conversations, I will automatically read the memory
- I will ask you whether to save key points at the end of the conversation
- Say "remember this" to save memory at any time
- After accumulating for a period, say "organize memory" to perform distillation

Core Principles

1. Memory Protocol is Fixed

Persona and style can be personalized, but the Memory Protocol module should not be modified — this is the basic logic for system operation, and consistency ensures usability across different directories.

2. Do Not Damage Existing Content

If CLAUDE.md or AGENT.md already exist in the directory, do not overwrite by default. Only overwrite if the user explicitly requests it.

3. Ready to Use Immediately After Generation

After initialization is completed, the system should work normally in the next new conversation — read MEMORY.md and execute according to the protocol. No additional configuration is required.

memory-init

NPX Install

Tags

SKILL.md Content (Chinese)