session-memory
FeaturedSave, recall, compare or cross-reference Design System Ops findings across runs in .ds-ops/sessions/. Triggers: save these findings, what did we find last time, compare with last run, what changed since. Not for producing a new audit (run that skill) or a full sweep (full-diagnostic).
Install
Quality Score: 90/100
Skill Content
Details
- Author
- murphytrueman
- Repository
- murphytrueman/design-system-ops
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
session-audit
End-of-session audit that scans the conversation for corrections, preferences, decisions, and new context that were never saved, then proposes where each belongs in the user's memory files (CLAUDE.md, MEMORY.md, or a memory/ folder). Use whenever the user says "audit this session", "session audit", "what did we miss", "end of session check", or asks to capture what was learned before closing a session. Adapts to whatever memory structure the workspace already has, and proposes a simple one if none exists.
save-session
MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands; also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.
memo-session-skill
Persistent AI agent memory for coding sessions — cross-session knowledge that survives context window resets. Consolidates session noise into durable facts and routes them via memory routing into MEMORY.md, memory/ HOT/WARM/COLD layers, project wiki, AGENTS.md, skills, and optional portfolio memory — git-tracked, with conflict gate and temperature limits. Stateful handoff when volatile chat context is lost; complements vector RAG or managed memory platforms, does not replace them. Use when the user says "wrap up the session", "save what we learned", "handoff", "open loops", "update memory", "agent memory", "persistent memory", "cross-session persistence", "how to give my agent memory", or when another skill requests a memory checkpoint. Also for portfolio/global memory, bootstrap project memory, session changelog, `/inbox`, process inbox, or ingest files from memory/inbox. When memo-session-mcp is connected, use search_all for portfolio/project lookup and reindex_changed after writes. Prefer after non-trivial