菜单
Initialize the file-based memory system for the current project. Creates the directory structure and starter files. Use when starting organized work on a new project.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/swannysec/context-keeper --skill memory-init命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | memory-init |
| description | Initialize the file-based memory system for the current project. Creates the directory structure and starter files. Use when starting organized work on a new project. |
| triggers | ["/memory-init"] |
.claude/memory/ already exists
mkdir -p .claude/memory/decisions
mkdir -p .claude/memory/sessions
Ask user (or infer from codebase):
product-context.md - Populate with gathered info:
# Product Context
## Project Overview
<!-- What is this project? What problem does it solve? -->
## Architecture
<!-- High-level architecture description -->
## Key Stakeholders
<!-- Who uses this? Who maintains it? -->
<!-- Technical, business, or regulatory constraints -->
<!-- What this project explicitly doesn't do -->
---
active-context.md - Set current focus:
# Active Context
## Current Focus
<!-- What are we working on right now? -->
## Recent Decisions
<!-- Decisions made in recent sessions that affect current work -->
## Open Questions
<!-- Unresolved questions that need answers -->
## Blockers
<!-- What's preventing progress? -->
---
*Session: [date]*
progress.md - Empty or with known tasks:
# Progress Tracker
## In Progress
- [ ] [Initial task if known]
## Completed (Recent)
<!-- Recently completed items -->
## Backlog
<!-- Future tasks -->
---
*Last updated: [date]*
patterns.md - Any detected patterns:
# Project Patterns
## Code Conventions
<!-- Coding standards and conventions -->
## Architecture Patterns
<!-- Recurring architectural patterns -->
## Testing Patterns
<!-- Testing conventions -->
---
*Last updated: [date]*
glossary.md - Any project-specific terms:
# Project Glossary
## Terms
<!-- Project-specific terminology -->
## Abbreviations
<!-- Common abbreviations used -->
---
*Last updated: [date]*
friction.md - Friction patterns (initially empty):
# Friction Patterns
<!-- Generated by /memory-insights. Edit freely. -->
<!-- Loaded at session start to help agents avoid known pitfalls. -->
<!-- Max ~15-20 entries to stay within token budget. -->
## Conventions
<!-- Add friction-reducing conventions here -->
## Project-Specific
<!-- Friction patterns specific to this project -->
---
*Last updated: [date]*
Ask user:
What token budget preset would you like?
- Economy (~2000 tokens): Minimal context, fast loading
- Light (~3000 tokens): Smaller projects, lighter footprint
- Standard (~4000 tokens): Balanced for most projects (default)
- Detailed (~6000 tokens): Comprehensive context, rich handoffs
Create .claude/memory/.memory-config.md with their choice:
---
token_budget: standard
---
If user accepts default (Standard), this file can be omitted.
Ask user:
Enable cross-project memory search? This allows searching memory across other projects on your machine. [y/n]
If yes:
Enter parent directories to search (comma-separated). Example: ~/zed, ~/work Write to
.claude/memory/.memory-config.md(append to existing frontmatter):
project_search_paths: ["~/zed", "~/work"]
If no:
Disable this prompt permanently? [y/n]
project_search_paths: disabled in configAsk user:
Should
.claude/memory/be tracked in git?
- Yes: Memory persists with repo (recommended for solo projects)
- No: Add to .gitignore (recommended for shared repos)
If no, add to .gitignore (idempotent - won't duplicate if already present):
grep -qxF '.claude/memory/' .gitignore 2>/dev/null || echo '.claude/memory/' >> .gitignore
Output summary:
Memory initialized for [project-name]
- Product context: [summary]
- Current focus: [focus]
- Token budget: [economy/light/standard/detailed]
- Git tracking: [yes/no]
Use
/memory-syncto update memory as you work. Use/memory-configto adjust settings later.
If any memory files already contain entries (e.g., reset scenario or migration from a previous setup), offer to tag them:
Tag existing memory entries with categories? [y/n]
If yes: Read each memory file and classify each entry or section heading using these keyword matching rules:
decisionpatternbugfixconventionlearningPlace each tag on its own line immediately after the entry it categorizes. Show the proposed tags to the user before applying, then apply on confirmation.
If no: Skip — no tags added. Files continue to work normally without tags.
This step is opt-in only. Never auto-tag without asking.
View and modify ConKeeper memory configuration settings. Use to adjust token budget, output style, and other preferences after memory initialization.
Analyze session friction trends, success rates, and satisfaction patterns across sessions using Claude Code facets data. Read-only query tool for on-demand trend analysis.
Session retrospection using After Action Review methodology. Analyzes corrections, observations, and session activity to produce improvement recommendations. Use at end of sessions or after /memory-sync.