-
Treat the current working directory as the target project unless the user gives another path.
-
Do not overwrite an existing .memory/ directory unless the user explicitly asks for force/overwrite.
-
Prefer the bundled installer from this skill directory. Use the known skill path if the tool exposes it; otherwise try the global paths created by the installer:
python <skill-dir>/scripts/install-memory.py --dest .
python "$HOME/.codex/skills/agent-memory/scripts/install-memory.py" --dest .
python "$HOME/.claude/skills/agent-memory/scripts/install-memory.py" --dest .
python "$HOME/.config/opencode/skills/agent-memory/scripts/install-memory.py" --dest .
python "$HOME/.gemini/skills/agent-memory/scripts/install-memory.py" --dest .
In Claude Code, ${CLAUDE_SKILL_DIR} may be used as <skill-dir>. If python is unavailable, try python3 or py. If the user asked to replace an existing .memory/, add --force.
-
If the bundled script cannot run, manually copy assets/memory-template/.memory into the target project as .memory, then create or update these root files:
AGENTS.mdCLAUDE.mdGEMINI.md
-
The root instruction files must contain this block, or an equivalent existing reference:
# 记忆
命中对应`记忆存储规则`自动更新对应记忆中
@.memory/AGENTS.md
## 用户偏好
@.memory/user-memory.md
-
If a root instruction file already exists and already references .memory/AGENTS.md and .memory/user-memory.md, leave it unchanged.
-
If a root instruction file exists but lacks the memory references, append the memory block instead of replacing the user's content.
-
Finish by reporting whether .memory/ was installed, kept, or replaced, and which instruction files were created or updated.
-
Before ending the turn, infer the user's primary communication language from the current conversation and project files. Ask in that language whether to initialize .memory/user-memory.md. Do not write user memory before the user confirms.
-
If the user confirms, ask one compact initialization question group adapted to the project context. Include:
- Whether the inferred primary communication language is correct.
- The user's role or responsibility in this project.
- Main programming language, stack, and experience level. If the project reveals likely stack details, mention them as a hypothesis for confirmation.
- Preferred collaboration style: discuss first, implement directly with reasonable assumptions, or ask before risky choices.
- Preferred output style: concise, detailed, code-first, explanation-first, Chinese/English/bilingual, etc.
- Implementation, verification, and git preferences: when to run tests, whether to stage/commit, and what needs confirmation.
- Memory boundaries: anything the user does not want stored as long-term user memory.
-
After the user answers, update .memory/user-memory.md from the template. Preserve useful existing content, merge rather than replacing non-template memory, and use absolute timestamps in yyyy-mm-dd hh format.
