Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From nemp
Manages persistent local memory in .nemp/memories.json for Claude Code agents, storing project stack, architecture decisions, user preferences, and enabling cross-session context retention.
npx claudepluginhub sukinshetty/nemp-memory --plugin nempHow this skill is triggered — by the user, by Claude, or both
Slash command
/nemp:nemp-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
\# Nemp Memory — Persistent Local Memory for Claude Code
Loads and applies project memories from prior sessions for consistent decisions, conventions, and preferences. Stores new entries automatically or via /remember.
Manages persistent memory across Claude Code sessions via AutoMem. Recall project context, architectural decisions, bug fixes, user preferences, and patterns at session start or debugging.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
# Nemp Memory — Persistent Local Memory for Claude Code
You have access to a local memory system stored in .nemp/ in the project root. Use it to persist context across sessions so users never have to repeat themselves.
## When to Use This Skill
- **Session start**: Always check for existing memories by reading .nemp/memories.json
- **Architecture decisions**: Save decisions so future sessions know why
- **Stack detection**: On first use, auto-detect the project stack and save it
- **User preferences**: Save coding style, conventions, patterns the user prefers
- **Agent coordination**: When working with other agents, save context they'll need
## Memory Storage Format
Memories are stored in .nemp/memories.json as an array of objects with keys: key, value, tags, timestamp, source, agent_id.
## How to Save a Memory
Read .nemp/memories.json, add or update the entry, write back. Rules:
- Compress values: remove filler words, keep under 200 chars
- Use descriptive keys: auth-provider, database, styling-framework
- Tag appropriately: stack, architecture, convention, preference, api
- Track agent_id: use "main" for single agent or your agent name
- Upsert: if key exists, update it
## How to Recall Memories
Search .nemp/memories.json with keyword expansion:
- auth -> authentication, login, session, jwt, token, oauth
- database -> db, postgres, mysql, sqlite, mongo, prisma, drizzle
- styling -> css, tailwind, sass, scss, styled-components, shadcn
- testing -> test, jest, vitest, cypress, playwright, e2e
- deploy -> deployment, docker, vercel, netlify, aws, ci, cd
## Auto-Detection (First Session)
Scan package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml, tsconfig.json, docker-compose.yml, .env to auto-detect stack. Save each with source: "auto-detect" and agent_id: "nemp-init".
## Access Logging
Log every operation to .nemp/access.log with timestamp, operation, key, and agent.
## Critical Rules
1. ALL data stays local. Never make network calls.
2. Create .nemp/ directory if it doesn't exist.
3. Always read before write to avoid overwriting other agents' memories.
4. Compress aggressively — keep values under 200 chars.
5. Log every operation to .nemp/access.log.
6. Regenerate .nemp/MEMORY.md after every write/delete.