chore: initialize EverOS 1.0.0
md-first memory extraction framework for AI agents. Markdown is the single source of truth; SQLite holds state and LanceDB provides the rebuildable vector + BM25 + scalar index. The codebase follows a single-direction DDD layering (entrypoints -> service -> memory -> infra, with component / core / config cross-cutting) enforced by import-linter. Engineering surface: - Coding conventions in .claude/rules/ (path-scoped) and workflows in .claude/skills/ (/commit, /new-branch, /pr). - GitHub Actions CI runs make lint + test + integration; pre-commit mirrors the gates locally (ruff, hygiene hooks, gitlint commit-msg). - Commit messages follow Conventional Commits, enforced by gitlint. - make lint also enforces datetime two-zone discipline and OpenAPI drift.
This commit is contained in:
17
use-cases/claude-code-plugin/commands/search.md
Normal file
17
use-cases/claude-code-plugin/commands/search.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
description: Search EverMem for relevant memories from past sessions
|
||||
arguments:
|
||||
- name: query
|
||||
description: The search query to find relevant memories
|
||||
required: true
|
||||
---
|
||||
|
||||
Search EverMem Cloud for memories matching the user's query.
|
||||
|
||||
Run this command to search:
|
||||
|
||||
```bash
|
||||
node "${CLAUDE_PLUGIN_ROOT}/commands/scripts/search-memories.js" "$ARGUMENTS"
|
||||
```
|
||||
|
||||
After the search completes, summarize the key findings for the user. Highlight the most relevant memories and explain how they might be useful for their current work.
|
||||
Reference in New Issue
Block a user