chore: align opencode memory docs with .memory project
This commit is contained in:
@@ -19,7 +19,8 @@ so future sessions can resume quickly.
|
||||
|
||||
Use `list_memory_projects` to check whether this repo already has a basic-memory
|
||||
project. If not, create one with `create_memory_project` using a short kebab-case
|
||||
name (e.g., `my-web-app`) and the repo's root directory as `project_path`.
|
||||
name (e.g., `my-web-app`) and the repo's `.memory/` subdirectory as `project_path`
|
||||
(e.g., `/path/to/repo/.memory`).
|
||||
|
||||
All subsequent `write_note`, `search_notes`, and `build_context` calls in this
|
||||
command must pass `project="<repo-project-name>"` for project-specific notes, or
|
||||
@@ -36,9 +37,9 @@ current state prevents duplication and helps you decide what to create vs update
|
||||
Run `git ls-files` to understand the project layout, then read `README.md` and
|
||||
the highest-signal files for architecture and conventions.
|
||||
|
||||
Also check for existing cross-tool instruction files (`AGENTS.md`, `CLAUDE.md`,
|
||||
`.cursorrules`, `.github/copilot-instructions.md`) — they may contain project
|
||||
knowledge from other tools or team members that should be incorporated.
|
||||
Also check whether any legacy tool-specific instruction files exist alongside
|
||||
`AGENTS.md` — they may contain project knowledge from other tools or team
|
||||
members that should be consolidated into `AGENTS.md`.
|
||||
|
||||
Identify:
|
||||
- What the project does (primary capabilities)
|
||||
@@ -81,9 +82,9 @@ Do not store project-specific plans, decisions, or session state in `main`.
|
||||
If `AGENTS.md` exists, update it with any new project knowledge discovered
|
||||
during bootstrap (architecture, conventions, commands). Add the repo's
|
||||
basic-memory project name (e.g., `opencode-config`) to `AGENTS.md` so
|
||||
agents know which project to target. The symlinks (`CLAUDE.md`,
|
||||
`.cursorrules`, `.github/copilot-instructions.md`) will automatically
|
||||
reflect changes.
|
||||
agents know which project to target. If legacy tool-specific instruction files
|
||||
exist, consolidate any durable repo guidance into `AGENTS.md` and stop
|
||||
maintaining duplicate copies.
|
||||
|
||||
If the instruction file doesn't exist, note that `/init` should be run to create it.
|
||||
|
||||
@@ -94,4 +95,4 @@ If the instruction file doesn't exist, note that `/init` should be run to create
|
||||
- Prefer durable knowledge over transient status notes.
|
||||
- Use WikiLinks `[[Topic]]` to create relations between related notes.
|
||||
- Use tags for categorization: `#pattern`, `#convention`, `#decision`, `#architecture`.
|
||||
- Always pass the `project` parameter on every MCP call.
|
||||
- Always pass the `project` parameter on every MCP call.
|
||||
|
||||
Reference in New Issue
Block a user