eaa-session-memory

Record architecture decisions and design context to file-based storage.

Updated Aug 23, 2026

Search Tags:#architecture #state management #session memory #handoffs #context persistence #design decisions

Ready to run

npx skills add https://github.com/Emasoft/emasoft-architect-agent --skill eaa-session-memory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eaa-session-memory
Source: https://github.com/Emasoft/emasoft-architect-agent/tree/main/skills/eaa-session-memory
Command: npx skills add https://github.com/Emasoft/emasoft-architect-agent --skill eaa-session-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill ensures that critical architecture decisions, design patterns, technology choices, and open questions are not lost between design sessions, enabling seamless continuity and preventing rework.

Core Features & Use Cases

Persistent Memory: Saves and loads architecture decisions, constraints, and design patterns.
Session Continuity: Restores the agent's context when resuming work.
Handoffs: Creates documents to transfer design state between sessions or agents.
Use Case: After a long design session, you can close your laptop. The next day, the Architect agent will automatically load all previously made decisions and continue from where you left off, without needing to re-explain anything.

Quick Start

When the design session starts, load the existing session memory to restore context.

Frequently Asked Questions about eaa-session-memory

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

FAQPage Schema

How do I preserve architecture decisions and design context across sessions?▼

Session memory persistence saves architecture decisions, design patterns, technology choices, and open questions to file-based storage, ensuring continuity and preventing rework between design sessions.

What is the best way to transfer design state between agents or sessions?▼

Creating handoffs transfers design state between agents or sessions by generating documents that capture architecture decisions and open questions for seamless state transfer and context restoration.

How does context persistence work for restoring an agent's previous work?▼

Context persistence restores the agent's previous work by loading existing session memory from file-based storage at session start, automatically retrieving all recorded design decisions and constraints.

Can I resume a long design session without re-explaining previous technology choices?▼

Yes, session continuity automatically loads previously made decisions, technology choices, and constraints when resuming work, allowing the Architect agent to continue from where you left off without re-explanation.

What architecture details does session memory record for future reference?▼

Session memory records architecture decisions, design patterns, technology choices, constraints, and open questions to file-based storage, preserving critical design context for future reference and continuity.

When do I need session memory management for design work?▼

Session memory management is needed when design work spans multiple sessions and requires preserving architecture decisions, constraints, and open questions to prevent losing critical context and avoid rework.