Awolf81 Memory Lane
awolf81-memory-lane is a Claude Code plugin for the Build phase that provides zero-config, locally extracted persistent project memory so Claude injects only relevant context.
by AWolf81 · github.com/AWolf81/memory-lane
Give Claude Code persistent, locally extracted project memory so only relevant context is injected each session without manual note files.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install awolf81-memory-lane@AWolf81/memory-laneBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:AWolf81/memory-lane") and the paste-ready config with skillselion.get_install_config("plugin:AWolf81/memory-lane").
What it does
awolf81-memory-lane (MemoryLane) is a Claude Code plugin that tackles the solo builder’s recurring problem: every new session starts cold and you re-upload architecture decisions, naming conventions, and half-finished tasks. MemoryLane extracts knowledge locally from your project and injects a focused slice of what matters instead of dumping the whole repo into context. That makes it journey-wide infrastructure—you benefit during build, ship reviews, launch tweaks, and operate iterations whenever you touch the same codebase. It is positioned as automatic and zero-config relative to hand-maintained memory files, with emphasis on persistence and token savings rather than a one-shot code generator. Install it when you run Claude Code daily on one product and want the agent to accumulate durable recall without wiring a separate vector stack. It complements skills and MCP tools but does not replace explicit PRDs or security audits.
Highlights
- Durable project memory for Claude Code with local knowledge extraction
- Injects only what matters per turn to reduce repeated explanations
- Zero-config positioning—automatic memory without manual MEMORY.md curation
- Persistent context savings across long solo-builder sessions
- Single-plugin bundle focused on memorylane workflow keywords
Why builders use it
Solo builders waste time re-teaching Claude the same project facts every session because nothing durable and selective persists locally.
Claude Code sessions start with automatically surfaced project knowledge so you ship faster with fewer repeated prompts and smaller redundant context.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is awolf81-memory-lane for?
Solo builders and indie developers who use Claude Code repeatedly on the same project and need durable, selective project memory.
When should I use awolf81-memory-lane?
Use it from first serious build work through ongoing operate iterations whenever Claude should remember prior decisions without you restating them.
How do I add awolf81-memory-lane to my agent?
Install the MemoryLane plugin from AWolf81/memory-lane in Claude Code; zero-config setup lets local extraction run as you work in the project directory.
Comments
Share how you use awolf81-memory-lane, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.