precedentlisted

Remember and reuse the user's architectural, business, and tooling decisions across every project, in a queryable graph. Use this skill whenever the user settles a non-trivial choice (database, framework, auth, deployment, pricing, process) so it gets recorded; whenever they start work in a project you have not briefed on yet, including one that predates the graph and whose decisions are only visible in its manifests, CI and docs; whenever they weigh options and ask "which should I use" or "what did I do last time"; whenever they say a past choice was a mistake, that it bit them, or that they would not do it that way again; whenever they knowingly depart here from how they usually do it; and whenever they ask what they have already decided, whether a choice is consistent with their other projects, or what decisions they still owe this project. Trigger it even when the user does not mention decisions, memory, or the graph — the point is that they should not have to remember to ask.
asm0dey/precedent · ★ 0 · Data & Documents · score 70

Install: claude install-skill asm0dey/precedent

# Decision graph This is Claude Code's adapter onto `precedent`, a decision graph that also reaches Codex and Cursor (see the repo's top-level README for the other install channels). The user's decisions are scattered across dozens of repos and two years of conversations they no longer remember. The graph keeps them in one place, so a choice made in one project informs the next one, from whichever agent looks it up. Everything goes through one script, shared by every adapter. It handles locking, the append-only journal, project typing, and the inference queries, so you write no Cypher for normal work. `<skill>` below is this file's own directory (`adapters/claude/skills/precedent/` in the repository, or wherever it was installed as `~/.claude/skills/precedent`). The script lives at the package root's `scripts/precedent.py`: ```bash uv run <skill>/../../../../scripts/precedent.py <command> [flags] ``` An `acr realize` install puts the script beside the skills instead, at `../../scripts/*/precedent.py` from here. The session brief prints the resolved path either way — prefer that over recomputing it. `uv` fetches the dependency on first run — there is no install step. If `uv` is missing, `pip install graphdblite` and run with `python`. ## The task skills beside this one Nine skills cover the daily paths without going through this document. They are directories beside this one, so every install channel ships them: a plugin install discovers them by convention, and `acr r