@pinkpixel/memi 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/package.json

@@ -1,6 +1,58 @@
 {
   "name": "@pinkpixel/memi",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.1.0",
+  "description": "Local-first memory for AI agents. SQLite, hybrid search, MCP server, and a small local UI.",
+  "type": "module",
+  "license": "Apache-2.0",
+  "author": "Pink Pixel <admin@pinkpixel.dev> (https://pinkpixel.dev)",
+  "homepage": "https://pinkpixel.dev",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pinkpixel-dev/memi.git"
+  },
+  "bin": {
+    "memi": "dist/cli/index.js"
+  },
+  "files": [
+    "dist",
+    "ui",
+    "skills",
+    "LICENSE",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.build.json",
+    "dev": "tsx src/cli/index.ts",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run"
+  },
+  "keywords": [
+    "mcp",
+    "memory",
+    "agents",
+    "sqlite",
+    "embeddings",
+    "ollama",
+    "openai"
+  ],
+  "dependencies": {
+    "@hono/node-server": "^2.1.3",
+    "@modelcontextprotocol/sdk": "^1.32.0",
+    "better-sqlite3": "^13.0.3",
+    "commander": "^15.0.0",
+    "hono": "^4.13.13",
+    "sqlite-vec": "^0.1.9",
+    "zod": "^4.6.5"
+  },
+  "devDependencies": {
+    "@types/better-sqlite3": "^9.6.0",
+    "@types/node": "^26.6.4",
+    "happy-dom": "^20.14.5",
+    "tsx": "^4.23.15",
+    "typescript": "^7.0.2",
+    "vitest": "^5.0.3"
+  }
+}

package/skills/memi-curate/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: memi-curate
+version: 1.0.0
+description: |
+  Review and clean up memories stored in memi: find duplicates, contradictions,
+  stale or vague entries, wrong scope or category, inflated importance, and
+  accidentally saved secrets, then fix them with the user's approval. Use when
+  the user asks to "clean up", "review", "organize", or "audit" memories, when
+  recall keeps returning noise or contradictory results, or when list_memories
+  shows a large pile of low-value entries.
+license: Apache-2.0
+compatibility: claude-code cursor codex gemini-cli opencode
+---
+
+# Curating memi memories
+
+Memories pile up. Over time a store collects near-duplicates, decisions that were later reversed, vague notes nobody can interpret, and categories that drifted. A messy store makes `recall` worse, because contradictory or noisy results waste attention and can lead the next session wrong.
+
+This skill is a careful review. The rule that matters most: **deleting is permanent, so you propose first and the user approves.**
+
+If the user would rather look through memories themselves, `memi ui` opens a browser view where they can search, edit, and delete.
+
+## 1. Survey
+
+1. `list_categories` for the shape of the store.
+2. `list_memories` with `scope: "all"` and `limit: 50`, paging with `offset` until `total` is covered. Use `order: "importance"` to see what is loaded at session start first, then `order: "oldest"` for the stale tail.
+3. If the user only cares about one project, use `scope: "project"` with that `project`. Include `scope: "global"` separately.
+
+Read everything before you judge anything. A "duplicate" is easy to misjudge from one memory.
+
+## 2. Look for these problems
+
+| Problem | How to spot it | Fix |
+|---|---|---|
+| **Duplicate** | Two memories say the same thing | Keep the clearer one (`update_memory` to merge in any detail from the other), `forget` the rest |
+| **Contradiction** | Two memories disagree | Decide which is current. Check the repo or ask the user if unsure. Update or keep that one, `forget` the other |
+| **Stale** | Names a file, flag, host, or version that may no longer exist | Verify against the repo. If it changed, `update_memory`. If it is gone, `forget` |
+| **Vague** | Cannot be understood without the original conversation ("use the second approach") | Rewrite so it stands alone if you can tell what it meant. Otherwise `forget` |
+| **Wrong category** | Lots of `context` that is really a decision, preference, or fact | `update_memory` with the right `category` |
+| **Wrong scope** | A project memory that is really a global preference, or the reverse | `update_memory` with `scope` (and `project` if moving to a project) |
+| **Inflated importance** | A pile of 4s and 5s, or more than about five pinned memories per scope | Lower importance, unpin the rest |
+| **Category sprawl** | Near-identical custom names (`ci`, `cicd`, `ci-cd`) | Move the memories into one category |
+| **Secret** | An API key, token, password, or private key | Tell the user straight away, `forget` it, and tell them the secret should be rotated since it was stored |
+
+Do not fix what is not broken. A short, plain memory that is correct is fine.
+
+## 3. Propose before you change anything
+
+Present a list the user can approve in one pass. Group by action, and give the id, the reason, and the new wording when you rewrite:
+
+```
+Delete (3)
+  #14  duplicate of #9
+  #31  vague: "use the second approach"
+  #40  stale: refers to scripts/old-deploy.sh, which no longer exists
+
+Update (2)
+  #22  fact -> decision; reword: "Auth uses signed cookies, not JWTs, because sessions must be revocable."
+  #27  scope project -> global (it is a tooling preference)
+
+Lower importance (1)
+  #8   5 -> 3
+
+Secrets (0)
+```
+
+Then wait. Apply only what the user approves. If they approve some items, do those and leave the rest.
+
+A secret is the one case where you should say so immediately and not wait for the end of the review. You still need approval before deleting.
+
+## 4. Apply
+
+- `update_memory` for rewording, recategorizing, rescoping, importance, tags, pinning. Changing `content` or scope re-embeds the memory.
+- `forget` for deletions, one id at a time.
+- Merging: update the best memory with the combined content, then `forget` the others.
+
+Note that `update_memory` with `tags` **replaces** the existing tags. Pass the full list you want.
+
+## 5. Report
+
+End with plain counts: how many deleted, updated, left alone, and anything you were unsure about and skipped. If you could not check something against the repo, say so.
+
+## Rules
+
+- Never delete without approval.
+- Never change the meaning of a memory while rewording it. If you are not sure what it meant, ask or leave it.
+- Verify stale-looking details against the repo before calling them stale.
+- Keep the user's own words where they are clear. Do not polish for the sake of it.
+- If a warning like `Saved without a vector` appears while updating, mention it once and carry on.

package/skills/memi-memory/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: memi-memory
+version: 1.0.0
+description: |
+  Use memi, a local long-term memory for AI agents, so knowledge survives between
+  sessions. Use whenever the memi MCP tools (get_context, recall, remember,
+  update_memory, forget, list_memories, list_categories) are available: at the
+  start of a session, before making a decision that earlier sessions may have
+  settled, when the user says "remember", "save this", "do you remember", "what
+  did we decide", "last time", "forget that", or "don't do that again", and after
+  you learn something durable such as a decision, a preference, a fact, or a
+  mistake worth avoiding.
+license: Apache-2.0
+compatibility: claude-code cursor codex gemini-cli opencode
+---
+
+# Using memi memory
+
+memi stores memories in a local SQLite file and finds them by meaning and by keyword. Memories last across sessions, and the same store is shared by every agent on this machine. That makes you responsible for what goes in. A good memory saves the next session real time. A bad one is noise that someone will have to find and delete.
+
+Seven tools do all the work: `get_context`, `recall`, `remember`, `update_memory`, `forget`, `list_memories`, `list_categories`.
+
+## The loop
+
+1. **Start of a session:** call `get_context` once. It returns the pinned and high-importance (4 or 5) memories for this project plus global ones. Treat them as background. Do not read them back to the user.
+2. **While working:** call `recall` when earlier knowledge might change what you do (see below).
+3. **After you learn something durable:** call `remember`.
+4. **When a memory turns out to be wrong:** call `update_memory` or `forget`. Do not leave known-wrong memories behind.
+
+## Recall
+
+Recall before you:
+
+- choose a library, pattern, or architecture
+- answer a question about how this user or project does things
+- start debugging something that might have been hit before
+- act on something the user refers to from the past ("like we did before", "as I said")
+
+Recall tips:
+
+- Describe what you want in plain language: `how does the user want commit messages written`. Searching by meaning works, so you do not need to guess exact words.
+- The default scope `both` covers global memories plus the current project. Use `scope: "all"` only when the user asks about another project.
+- Add `min_importance: 4` when you only want what matters most. Add `category` to narrow down.
+- One or two searches per task is normal. Do not search on every message.
+
+Reading results: each memory starts with `#id | category | importance N | scope | ...`. The score is only useful for comparing results within one search.
+
+**Memories can be stale.** Specific details such as file paths, flags, function names, and versions may have changed since the memory was written. Check against the current code before you act on one. If it is wrong, fix it with `update_memory` or remove it with `forget`.
+
+If a result ends with `Note:`, read it. It usually means search fell back to keywords only. See "Warnings" below.
+
+## Remember
+
+### What belongs
+
+- **Decisions and the reason for them.** "Use SQLite, not Postgres, because the app is local-first and the data is small."
+- **User preferences and corrections.** "Prefers tabs. Wants short answers without a summary at the end."
+- **Durable facts that are not obvious from the code.** "Staging deploys need the VPN."
+- **Mistakes worth not repeating, with the fix.** "Running migrations before the seed script fails. Seed first."
+- **Work the user explicitly deferred.** "Add rate limiting to the upload route later."
+
+### What does not belong
+
+- **Secrets of any kind:** API keys, tokens, passwords, private keys. Never.
+- Anything you can read from the code, the git history, or the docs.
+- Task progress that only matters in this session.
+- Guesses. Save what you verified, or what the user said.
+- Long dumps. One memory is one idea in a few sentences. The hard limit is 8000 characters, and you should rarely come close.
+
+### Write it so it stands alone
+
+A future session will see the memory without this conversation. So:
+
+- Lead with the fact, then the reason.
+- Name things exactly (file, tool, command).
+- Use absolute dates, not "yesterday" or "last week".
+- No pronouns that point back at the conversation ("it", "that approach").
+
+Before: `We decided to go with the second option.`
+After: `Auth uses signed cookies, not JWTs, because sessions must be revocable. Decided 2026-10-04.`
+
+More examples are in `references/examples.md`.
+
+### Choose the fields
+
+| Field | How to choose |
+|---|---|
+| `scope` | `project` for things about this codebase. `global` for things about the user or how they work everywhere. If unsure, project. |
+| `category` | `decision`, `preference`, `fact`, `error`, `todo`, or `context`. Run `list_categories` before inventing a new one. |
+| `importance` | 1 to 5, default 3. See `references/rubrics.md`. Most memories are 2 or 3. |
+| `pinned` | Loaded at the start of every session. Use rarely, for rules where forgetting would cost real time or trust. |
+| `tags` | A few keywords you would search for. Optional. |
+
+`project` is worked out for you. Do not pass it unless the user is talking about a different project by name.
+
+### Handle duplicates
+
+`remember` checks for close matches in the same scope. If the result says `Similar memories already exist`:
+
+- **Same fact:** keep the better one. Call `update_memory` on the older memory with the improved wording, then `forget` the new id you just created.
+- **Related but different** (a new detail, a changed decision): keep both, or update the old one if the new one replaces it.
+
+For anything you suspect is already saved, a quick `recall` first is cheaper than cleaning up later.
+
+### Tell the user, briefly
+
+When you save a preference or a decision on your own initiative, say so in one short line ("Saved a note that you prefer tabs.") so they can correct you. Do not announce routine facts.
+
+## When the user asks directly
+
+- **"Remember X"**: save it right away, then confirm with the id.
+- **"Forget X"**: `recall` to find it. If more than one memory matches, show them and ask which. Then `forget`. Deleting is permanent.
+- **"What do you remember about X"**: `recall`, then summarize in your own words.
+
+## Projects and scope
+
+memi works out the project automatically: the folder name of the git repo you are in. With no git repo, it uses the agent name (`MEMI_AGENT`), stored as `agent:<name>`. With neither, saving a project memory fails with an error that says what to set.
+
+If you hit that error, either save the memory as `global` (if it truly is global) or ask the user for a project name or tell them to set `MEMI_AGENT`. Do not make up a project name.
+
+## Warnings
+
+| You see | What it means | What to do |
+|---|---|---|
+| `Saved without a vector` | Saved, but the embedder was unreachable. It can only be found by keyword for now. | Mention it once. The user can run `memi reindex --missing` when Ollama is back. |
+| `The embedder changed from ...` | The configured embedder no longer matches the stored vectors, so semantic search is off. Keyword search still works. | Tell the user to run `memi reindex`. It asks for confirmation, rebuilds the vectors, and keeps all memories. Do not run it yourself unless asked, because it re-embeds everything. |
+| `No embedder configured` / `No vectors yet` | Keyword search only. | Nothing needed. |
+| Tool error | Bad arguments or a bad id. | Read the message, fix the arguments, retry once. |
+
+## If the memi tools are not available
+
+If the MCP server is not connected but the `memi` command exists, use it from the shell: `memi search "query"`, `memi add "text" -c fact`, `memi list`. If neither is available, say so. Do not claim to remember something you cannot save.
+
+## Quick rules
+
+- `get_context` at the start. `recall` before deciding. `remember` after learning.
+- Never save secrets.
+- Write memories that make sense with no context.
+- Update or forget what is wrong. Do not stack contradictions.
+- Verify stale details before acting on them.
+- When unsure whether something is worth saving, ask: would the next session be worse off without it?

package/skills/memi-memory/references/examples.md

@@ -0,0 +1,50 @@
+# Examples
+
+## Rewriting vague memories
+
+| Before | After | What changed |
+|---|---|---|
+| `Use the new approach.` | `Search runs FTS5 and vector KNN, merged with reciprocal rank fusion, because either alone missed too much.` | Named the approach and gave the reason. |
+| `User likes it short.` | `Prefers short answers with no closing summary. Said so on 2026-10-04.` | Said what "it" is, added a date. |
+| `Fixed the bug with the thing.` | `Uploads over 10MB failed because the proxy limit is 10MB. Raised it in nginx.conf to 50MB.` | Named the symptom, the cause, and the fix. |
+| `Don't forget to test on mobile.` | `Every UI change must be checked at 375px width. The app is used mostly on phones.` | Made the rule concrete. |
+
+## What not to save
+
+| Candidate | Why not |
+|---|---|
+| `The project uses TypeScript.` | Visible from the repo. |
+| `Currently refactoring the auth module.` | Session progress. It will be wrong tomorrow. |
+| `The API key is sk-...` | A secret. Never. |
+| `Maybe we should use Redis?` | A guess, not a decision. |
+| A pasted 300-line stack trace | Too long. Save the cause and the fix in two sentences. |
+
+## A duplicate, handled
+
+You call `remember` with `The user prefers tabs over spaces`. The result says:
+
+```
+Saved memory #14 (global, preference, importance 3).
+
+Similar memories already exist. If one covers this, call update_memory on it and forget #14:
+#9 | preference | importance 4 | global | 2026-09-12
+The user prefers tabs over spaces for indentation
+```
+
+Memory #9 already says it, and with more detail. So delete the new one:
+
+1. `forget` with `{ "id": 14 }`
+
+If the new wording were better, you would first call `update_memory` on #9 with the improved `content`, then forget #14.
+
+## Session start
+
+1. Call `get_context`. It returns, say, four memories: two pinned rules, two important decisions.
+2. Use them silently. If the user asks to change something a decision covers, mention the decision and why it was made.
+3. Later the user says "let's add caching". Call `recall` with `caching decisions and constraints` before proposing anything.
+
+## A memory that turned out wrong
+
+`recall` returns `#22 | fact | ... | The staging database is at db-staging-1.` While working you find the host is now `db-staging-2`.
+
+Call `update_memory` with `{ "id": 22, "content": "The staging database is at db-staging-2 (moved from db-staging-1 on 2026-10-04)." }`. Do not save a second memory next to it.

package/skills/memi-memory/references/rubrics.md

@@ -0,0 +1,44 @@
+# Rubrics for memi memories
+
+Use these when the choice of importance, category, scope, or pinning is not obvious.
+
+## Importance
+
+| Level | Meaning | Examples |
+|---|---|---|
+| 1 | Minor. Nice to know, harmless to forget. | "The old build script is in `scripts/legacy/`." |
+| 2 | Useful detail. | "Dev server runs on port 5174 because 5173 is taken." |
+| 3 | Normal. Default. Worth having next session. | "API errors use the `{ error, code }` shape." |
+| 4 | Important. Getting it wrong costs real time. Loaded by `get_context`. | "Never run migrations on the shared staging database without asking." |
+| 5 | Critical. A rule or fact that must never be missed. Loaded by `get_context`. | "Production deploys are manual. Never trigger one from a script." |
+
+Most memories should be 2 or 3. If everything is a 4 or 5, `get_context` stops being useful. Search results are also nudged by importance, so inflating it distorts ranking.
+
+## Pinning
+
+Pinned memories load at the start of every session whatever their importance. Pin only what would hurt if a session started without it. A reasonable ceiling is about five pinned memories per scope. If you want to pin a sixth, unpin or merge one first.
+
+Pinning and importance 4 or 5 do the same job for `get_context`. Use importance for "this matters" and pinning for "this must always be loaded". In practice you rarely need both.
+
+## Categories
+
+| Category | Use for | Not for |
+|---|---|---|
+| `decision` | A choice that was made, with the reason, and ideally what was rejected | Preferences with no trade-off |
+| `preference` | How the user likes things done | Facts about the system |
+| `fact` | Durable truth about the project, system, or user | Anything that will be false next week |
+| `error` | Something that failed, what caused it, and the fix | Bugs that are already fixed and will not recur |
+| `todo` | Work explicitly deferred | Your own in-session task list |
+| `context` | Background that helps orient a future session (the default) | Anything that fits a more specific category |
+
+Custom categories are created the first time you use a name. Keep them short and lowercase (letters, numbers, dashes, underscores, up to 32 characters). Run `list_categories` first, because `ci` and `cicd` splitting the same topic helps nobody. Prefer a built-in category unless a custom one will hold several memories.
+
+## Scope
+
+| Question | If yes |
+|---|---|
+| Is it about the user, how they work, or their tools across projects? | `global` |
+| Would it be wrong or confusing in a different project? | `project` |
+| Is it a coding convention for one repo? | `project` |
+| Is it a personal preference that applies to every repo (tabs, tone, tools)? | `global` |
+| Not sure? | `project`. It is easier to promote later (`update_memory` with `scope: "global"`) than to find a stray global memory. |