ee-memory

Maintain persistent project memory with stable and volatile fact sections.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/6987zshmpy-bot/electrical-engineering-plugin --skill ee-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ee-memory
Source: https://github.com/6987zshmpy-bot/electrical-engineering-plugin/tree/main/skills/ee-memory
Command: npx skills add https://github.com/6987zshmpy-bot/electrical-engineering-plugin --skill ee-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent project memory manager ensures stable facts about a PCB design survive across sessions, reducing re-derivation and keeping context aligned as you resume work.

Core Features & Use Cases

  • Maintains a clear separation between stable facts (architecture, decisions) and volatile data (stock, part availability) to enable delta-checks only when needed.
  • Supports loading, updating, and querying the project memory to accelerate onboarding, project handoffs, and re-entry after interruptions.

Quick Start

Load the current project memory and resume work with the latest context.

Frequently Asked Questions about ee-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain project memory and design decisions across sessions?

Project memory persists by separating stable facts like design decisions from volatile data, enabling delta-checks to reload context and resume work without re-deriving previous conclusions.

What is the best way to resume work on a project after an interruption?

Resuming work after an interruption requires loading the existing project memory document to retrieve stable facts and volatile data, instantly restoring the latest context and accelerating re-entry.

How does separating stable facts and volatile data help with project handoffs?

Separating stable facts and volatile data enables delta-checks to identify only changed information, streamlining project handoffs and session-resume processes by preventing unnecessary full-context reloads.

Can I use a memory document to store PCB design context and part availability?

Yes, the memory document stores stable architecture decisions and volatile part availability data, maintaining consistent project context and supporting targeted delta-checks when stock or components change.

How do I update and query project memory for ongoing design work?

Updating and querying project memory uses a simple interface to modify the memory document, ensuring stable facts and volatile data sections reflect the latest design changes and session context.