agent-memory

Agent Memory — Unified Skill

This skill unifies three complementary capabilities into a single, coherent workflow:

1. /learn — Session Memory Management — Persist, search, prune, and export what the agent has learned about your codebase and project across sessions.
2. /browse — Browser-Based QA Testing — Drive real Chromium (headless or headed), click elements, take screenshots, import cookies, and assert page state for production-grade QA.
3. /pair-agent — Multi-Agent Coordination — Spawn parallel sub-agents on isolated scopes, aggregate results, and hand off context cleanly between agents.

---

Part 1 — Memory Management (/learn)

1.1 Philosophy: Why Memory Matters

Every time the agent explores your codebase, it discovers implicit patterns that are expensive to rediscover:

• Which modules are load-bearing vs. experimental
• Naming conventions that are project-local (not language-default)
• Fragile integration points that have broken before
• Performance invariants the team cares about
• Domain-specific jargon used in comments and variable names

Without memory, the agent starts cold every session. With memory, compound knowledge accumulates — each session builds on prior sessions, reducing repeated archaeology and increasing the precision of every suggestion.

Principle: Memory is a first-class engineering artifact. Treat it like documentation.

---

1.2 Memory Scopes

There are two distinct scopes of memory. Always be explicit about which scope you are reading from or writing to.

Global Memory (~/.agent-memory/global/)

Stores patterns that apply across all projects on this machine:

• Preferred code style decisions (e.g., "always use early-return guards")
• Recurring architectural preferences (e.g., "prefer repository pattern over active record")
• User-level shortcuts and workflow preferences
• Learned tool behaviors (e.g., "this user's Makefile uses make lint not make check")

Project Memory (<repo-root>/.agent-memory/)