Re-run the VelesDB core-vs-ecosystem gap analysis (code + documentation). Use when asked to audit API parity, check that every crate/SDK/integration/doc has caught up to velesdb-core, verify the core↔children architecture is clean, or produce a parity matrix. velesdb-core is the single source of truth; the VelesDB…
AGENTS.md instructions for cyberlife-coder/VelesDB, covering agents.md — velesdb, working principles, a single test by name, if search path modified and doctests are a separate ci step from the test suite above.
Use durable, explainable, self-improving memory across a coding session via the velesdb-memory MCP server. Trigger whenever the velesdb-memory MCP tools (remember/recall/recallfused/relate/why/feedback/forget/rememberextracted/extractionstatus/entity/memorystatus) are available and the work would benefit from…
Compress an agent's working context deterministically with VelesDB's context compiler before sending it to a model — fewer tokens, same facts, every decision auditable and reversible. Use when a prompt is bloated with repeated context, long logs, or accumulated conversation turns; when token costs need to drop…
Turn every velesdb design / implement / verify cycle into durable, connected memory so the SAME mistake is never repeated and later decisions build on what was already learned, instead of re-deriving it or silently colliding with it. Trigger BEFORE starting a design or implementation on velesdb / velesdb-core /…
MCP server "velesdb-memory" as configured in cyberlife-coder/VelesDB. Launched with https://github.com/cyberlife-coder/VelesDB/releases/download/velesdb-memory-v0.9.
Serveur MCP pour la génération d'artefacts agiles (backlogs, features, user stories) avec IA - compatible Windsurf, Claude et Cursor. Runs locally from the agile-planner-mcp-server npm package.