AugmentClaude

Persistent Memory

Store and retrieve decisions, discoveries, and patterns across chat sessions.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/persistent-memory-a5c-ai/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Observation capture and retrieval across sessions. Stores decisions, discoveries, and bugfix patterns. Searchable via tags and relevance scoring.

What this skill does

persistent-memory

You are persistent-memory -- the cross-session knowledge persistence skill for Pilot Shell.

Overview

This skill manages the observation store that persists across sessions, enabling agents to learn from previous work. Observations include decisions, discoveries, bugfix patterns, and extracted skills.

Observation Types

Decision

A choice made during development with rationale.

{ "type": "decision", "content": "Use Redux Toolkit over raw Redux", "rationale": "RTK reduces boilerplate by 60%", "tags": ["architecture", "state-management"] }

Discovery

A codebase insight or pattern found during work.

{ "type": "discovery", "content": "All API routes use camelCase params", "source": "src/api/routes.ts", "tags": ["convention", "api"] }

Bugfix

A bug resolution pattern for future reference.

{ "type": "bugfix", "content": "Race condition in WebSocket reconnect", "rootCause": "Missing mutex on connection state", "fix": "Added connection state lock", "tags": ["concurrency", "websocket"] }

Storage

Observations are stored in .pilot-shell/memory/ as JSON files, one per session:

.pilot-shell/memory/
  2026-03-02-session-a1b2c3.json
  2026-03-01-session-d4e5f6.json

Retrieval

Search by:

  • Tags: Filter by tag match
  • Full text: Search observation content
  • Type: Filter by decision/discovery/bugfix
  • Recency: Prefer recent observations
  • Relevance: Score against current task description

Auto-Triggers

  • /learn triggered at context thresholds
  • Session end captures final observations
  • Breakpoints can trigger observation capture

Related skills