Files
Elliot Chen 518b8eca85 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.
2026-06-06 07:33:17 +08:00

22 lines
646 B
Markdown

---
description: Open the EverMem Memory Hub to view statistics, search memories, and explore timeline
---
When the user runs this command:
1. First, start the proxy server in the background using the Bash tool:
```bash
node "${CLAUDE_PLUGIN_ROOT}/server/proxy.js" &
```
2. Then, construct the Memory Hub URL with the actual API key using Bash:
```bash
echo "http://localhost:3456/?key=${EVERMEM_API_KEY}"
```
3. Share a simple message with the user like:
"Memory Hub server started. Open this URL to view your memories:
[the URL from step 2]"
Do NOT show the bash commands or code blocks to the user. Just run them and share the final URL.