// AI DevKit · Use the memory CLI as a durable knowledge layer. Search before non-trivial work, store verified reusable knowledge, update stale entries, and avoid saving transcripts, secrets, or one-off task progress.
| name | memory |
| description | AI DevKit · Use the memory CLI as a durable knowledge layer. Search before non-trivial work, store verified reusable knowledge, update stale entries, and avoid saving transcripts, secrets, or one-off task progress. |
Use npx ai-devkit@latest memory ... as the durable knowledge layer.
For implementation, debugging, review, planning, or documentation tasks, search before deep work unless the task is trivial:
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.
Use results as context:
Search before storing:
npx ai-devkit@latest memory search --query "<knowledge to store>" --table
Store or update only after the quality gate passes.
Before storing, all must be true:
Store:
Do not store:
npx ai-devkit@latest memory search \
--query "<query>" \
--tags "<tags>" \
--scope "<scope>" \
--limit 5
Use --table to get IDs for updates:
npx ai-devkit@latest memory search --query "<query>" --table
Options: --query/-q required; --tags; --scope/-s; --limit/-l from 1-20; --table.
npx ai-devkit@latest memory store \
--title "<actionable title, 10-100 chars>" \
--content "<context, guidance, evidence, exceptions>" \
--tags "<lowercase,tags>" \
--scope "<global|project:name|repo:org/repo>"
Use this content shape when helpful:
Context: Where this applies.
Guidance: What to do.
Evidence: File, command, test, or user instruction.
Exceptions: When not to apply it.
Find the ID with search --table, then update only changed fields:
npx ai-devkit@latest memory update \
--id "<memory-id>" \
--title "<updated title>" \
--content "<updated content>" \
--tags "<replacement,tags>" \
--scope "<updated scope>"
--tags replaces all existing tags.
Use the narrowest useful scope:
repo:<org/repo> for one repository.project:<name> for one app, product, or workspace.global only for knowledge that applies across unrelated projects.If unsure, use a narrower scope.
npx ai-devkit@latest --version.--limit range.~/.ai-devkit/memory.db; project config can override it automatically.AI DevKit · Structured SDLC workflow with 8 phases — requirements, design review, planning, implementation, testing, and code review. Use when the user wants to build a feature end-to-end, or run any individual phase (new requirement, review requirements, review design, execute plan, update planning, check implementation, write tests, code review).
AI DevKit · Document a code entry point with structured analysis, dependency mapping, and saved knowledge docs. Use when users ask to document, understand, or map code for a module, file, folder, function, or API.
AI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).
AI DevKit · Proactively orchestrate running AI agents — scan statuses, assess progress, send next instructions, and coordinate multi-agent workflows. Use when users ask to manage agents, orchestrate work across agents, or check on agent progress.
AI DevKit · Review code, skills, and prompts for security vulnerabilities — OWASP Top 10, prompt injection, business logic flaws, and insecure defaults. Use when reviewing PRs, auditing modules, reviewing AI skills/prompts, or preparing for release.
AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability. Use when users ask to simplify code, reduce complexity, refactor for readability, clean up implementations, improve maintainability, reduce technical debt, or make code easier to understand.