← ClaudeAtlas

maxpool-builderlisted

Pick up and maintain this repo's project memory. Invoke at the START of a work session to load full context (CLAUDE.md + docs/CONTEXT.md + unreleased commits), and to APPEND decisions/changes to docs/CONTEXT.md as they happen, and at WRAP-UP to leave the memory current for the next session. Use when the user says "catch up", "where were we", "log this decision", "update context", or "wrap up".
2solarmax/maxpool · ★ 2 · Web & Frontend · score 75
Install: claude install-skill 2solarmax/maxpool
# Project-memory builder Keeps a fresh Claude Code session productive on this repo by making the project memory a living thing: read it in, keep it current, hand it off. The mechanics below are **project-agnostic** — they operate on *this repo's* files, so this skill is also the reusable seed for standing the same harness up in another repo (see "Reuse in another project" at the end). The two backing stores: - **`CLAUDE.md`** — durable facts + hard invariants. Always loaded. Rarely changes. - **`docs/CONTEXT.md`** — living state + append-only decision log. Changes often. ## START of a session — load context A SessionStart hook already injects the memory head, but on any non-trivial task confirm the full picture: 1. Read **`CLAUDE.md`** (facts + invariants you must not break). 2. Read **`docs/CONTEXT.md`** — the **Current focus** and the top few **Decisions**. 3. Check what changed but isn't released: `git log $(git describe --tags --abbrev=0)..HEAD --oneline`. 4. If anything in the code contradicts the memory, trust the code and fix the memory (a stale note is worse than none) — then note the correction. State back, in one or two lines, where things stand before you start. ## DURING work — append as you go (the load-bearing habit) The memory only works if it's written **the moment a decision is made or a change ships**, in-thread — not saved for "the end," which gets skipped. After each: - a **decision** (an approach chosen, a trade-off settled, a constraint accep