ihow-memorylisted

# Using iHow Memory well iHow Memory is a local-first memory layer exposed over MCP. It does **not** silently capture your whole session in the background as a substitute for recording — the memory you can rely on exists because you (or, at session end, a cooperative hook prompt) call its tools. (A low-weight automatic floor exists as a backstop, but it ranks below everything you record.) This skill is the discipline for when to call those tools, so a future session — or a different agent — can pick up where you left off. The tools: `memory.search`, `memory.read`, `memory.write_candidate`, `memory.promote`, `memory.durable_promote`, `memory.status`. Writes are governed: `write_candidate` is the **one call to remember** — the engine auto-promotes qualifying low-risk content that carries provenance and leaves everything else a candidate. The engine, not your judgment, gates what reaches durable memory. ## To resume after a context boundary — `continue`, don't re-brief If the user says "continue", "接着上面的做", "resume", "pick up where we left off", or you're starting fresh in a project that was clearly mid-task, run **`ihow-memory continue`**. It detects the project you were working on from the files you EDITED (so it works even when every session launches from one terminal dir), and prints a handoff: that project's git anchors (the only facts) + the previous session's own summary, quoted and marked **UNVERIFIED**. If the user works on several projects, pass a keyword: **`ihow-