From memstack
Updates or creates CLAUDE.md files across projects after significant changes. Reads config.json, identifies what changed (APIs, tables, components, env vars), and appends new entries under the correct sections.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memstack:grimoireThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
*Manage and update CLAUDE.md files across all projects.*
Manage and update CLAUDE.md files across all projects.
When this skill activates, output:
📖 Grimoire — Updating the knowledge library.
Then execute the protocol below.
User: "update claude.md with the CC Monitor stuff"
📖 Grimoire — Updating the knowledge library.
Reading: C:\Projects\AdminStack\CLAUDE.md
Adding to API Endpoints:
- POST/GET/PATCH/DELETE /api/cc-sessions
- POST /api/cc-sessions/report
Adding to Database Schema:
- cc_sessions (020_cc_sessions.sql)
Adding to Environment Variables:
- CC_MONITOR_API_KEY
CLAUDE.md updated ✓
npx claudepluginhub cwinvestments/memstack --plugin memstackCaptures conversation outcomes into CLAUDE.md — decisions, preferences, patterns, and conventions established during the session.
Updates, refreshes, optimizes, and cleans up CLAUDE.md by exploring codebase, removing stale content, and restructuring for scannability. Use when docs are out of sync.
Guides effective maintenance of CLAUDE.md files: adding lessons learned, updating conventions, restructuring instructions. Covers when to update/remove rules, structure templates, hierarchy, and size limits.