@memorax/memorax-code 0.1.0

package/lib/memorax-code-claude-adapter/scripts/build-marketplace.mjs

@@ -0,0 +1,99 @@
+#!/usr/bin/env node
+import { cp, mkdir, readdir, readFile, rm, writeFile } from "node:fs/promises";
+import { dirname, join, resolve } from "node:path";
+import { fileURLToPath, pathToFileURL } from "node:url";
+import {
+  collectClaudePluginArtifactSources,
+  describeClaudePluginArtifactProblems,
+  inspectClaudePluginArtifact,
+} from "../src/plugin-artifact-contract.mjs";
+
+const SCRIPT_DIR = dirname(fileURLToPath(import.meta.url));
+const ADAPTER_ROOT = resolve(SCRIPT_DIR, "..");
+const PLUGIN_NAME = "memorax-code-claude-adapter";
+
+export async function buildClaudeMarketplace({ outputDir, adapterRoot = ADAPTER_ROOT } = {}) {
+  if (!outputDir) throw new Error("outputDir is required");
+  const marketplaceRoot = resolve(outputDir);
+  const pluginRoot = join(marketplaceRoot, "plugins", PLUGIN_NAME);
+  const artifactSources = collectClaudePluginArtifactSources({ adapterRoot });
+
+  await rm(marketplaceRoot, { recursive: true, force: true });
+  await mkdir(join(marketplaceRoot, ".claude-plugin"), { recursive: true });
+  await mkdir(pluginRoot, { recursive: true });
+
+  await writeFile(
+    join(marketplaceRoot, ".claude-plugin", "marketplace.json"),
+    `${JSON.stringify({
+      name: "memorax-code-local",
+      description: "MemoraX Code integration for Claude Code.",
+      owner: {
+        name: "MemoraX Code Local",
+      },
+      plugins: [
+        {
+          name: PLUGIN_NAME,
+          displayName: "MemoraX Code",
+          source: `./plugins/${PLUGIN_NAME}`,
+          description: "Connect Claude Code to MemoraX Code memory.",
+        },
+      ],
+    }, null, 2)}\n`
+  );
+
+  for (const source of artifactSources) {
+    const destination = join(pluginRoot, ...source.relativePath.split("/"));
+    await mkdir(dirname(destination), { recursive: true });
+    await cp(source.sourcePath, destination, { force: true });
+  }
+  await rewriteAdapterCommonImports(pluginRoot);
+  const inspection = inspectClaudePluginArtifact(pluginRoot, artifactSources);
+  if (!inspection.ok) {
+    throw new Error(
+      `generated Claude plugin violates its artifact contract: ${describeClaudePluginArtifactProblems(inspection)}`,
+    );
+  }
+
+  return {
+    ok: true,
+    marketplaceRoot,
+    pluginName: PLUGIN_NAME,
+    pluginRoot,
+  };
+}
+
+async function rewriteAdapterCommonImports(pluginRoot) {
+  for (const dir of ["hooks", "runtime-hooks", "src"]) {
+    for (const path of await mjsFiles(join(pluginRoot, dir))) {
+      const text = await readFile(path, "utf8");
+      const next = text.replaceAll("../../memorax-code-adapter-common/src/", "../memorax-code-adapter-common/src/");
+      if (next !== text) await writeFile(path, next, "utf8");
+    }
+  }
+}
+
+async function mjsFiles(root) {
+  const files = [];
+  for (const entry of await readdir(root, { withFileTypes: true })) {
+    const path = join(root, entry.name);
+    if (entry.isDirectory()) files.push(...await mjsFiles(path));
+    else if (entry.isFile() && entry.name.endsWith(".mjs")) files.push(path);
+  }
+  return files;
+}
+
+if (process.argv[1] && import.meta.url === pathToFileURL(resolve(process.argv[1])).href) {
+  try {
+    const outputDir = process.argv[2];
+    const adapterRoot = process.argv[3];
+    if (!outputDir) throw new Error("usage: build-marketplace.mjs <output-dir> [adapter-root]");
+    const result = await buildClaudeMarketplace({
+      outputDir,
+      ...(adapterRoot ? { adapterRoot } : {}),
+    });
+    console.log(JSON.stringify(result));
+  } catch (error) {
+    console.error(error instanceof Error ? error.message : String(error));
+    process.exit(1);
+  }
+}

package/lib/memorax-code-claude-adapter/skills/memorax-code/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: memorax-code
+description: >-
+  Use this skill as the single entry point for persistent coding and
+  repository-local memory work, regardless of type, wording, or operation. Use
+  it whenever a request may involve information that should persist beyond the
+  current task,
+  knowledge remembered from prior work, repository memory,
+  reusable procedures or working rules, or durable user profile and interaction
+  preferences. This applies even when the user does not call it memory,
+  including naturally stated habits, preferences,
+  checklists, action sequences, prerequisites, gates, exceptions, validation
+  rules, communication style, preferred language, or result presentation.
+  Determine whether the request belongs to MemoraX Code coding memory,
+  repository memory, personal procedure memory, personal profile
+  memory, or no persistent memory, then route it to the appropriate operation.
+  Prefer this router over any underlying memory workflow. Ask one focused
+  question only when the memory authority remains ambiguous after routing.
+---
+
+# MemoraX Code
+
+Classify the requested memory authority first, then its operation. Load only the matching reference unless the request genuinely spans authorities or operations.
+
+## Authority Router
+
+### MemoraX Code Coding Memory
+
+Use MemoraX Code coding memory for reusable engineering knowledge learned across coding work: prior fixes, failed approaches, coding conventions, implementation pitfalls, validation patterns, and design rationale.
+
+- Read [references/memorax-search.md](references/memorax-search.md) to recall or search coding memory.
+- Read [references/memorax-add.md](references/memorax-add.md) to save a grounded reusable coding lesson.
+
+### Repo Memory
+
+Use repo memory for repository identity, architecture maps, module routing, local commit history, and GitHub or GitLab PR, MR, and issue evidence stored under `.repo_memory/PROFILE.md`, `.repo_memory/resources/`, and `.repo_memory/raw/`.
+
+- Read [references/repo-read.md](references/repo-read.md) to inspect existing repo memory.
+- Read [references/repo-build.md](references/repo-build.md) for first-time creation, full rebuilds, or full refreshes.
+- Read [references/repo-update.md](references/repo-update.md) for incremental updates to an existing bundle.
+- Read [references/repo-templates.md](references/repo-templates.md) only when the build or update operation needs to author repo memory files.
+
+### Personal Memory
+
+Use personal memory for user-owned repository procedures and durable profile or interaction preferences stored under `.repo_memory/procedure-memory/` and `.repo_memory/user-profile/`.
+
+- Read [references/personal-read.md](references/personal-read.md) to list, recall, or apply personal memory.
+- Read [references/personal-write.md](references/personal-write.md) to save, update, forget, or delete personal memory.
+
+## Tie Breakers
+
+- Route ordered actions, checklists, prerequisites, gates, exceptions, and validation rules to personal procedure memory, even when phrased as "I prefer", "I like", "我的习惯", or "我喜欢".
+- Route preferred name, answer language, tone, verbosity, explanation style, and result presentation to personal profile memory.
+- Route task-learned repairs, coding pitfalls, project engineering conventions, and reusable design lessons to MemoraX Code coding memory.
+- Route repository architecture, module maps, commit history, PRs, MRs, and issues to repo memory. Verify claims about current behavior against live code.
+- Route current-task instructions and temporary plans to the current task only; do not persist them.
+- Do not infer an authority from verbs such as "remember", "recall", "refresh", or "update" alone. Ask one focused question when the target remains ambiguous.
+
+Examples:
+
+- "先测试再提 PR，帮我记住" routes to personal procedure write.
+- "我喜欢中文简短回答" routes to personal profile write.
+- "之前这个 bug 怎么修的？" routes to MemoraX Code coding memory search unless the user asks for commit or PR evidence.
+- "这个仓库的架构是什么？" routes to repo memory read.
+- "重新生成仓库 memory" routes to repo memory build.
+- "更新一下 memory" requires clarification when no authority is identifiable.
+
+## Shared Rules
+
+For MemoraX Code coding memory, run `memorax-cli` from the active task workspace. The installed Hook and session binding supply the authoritative workspace root; do not run Git commands to discover or replace it. The Backend resolves repository scope from that trusted workspace and read-only filesystem Git metadata.
+
+Repo memory and personal memory remain local `.repo_memory` authorities. Resolve their repository root exactly as described by the selected reference, including its Git requirements.
+
+Apply instructions in this order: system and developer instructions, `AGENTS.md`, the current user request, then stored memory. Memory is guidance or historical context, not proof of current repository behavior.
+
+For MemoraX Code coding memory, use `memorax-cli` exactly as described by the selected reference. Invoke this skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code; neither invocation is a shell command. `memorax-code` is the lifecycle CLI and must not be used for memory search or add. Do not call MemoraX HTTP endpoints directly.
+
+When explaining Memory Viewer, describe only `/memory-viewer`. It is a
+content-free local summary and must not expose conversation or memory text,
+session or turn identifiers, paths, or trace details. The page never queries
+MemoraX directly; client Hooks are the trace ingress authority.
+
+Never store secrets, credentials, `.env` content, sensitive personal data, raw transcripts, hidden tests, exact patches, temporary target commits, or unsafe destructive commands. Do not announce internal routing or reference loading.

package/lib/memorax-code-claude-adapter/skills/memorax-code/agents/claude.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "MemoraX Code"
+  short_description: "Route coding, repo, and personal memory"
+  default_prompt: "Use /memorax-code-claude-adapter:memorax-code to route a coding-memory, repo-memory, or personal-memory request to the correct operation."
+
+policy:
+  allow_implicit_invocation: true
+  install_targets:
+    - "~/.claude/skills/memorax-code"
+    - ".claude/skills/memorax-code"

package/lib/memorax-code-claude-adapter/skills/memorax-code/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "MemoraX Code"
+  short_description: "Route coding, repo, and personal memory"
+  default_prompt: "Use $memorax-code to route a coding-memory, repo-memory, or personal-memory request to the correct operation."
+
+policy:
+  allow_implicit_invocation: true

package/lib/memorax-code-claude-adapter/skills/memorax-code/defaults.json

@@ -0,0 +1,9 @@
+{
+  "schema": "repo_memory_builder_defaults.v1",
+  "limits": {
+    "commits": 30,
+    "prs": 30,
+    "issues": 30
+  },
+  "summaryChars": 4000
+}

package/lib/memorax-code-claude-adapter/skills/memorax-code/references/memorax-add.md

@@ -0,0 +1,82 @@
+# MemoraX Code Coding Memory Add
+
+Use these instructions only to add reusable coding knowledge through `memorax-cli`. Invoke the skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code; do not route memory operations through the lifecycle-only `memorax-code` CLI. Do not use this authority for personal procedures, interaction preferences, generated repository facts, or one-off task details.
+
+## Eligible Knowledge
+
+Add a coding memory only when the task yields stable, grounded, reusable engineering knowledge, such as:
+
+- a verified repair invariant or validation pattern;
+- a reusable failed-attempt lesson;
+- a confirmed coding convention, lifecycle boundary, or implementation pitfall;
+- durable design rationale that will help future coding work.
+
+Route user-owned ordered actions, checklists, gates, and work rules to personal procedure memory. Route preferred language, tone, verbosity, name, and presentation to personal profile memory. Route commit, PR, issue, architecture-map, and repository-history facts to repo memory.
+
+Do not add positive repair lessons based only on unverified edits or assistant self-report. Verification may come from a focused test, evaluator, CI check, accepted review, manual reproduction, or deployed behavior. A failed attempt may be saved as negative evidence when the failure itself is clear and reusable.
+
+## Add Workflow
+
+For a proactive add, write all generated prose in `--memory`, `--reason`, and the confirmation in the language of the user's current request; preserve exact code, API, path, workflow, and project identifiers.
+
+Run from the active task workspace. Pass the memory and reason directly. Put every dynamically generated `--memory` and `--reason` value in single quotes, never double quotes. Treat `$HOME`, backticks, and `$(command)` as literal text inside those quotes. Replace each literal single quote in a value with the exact POSIX sequence `'\''`.
+
+```bash
+memorax-cli add \
+  --memory 'Concise reusable memory.' \
+  --type procedural \
+  --reason 'Capture reusable coding memory.'
+```
+
+Use an appropriate supported type such as `core`, `semantic`, `procedural`, `episodic`, or `unclassified`. Use `preference` only for an engineering convention owned by MemoraX Code coding memory, not for a personal interaction preference.
+
+For a complex verified repair or failed approach, use this compact card when it improves later retrieval:
+
+```text
+CODE_AGENT_MEMORY
+repo: <repository or product area>
+scope: <module/path::symbol/API or lifecycle boundary>
+status: <verified|failed_attempt|candidate>
+signal: <test, CI, review, reproduction, deployment, failure, or unknown>
+problem: <small behavioral symptom or engineering situation>
+technical_context: <stable API, lifecycle, state owner, or data-shape detail>
+surfaces: <observable producer/consumer or setup/runtime/cleanup boundaries>
+failed_shape: <reusable wrong assumption or unsafe patch shape, or none>
+validation: <small reusable check contract>
+principle: <abstract invariant or decision rule>
+anchors: <stable repository source, tests, or public docs>
+```
+
+Keep the card under 1,100 characters when practical. It must guide future investigation while still requiring live-code inspection.
+
+Pass a completed multi-line card as one single-quoted `--memory` argument:
+
+```bash
+memorax-cli add \
+  --memory 'CODE_AGENT_MEMORY
+repo: owner/name
+scope: module/path::symbol
+status: verified
+signal: focused test passed
+problem: concise reusable symptom
+technical_context: stable implementation fact
+surfaces: affected boundary
+failed_shape: reusable pitfall or none
+validation: smallest reusable check
+principle: reusable invariant
+anchors: stable/source/path' \
+  --type procedural \
+  --reason 'Capture verified reusable coding memory.'
+```
+
+If add fails, report the exact failure and do not retry automatically, bypass the CLI, or call MemoraX directly.
+
+## Exclusions
+
+Do not add secrets, credentials, private URLs, raw authorization headers, exact patches, target commits, hidden tests, target diffs, vulnerability details, exploit steps, copied source, long logs, stack traces, raw transcripts, temporary errors, or facts directly recoverable from current files and git history.
+
+Do not add speculation, assistant-only praise, or a current instruction merely because it contains "remember". Return to `SKILL.md` when the content belongs to personal memory or repo memory.
+
+## Output
+
+After an add request is accepted, confirm briefly that it was submitted for processing and identify the reusable coding lesson at a high level. If add is disabled or fails, report the issue and continue without bypassing the CLI.

package/lib/memorax-code-claude-adapter/skills/memorax-code/references/memorax-search.md

@@ -0,0 +1,61 @@
+# MemoraX Code Coding Memory Search
+
+Use these instructions only to search reusable coding memory through `memorax-cli`. Invoke the skill as `$memorax-code` in Codex or `/memorax-code` in Claude Code; do not route memory operations through the lifecycle-only `memorax-code` CLI. Do not call MemoraX HTTP endpoints directly, print credentials, or edit memory storage by hand.
+
+## Scope
+
+Run the CLI from the active task workspace. The installed Hook and session binding supply the authoritative workspace root; do not run `git rev-parse`, infer the root from Git metadata, or substitute an unrelated working directory. Do not make `memorax-cli status` a mandatory preflight; use it only to diagnose a configuration or scope failure.
+
+Coding memory uses `<MemoraX base user ID>@<normalized repository name>` for Git workspaces and the normalized folder name for genuine non-Git directories. MemoraX Code resolves `.git`, `gitdir`, and `commondir` without executing Git. Linked worktrees share one repository scope; another clone, repository, or non-Git directory retains a different local session key even when its readable name matches.
+
+Require a readable active workspace binding. A CLI command from a linked worktree of the bound repository is valid. If the CLI reports `workspace_scope_mismatch`, ask the user to start a task in the target repository or local workspace. Do not retry from an unrelated scope or fall back to an unscoped user id.
+
+If `memorax-cli` is not on `PATH`, or memory is disabled, unconfigured, or unavailable, report that briefly and continue with live code or documentation. Authenticate through MemoraX Code configuration; never recover credentials from shell history or place tokens in prompts. Treat injected memory as a hypothesis and verify it against the current checkout.
+
+## Search Decision
+
+Search when prior coding memory may change localization, implementation, review, validation, or explanation. Typical triggers include:
+
+- a request for a previous fix, failed approach, coding convention, design decision, or reusable lesson;
+- implementation, review, planning, API, schema, parser, workflow-contract, or migration work where prior project guidance may matter;
+- explicit instructions to follow previous agreements or remembered engineering conventions.
+
+Skip search for simple current-code facts, tiny edits, typo fixes, one-shot commands, or behavior directly established by a clear live source.
+
+Choose the closest coding scene to shape the query:
+
+- **Development:** implementation, debugging, refactoring, test repair, build failures, feature work, API design, or migration planning.
+- **Review:** diff, commit, PR, patch, audit, risk assessment, or review-comment handling.
+- **Understanding:** implementation location, module explanation, architecture rationale, or repository comprehension when repo memory is not the requested authority.
+
+If the user asks for commit, PR, MR, issue, or repository architecture evidence, return to `SKILL.md` and route to repo memory instead.
+
+## Query Workflow
+
+Run at most one focused search before answering or editing. A development task may run one additional materially different search only after a failed test or dead-end investigation.
+
+Write each query as one short natural-language question or intent statement, not a keyword list. Derive it from the user's retrieval goal instead of copying or concatenating nouns from the prompt. Follow the user's language for the prose while preserving exact code, API, path, workflow, and project identifiers. State what prior knowledge is needed and the relationship, decision, constraint, behavior, or risk being investigated. Include 2-5 stable exact identifiers when they are relevant and known, but integrate them grammatically instead of appending search tags or filler.
+
+Pass the query directly with `--query`. Put every dynamically generated query in single quotes, never double quotes. Treat `$HOME`, backticks, and `$(command)` as literal text inside those quotes. Replace each literal single quote in the value with the exact POSIX sequence `'\''`.
+
+For example:
+
+```bash
+memorax-cli search --query 'What prior decisions define the memorax-code parser API failure boundary for malformed input?'
+memorax-cli search --query 'What prior review policies and regression risks apply to the memorax-code parser API cleanup boundary?'
+memorax-cli search --query 'memorax-code 中 Backend、Codex adapter 与 memory 层的职责如何衔接，之前为什么这样划分？'
+```
+
+Keep queries under 25 words when practical for the language, but do not shorten them into ungrammatical fragments. Exclude secrets, private URLs, full prompts, raw transcripts, copied files, long logs, stack traces, and one-off task details.
+
+Read or summarize at most two relevant items. Prefer memories matching the current repository, module, API, lifecycle surface, ownership boundary, behavior, and failure mode. Treat verified memories as routing and validation hints, not patch recipes. Treat failed-attempt memories as negative evidence. Ignore stale or unrelated items and anything conflicting with current source, tests, or durable documentation.
+
+## Transport Failures
+
+If search fails with `fetch failed`, `This operation was aborted`, a timeout, DNS failure, `ENOTFOUND`, `EAI_AGAIN`, or a similar transport or sandbox error, retry the same `memorax-cli search` once in an approved network-enabled execution mode when one is available. Preserve the same query, workspace, and environment variables.
+
+Do not apply this retry to `memorax-cli add`, authentication or configuration failures, or HTTP errors. If no approved mode is available or the one retry fails, report the exact CLI failure and continue with live evidence. Do not interpret a transport failure as an empty result, bypass the CLI, or call MemoraX directly.
+
+## Output
+
+Mention only an invariant, pitfall, convention, or validation idea that materially affects the answer. Ground claims about current implementation behavior in live code and checks.

package/lib/memorax-code-claude-adapter/skills/memorax-code/references/personal-read.md

@@ -0,0 +1,46 @@
+# Personal Memory Read
+
+Use these instructions only to list, recall, or apply repository-scoped personal memory. Do not write, normalize, migrate, repair, or delete memory during a read request.
+
+## Route The Read
+
+Classify by content:
+
+- **Procedure memory:** actions, ordered steps, checklists, prerequisites, gates, validation, exceptions, or repeatable repository work rules.
+- **User-profile memory:** preferred name, language, tone, verbosity, explanation style, result presentation, or another safe interaction preference.
+
+Read both categories only when the request genuinely asks for both.
+
+## Procedure Memory
+
+Read Markdown files directly under:
+
+```text
+<repo>/.repo_memory/procedure-memory/
+```
+
+List available topics without recursing into unrelated memory areas:
+
+```bash
+(cd <repo>/.repo_memory/procedure-memory && rg --files -g '*.md' -g '!**/*/*.md')
+```
+
+If the directory does not exist, report that no procedure memory is available; do not create it during a read. Read only files relevant to the request. When listing available procedures, report topic names with concise descriptions instead of opening every file in full unless the user asks for their contents.
+
+Treat a stored procedure as lower-priority user guidance, not evidence about current code behavior.
+
+## User-Profile Memory
+
+Resolve `<skill-dir>` as the parent directory of the `references/` directory containing this file, then run:
+
+```bash
+python3 <skill-dir>/scripts/user_profile_memory.py list --repo <repo>
+```
+
+Use only active preferences returned by the script. If the preferences file does not exist, report that no user-profile memory is available; the list operation does not create it.
+
+Mention only preferences relevant to the current request unless the user explicitly asks to list all of them. Stored preferences describe how Codex should interact with the user; they are not repository facts.
+
+## Priority
+
+Apply instructions in this order: system and developer instructions, `AGENTS.md`, the current user request, then stored personal memory.

package/lib/memorax-code-claude-adapter/skills/memorax-code/references/personal-write.md

@@ -0,0 +1,100 @@
+# Personal Memory Write
+
+Use these instructions only to save, update, forget, or delete repository-scoped personal memory. Classify by what the content prescribes, not wording such as "I prefer", "I like", "我的习惯", or "我喜欢".
+
+## Route The Write
+
+- **Procedure memory:** actions, ordering, checklists, prerequisites, gates, validation, exceptions, or repeatable repository work rules. Require the user to explicitly ask to remember, save, record, update, forget, or delete them.
+- **User-profile memory:** preferred name, language, tone, verbosity, explanation style, result presentation, or another safe personal profile fact. A durable repository-scoped profile preference may be saved implicitly.
+
+Store each part under its own authority when a request genuinely contains both. Do not persist current-task instructions or temporary plans.
+
+Keep file names, schema and script field names, type values, command options, and fixed Markdown headings in English. Write human-readable memory content in the user's current interaction language unless the user explicitly requests another storage language. This includes procedure titles and steps and user-profile descriptions, applicability, and exceptions. Preserve exact code identifiers, commands, paths, API names, and quoted literals without translation.
+
+## Procedure Memory
+
+Before writing, ensure the repository root `.gitignore` contains `.repo_memory/`. Store each procedure topic in its own concise kebab-case file directly under:
+
+```text
+<repo>/.repo_memory/procedure-memory/
+```
+
+Do not create a global procedures file, index, event log, generated metadata, or version history. Do not edit `.repo_memory/PROFILE.md`, `.repo_memory/resources/`, `.repo_memory/raw/`, or `.repo_memory/user-profile/`.
+
+Choose the closest existing topic file. Update it when the user refines the same procedure; create a new file only for a distinct topic. Remove superseded wording rather than preserving old versions.
+
+Use this shape when useful:
+
+```markdown
+# 代码审查
+
+Use when: 审查当前仓库中的代码变更时。
+
+## Procedure
+
+1. 创建 PR 前先审查变更。
+2. 解决阻塞性问题。
+3. 审查完成后再创建 PR。
+
+## Exceptions
+
+- 优先遵循用户当前提出的更具体指令。
+```
+
+Delete only the topic file or section the user explicitly identifies. Do not retain deleted text in tombstones, backups, inactive entries, or history files.
+
+## User-Profile Memory
+
+Use only:
+
+```text
+<repo>/.repo_memory/user-profile/preferences.md
+```
+
+Resolve `<skill-dir>` as the parent directory of the `references/` directory containing this file. The script owns directory creation, `.gitignore` updates, parsing, normalization, locking, duplicate detection, counts, and deterministic rewriting. Do not hand-edit `preferences.md` except when diagnosing a script failure.
+
+List existing preferences before adding and perform semantic matching:
+
+```bash
+python3 <skill-dir>/scripts/user_profile_memory.py list --repo <repo>
+```
+
+If equivalent content exists, do not add it again. Update the matching id when an existing entry expresses the same preference differently. Add only a genuinely new preference:
+
+```bash
+python3 <skill-dir>/scripts/user_profile_memory.py add \
+  --repo <repo> \
+  --type communication \
+  --description "用户希望在当前仓库中使用简洁的中文回答。" \
+  --applies-when "回答当前仓库相关问题时。" \
+  --do-not-apply-when "用户明确要求使用其他语言或格式。"
+```
+
+Allowed script types are `communication`, `workflow`, `environment`, and `profile`. These type names do not expand this authority: never use `workflow` or `environment` to store an executable repository procedure.
+
+Update a clearly identified preference in place:
+
+```bash
+python3 <skill-dir>/scripts/user_profile_memory.py update \
+  --repo <repo> \
+  --id <preference-id> \
+  --description <current-description> \
+  --applies-when <current-scope> \
+  --do-not-apply-when <exception>
+```
+
+If multiple preferences may match, ask the user to choose before updating. Delete only an explicitly identified preference:
+
+```bash
+python3 <skill-dir>/scripts/user_profile_memory.py delete \
+  --repo <repo> \
+  --id <preference-id>
+```
+
+For delete-all requests, list active preferences and delete each id. Do not preserve deleted text elsewhere.
+
+## Safety And Output
+
+Do not store secrets, tokens, credentials, `.env` content, sensitive personal data, repository facts, code history, design rationale, one-off task details, raw transcripts, hidden tests, exact patches, raw diffs, target commits, or unsafe destructive commands.
+
+After a successful write, update, or deletion, identify the affected topic or preference briefly and confirm that it is local to the current repository.