litopys-memorylisted

# Litopys Memory Persistent graph memory across sessions. The MCP server already injects 5 baseline rules (SEARCH FIRST · CREATE ON LEARNING · LINK AFTER CREATING · AVOID DUPLICATES · QUALITY THRESHOLD). **This skill goes further** — covers what those rules don't: graph traversal, temporal awareness, conflict resolution, constraint-aware writes. ## Customize this skill After installing, open `SKILL.md` and replace the generic trigger description above with the **exact project and system names from your graph**. Run `litopys startup-context` or ask `litopys_search("projects")` to see them. This makes the skill fire at the right moments instead of relying on generic phrasing. ## Iron Law **No factual claim about user-specific things without searching the graph first.** Applies to: the user's projects, systems, infrastructure, people, past decisions, recurring problems. Does NOT apply to: generic programming questions, library docs, syntax, code review unrelated to the user's stack. ## Four Disciplines ### 1. Reading — Search + Traverse (top pain) Plain `litopys_search` returns flat results. The graph carries meaning in **edges**. Every search must be followed by traversal when the answer needs context. ``` Step 1: litopys_search("keyword") → find candidate nodes Step 2: litopys_get(id) → full body if needed Step 3: litopys_related(id) → MANDATORY for any non-trivial answer Step 4: Check supersedes chains → incoming supersedes = node