mem

Use this skill as the single interface for persistent knowledge bases, project context, generated base indexes, workspace project snapshots, and schema-backed file layouts. It owns base selection, root containment, schema inspection, model-inferred node selection, exact-node materialization, and durable read/write safety.

Concepts

• Root node: The first node in a tree.
• Hierarchy: A directed graph that describes the layout of files.
• Schema: Rules defining how a hierarchy is organized.
• Base: A collection of one or more schemas that make a knowledge connection.
• Mem config: Global configuration that defines knowledge bases.

Invocation Rule

Invoke $mem whenever the user explicitly asks to save, retrieve, organize, or update durable knowledge, even when they do not name this skill. Treat requests to record, remember, capture, or document reusable guides, cookbooks, runbooks, decisions, research notes, findings, lessons, and references as $mem requests.

Also invoke $mem when inspecting, validating, or materializing a bundled file schema.

When project or workspace instructions require $mem for context lookup, invoke it even without durable-output intent. Context lookup never changes knowledge documents or source files, but may create the selected base's missing derived .mem.index.json; select the configured base, resolve its schemas, infer likely nodes from their descriptions, and search existing knowledge before inspecting source.