brain-docslisted

Set up and maintain a "project brain" — a brain/ folder holding three living documents (decisions.md, flow.md, todo.md) that give a project persistent memory across chat sessions. Use this skill whenever the user wants a decision log, architecture/flow notes, project memory, living documentation, or notes that survive between sessions ("set up a project brain", "start a decision log for this repo", "remember why we chose X"). Also use it in any repo that already has a brain/ folder: after completing a meaningful code change, when the user says "update the brain docs" or "log this decision", when a risk/limitation/idea surfaces worth writing down, or when the user asks why a past decision was made (read decisions.md before answering).
IAbhishekJhaI/brain · ★ 3 · AI & Automation · score 64

Install: claude install-skill IAbhishekJhaI/brain

# brain-docs — a living project memory Chat sessions end; the reasoning behind code shouldn't. This skill maintains a `brain/` folder of three documents that together act as the project's memory: | File | Holds | Answers | |---|---|---| | `brain/decisions.md` | Dated decision log (newest first) | "Why is it built this way?" | | `brain/flow.md` | Whole-system execution flow | "What calls what, in what order?" | | `brain/todo.md` | Tagged action items, caveats, ideas | "What's known-broken, known-limited, or worth doing?" | The system only works if the docs are updated **incrementally, as you work** — not in a batch when someone remembers to ask. A future session (or a future maintainer) relies on them being current. There are two modes. Check whether `brain/` exists in the project root: - **No `brain/` folder, or the user asks to set one up → Setup mode.** - **`brain/` exists → Maintain mode.** --- ## Setup mode 1. **Create `brain/`** in the project root and seed the three files from `assets/templates/` (in this skill's folder). Adapt each file's title line to the project's name; keep the maintenance blockquotes — they remind future sessions of the rules even if this skill doesn't load. 2. **Ask whether `brain/` should be git-ignored.** Don't assume — this is a real tradeoff the user owns: - *Git-ignored (local)*: the notes can be candid — honest tradeoffs, "this is a hack", API-billing gripes — because nobody else reads them. But they live on