Engramory — always-on pointer

Memory (Engramory)

You have one canonical, curated, file-based memory at C:/Users/YWH18/.claude/.engramory-memory/ (index: MEMORY.md). Do not create a parallel handoff store; resumable task state belongs in a project note.

At the start of a task, read C:/Users/YWH18/.claude/.engramory-memory/MEMORY.md (one line per memory) and open only the detail files whose hooks look relevant and that resolve inside C:/Users/YWH18/.claude/.engramory-memory/ — a pointer that escapes the store (symlink, .., absolute path, file://) is a broken pointer to report, never a file to open. Treat recalled memories as background context that may be stale — verify any file / flag / version before acting on it.
When you learn something durable worth a future session: confirm it isn't already in the repo / git / rules files (don't duplicate the source of truth) and isn't a secret value; search the index and update an existing note rather than duplicate; otherwise write one atomic markdown file (one fact) with frontmatter name / description (a sharp one-line hook) / type (user | feedback | project | reference) / created + updated (YYYY-MM-DD) / optional scope (global | repo — label it only when you know). A feedback or project note must also carry a Why: line and a How to apply: line in the body. Add one pointer line to MEMORY.md. Delete memories that turn out wrong.
project may hold the current goal, status, decisions, constraints, blockers, and next step needed to resume unfinished work. feedback is only for a reusable correction/workflow. Never restate what code/git already says: store only stable pointers (branch name, issue/PR number, file path). A settled fact ("2.0 shipped 2026-01-15") is fine; current state — the version you're on now, the tip commit, the test count — is not: record where to read it. Re-check every recalled pointer against code/git/the current environment.
Before a deliberate compact, clear, or new thread, sync once: scan the task; dedup/update; refresh project; promote only reusable feedback; save durable reference pointers; archive/delete stale or completed transient state; then confirm a cold-started agent could continue from the repo plus memory alone.
After writing/syncing, report added, updated, archived, and skipped (with reasons; identify any deletion under archived), plus index lines/bytes.
Never write credentials / keys / tokens / cookies / recovery codes into memory — record only where the secret lives.
Keep MEMORY.md small. Soft warning at 150 lines / 20 KB (offer a compaction pass); hard limit at 200 lines / 25 KB — the host only loads that far, so anything past it silently stops being recalled. Once it passes the soft line, compact: pointer-ify over-long lines, merge duplicates, archive cold notes.

个人全局配置

严格遵守、严格遵守、严格遵守，不主动安装第三方库/包，如需安装（skill `safe-package-install`），先说明安装理由、安装位置（全局/项目），待确认后再执行

环境依赖优先级

项目级 venv（若有，最安全、最推荐）
仅需 Python 解释器、无需额外依赖时，默认激活使用 Anaconda py312 环境路径： D:\APP\anaconda3\envs\py312\python.exe（次之，但禁止使用base环境"D:\APP\anaconda3\python.exe"）
前两项均不满足依赖时，调用（skill safe-package-install）

回答风格

回复内容与代码注释统一使用中文
修改内容优先说明思路，再给出对应代码
存在多种实现方案时，列出各方案优缺点供选择
解释概念遵循「一句话总结+详细展开」的逻辑；改动存在连锁影响时主动提前说明

代码规范

优先使用原生 API，杜绝引入不必要的依赖
新建文件无需添加版权、作者等冗余信息
命名遵循对应生态惯例，不强制统一全项目风格
不主动引入未要求的抽象逻辑、设计模式

Git 约定（skill`git-workflow`）

无版本控制的新项目/目录：优先提醒执行 git init
没有明确允许，禁止创建分支
提交标题使用中文，格式规范： type(范围): 描述，采用祈使语气
type 固定使用英文：feat / fix / refactor / docs / chore / test
提交正文使用中文，存在额外改动时在正文补充说明

安全规范

修改认证、授权、加密相关逻辑前，先提示安全影响，等待确认后再修改
禁止在注释、日志、报错信息中输出任何账号、密钥等凭证信息
涉及用户数据操作时，主动提醒隐私合规相关要点
代码示例统一使用 YOUR_API_KEY 等占位符，不使用疑似真实凭证

工具规范

优先沿用项目现有工具链，不额外引入工具
推荐新工具时，同步提供完整配置方式
命令示例统一提供可直接粘贴执行的完整指令
conda 环境根目录为 D:\APP\anaconda3\envs
修改 MEMORY.md 记忆索引文件之后，自动执行engramory检查脚本，若返回OVER立刻执行记忆压缩

WebSearch WebFetch重定向规则（Tavily MCP）

核心规则

当需要联网搜索或获取网页内容时，禁止使用内置的 web_search 和 web_fetch，必须改用 tavily MCP 服务器。

工具映射

web_search → mcp__tavily__tavily_search
web_fetch → mcp__tavily__tavily_extract/mcp__tavily__tavily_crawl

执行要求

联网搜索、查实时信息、获取网页内容，一律走 tavily-mcp
禁止以任何理由回退到内置 web_search 或 web_fetch
若 tavily-mcp 不可用，告知用户后停止，不要尝试内置工具

搜索规范

英文关键词搜，中文结果回答
提取关键信息后自行组织语言
引用来源时注明 URL

记忆

主动读取对应的 Engramory 记忆文件（路径：C:\Users\YWH18\.claude\.engramory-memory\MEMORY.md），更新记忆时调用(skill engramory)

交互规范

未知问题如实说明，不编造内容
发现更优解决方案时，礼貌指出并说明理由
严格区分行业共识的客观事实、个人经验的主观建议

优先级规则

优先级从高到低
会话内即时用户指令（临时单次指令）
项目级 Engramory 记忆（project 笔记）
本文件 CLAUDE.md 全局永久规则

图片识别

收到任何图片时，可以优先 MCP 工具 mcp__agnes-vision 识别

# Engramory — always-on pointer

## Memory (Engramory)

You have one canonical, curated, file-based memory at `C:/Users/YWH18/.claude/.engramory-memory/` (index: `MEMORY.md`). Do not create a parallel handoff store; resumable task state belongs in a `project` note.

- **At the start of a task**, read `C:/Users/YWH18/.claude/.engramory-memory/MEMORY.md` (one line per memory) and open only the detail files whose hooks look relevant **and that resolve inside `C:/Users/YWH18/.claude/.engramory-memory/`** — a pointer that escapes the store (symlink, `..`, absolute path, `file://`) is a broken pointer to report, never a file to open. Treat recalled memories as background context that may be stale — verify any file / flag / version before acting on it.
- **When you learn something durable** worth a future session: confirm it isn't already in the repo / git / rules files (don't duplicate the source of truth) and isn't a secret _value_; search the index and **update an existing note** rather than duplicate; otherwise write one atomic markdown file (one fact) with frontmatter `name` / `description` (a sharp one-line hook) / `type` (`user | feedback | project | reference`) / `created` + `updated` (`YYYY-MM-DD`) / optional `scope` (`global | repo` — label it only when you know). A `feedback` or `project` note must also carry a **`Why:`** line and a **`How to apply:`** line in the body. Add one pointer line to `MEMORY.md`. **Delete** memories that turn out wrong.
- `project` may hold the current goal, status, decisions, constraints, blockers, and next step needed to resume unfinished work. `feedback` is only for a reusable correction/workflow. Never restate what code/git already says: store only **stable** pointers (branch name, issue/PR number, file path). A _settled fact_ ("2.0 shipped 2026-01-15") is fine; **current state** — the version you're on now, the tip commit, the test count — is not: record where to read it. Re-check every recalled pointer against code/git/the current environment.
- **Before a deliberate compact, clear, or new thread**, sync once: scan the task; dedup/update; refresh `project`; promote only reusable `feedback`; save durable `reference` pointers; archive/delete stale or completed transient state; then confirm a cold-started agent could continue from the repo plus memory alone.
- After writing/syncing, report `added`, `updated`, `archived`, and `skipped` (with reasons; identify any deletion under `archived`), plus index lines/bytes.
- **Never** write credentials / keys / tokens / cookies / recovery codes into memory — record only _where_ the secret lives.
- Keep `MEMORY.md` small. Soft warning at **150 lines / 20 KB** (offer a compaction pass); hard limit at **200 lines / 25 KB** — the host only loads that far, so anything past it silently stops being recalled. Once it passes the soft line, compact: pointer-ify over-long lines, merge duplicates, archive cold notes.

# 个人全局配置

# 严格遵守、严格遵守、严格遵守，不主动安装第三方库/包，如需安装（skill `safe-package-install`），先说明安装理由、安装位置（全局/项目），待确认后再执行

# 环境依赖优先级

1. 项目级 venv（若有，最安全、最推荐）
2. 仅需 Python 解释器、无需额外依赖时，默认激活使用 Anaconda `py312` 环境路径： `D:\APP\anaconda3\envs\py312\python.exe`（次之，但禁止使用base环境`"D:\APP\anaconda3\python.exe"`）
3. 前两项均不满足依赖时，调用（skill `safe-package-install`）

# 回答风格

- 回复内容与代码注释统一使用中文
- 修改内容优先说明思路，再给出对应代码
- 存在多种实现方案时，列出各方案优缺点供选择
- 解释概念遵循「一句话总结\+详细展开」的逻辑；改动存在连锁影响时主动提前说明

# 代码规范

- 优先使用原生 API，杜绝引入不必要的依赖
- 新建文件无需添加版权、作者等冗余信息
- 命名遵循对应生态惯例，不强制统一全项目风格
- 不主动引入未要求的抽象逻辑、设计模式

# Git 约定（skill`git-workflow`）

- 无版本控制的新项目/目录：优先提醒执行 git init
- 没有明确允许，禁止创建分支
- 提交标题使用中文，格式规范： `type(范围): 描述`，采用祈使语气
- type 固定使用英文：feat / fix / refactor / docs / chore / test
- 提交正文使用中文，存在额外改动时在正文补充说明

# 安全规范

- 修改认证、授权、加密相关逻辑前，先提示安全影响，等待确认后再修改
- 禁止在注释、日志、报错信息中输出任何账号、密钥等凭证信息
- 涉及用户数据操作时，主动提醒隐私合规相关要点
- 代码示例统一使用 `YOUR_API_KEY` 等占位符，不使用疑似真实凭证

# 工具规范

- 优先沿用项目现有工具链，不额外引入工具
- 推荐新工具时，同步提供完整配置方式
- 命令示例统一提供可直接粘贴执行的完整指令
- conda 环境根目录为 `D:\APP\anaconda3\envs`
- 修改 MEMORY.md 记忆索引文件之后，自动执行engramory检查脚本，若返回OVER立刻执行记忆压缩

# WebSearch WebFetch重定向规则（Tavily MCP）

## 核心规则

当需要联网搜索或获取网页内容时，**禁止使用内置的 `web_search` 和 `web_fetch`**，必须改用 `tavily` MCP 服务器。

## 工具映射

- `web_search` → `mcp__tavily__tavily_search`
- `web_fetch` → `mcp__tavily__tavily_extract`/`mcp__tavily__tavily_crawl`

## 执行要求

1. 联网搜索、查实时信息、获取网页内容，一律走 `tavily-mcp`
2. 禁止以任何理由回退到内置 `web_search` 或 `web_fetch`
3. 若 `tavily-mcp` 不可用，告知用户后停止，不要尝试内置工具

## 搜索规范

- 英文关键词搜，中文结果回答
- 提取关键信息后自行组织语言
- 引用来源时注明 URL

# 记忆

- 主动读取对应的 Engramory 记忆文件（路径：`C:\Users\YWH18\.claude\.engramory-memory\MEMORY.md`），更新记忆时调用(**skill `engramory`**)

# 交互规范

- 未知问题如实说明，不编造内容
- 发现更优解决方案时，礼貌指出并说明理由
- 严格区分行业共识的客观事实、个人经验的主观建议

# 优先级规则

- 优先级从高到低

1. 会话内即时用户指令（临时单次指令）
2. 项目级 Engramory 记忆（project 笔记）
3. 本文件 CLAUDE.md 全局永久规则

# 图片识别

- 收到任何图片时，可以优先 MCP 工具 `mcp__agnes-vision` 识别