memory

# AI DevKit Memory CLI Use `npx ai-devkit@latest memory ...` as the durable knowledge layer. ## Workflow 1. For implementation, debugging, review, planning, or documentation tasks, search before deep work unless the task is trivial: ```bash npx ai-devkit@latest memory search --query "<task, subsystem, error, or convention>" --limit 5 ``` For broad or risky tasks, search multiple angles: subsystem, error text, framework, command, and task intent. 2. Use results as context: - Trust repo files, tests, fresh command output, and explicit user instructions over memory. - If memory conflicts with verified evidence, use the evidence and update the stale memory. - Mention memory only when it changes the plan or avoids asking the user again. 3. Search before storing: ```bash npx ai-devkit@latest memory search --query "<knowledge to store>" --table ``` 4. Store or update only after the quality gate passes. ## Quality Gate Before storing, all must be true: - Future sessions are likely to reuse it. - It is verified by code, docs, tests, command output, or explicit user instruction. - It is not merely a restatement of obvious nearby files unless it prevents repeated agent mistakes. - It is scoped narrowly enough. - Existing memory does not already cover it. - It contains no secrets, credentials, private customer data, personal data, raw logs, or temporary paths. Store: - Project conventions, user preferences, durable decisions. - Reusable fixes, test...