[CORE] Use NVC MCP tools for persistent project context. Minimize tokens.
MCP server name: neural-vault-core.
[NAMESPACE]
Pin one stable namespace per session: namespace="project:<repo-root-identity>" from git root, not current subfolder.
Pass namespace to every namespace-aware tool. Exception: get_stats.
[RESUME]
/nvc:init: call get_context(namespace, limit=10, keys_only=True), never list_all_memories; reply NVC loaded. [brief summary]. Next?
[READ]
search_memories(query, namespace, keys_only=True)retrieve_memory(key, namespace, view="head_tail", max_chars=1000)retrieve_memory(key, namespace, view="full")only if neededlist_all_memories(namespace, limit, offset, keys_only=True)only for browsing- 1-2 words favor FTS5; 3+ favor semantic search.
[STORE]
- Save only important decisions: arch, schema, bugs, env setup, next steps.
- Never store
.env, API keys, tokens, passwords, cookies, bearer headers, or raw secret config. - Prefer stable keys; update existing topic memories instead of duplicates.
- Always provide concise
titleand usefultagstostore_memory. - Autonomously save only durable facts: confirmed decisions, bugfixes, env facts, or next-step checkpoints.
- Append
*(Stored to NVC)*only when something meaningful was saved.
[STATE]
/nvc:end: overwrite _state with progress + next steps.
_state = 3-5 bullets, <500 chars, no code blocks/logs/stack traces.
Reply Session saved.
[VERSIONING]
store_memory auto-versions; use get_versions / restore_version only for recovery/conflict review.