memento

How to use Memento — a local-first MCP memory layer for AI assistants — to remember and recall durable knowledge about the user, their preferences, conventions, decisions, and projects across sessions. Trigger this skill whenever the user has Memento connected and any of the following happens, even when the user does not explicitly say "remember it" — the user states something durable about themselves, their tools, their projects, or their conventions ("I prefer pnpm", "we squash-merge on main", "the staging cluster is gke-staging"); the user asks a "what is/was/did I" question that depends on prior context ("what's my preferred test runner?", "what did I decide about logging?"); the user changes their mind about something durable ("actually, I switched from X to Y"); the user asks to forget, archive, or stop suggesting something; or a fresh task starts and prior context would help. Also trigger when the user explicitly says "remember", "memorise", "save", or "note" something. Do NOT use this skill for transi

How to contribute changes to the Memento codebase — the local-first MCP memory layer at github.com/veerps57/memento. Trigger this skill whenever the user is working in a checkout of the Memento repo (look for AGENTS.md and packages/{schema,core,server,cli,dashboard,embedder-local,landing} at the repo root) and any of the following holds — the user is editing source under packages/, the user is adding or changing a command / config key / migration / ADR, the user mentions "the Memento repo" or "this repo" while inside a Memento checkout, the user is debugging a failing pnpm verify run, or the user asks "how do I contribute" / "where does X go" / "what are the rules". Do NOT trigger this skill when Memento is merely a dependency of another project (look for a memento entry in package.json dependencies, not at the repo root) — that is an end-user context where the `memento` skill applies. Do NOT trigger for unrelated TypeScript work, even if a Memento checkout happens to be open elsewhere.