project-memory

Creates and maintains structured project memory files tracking bugs, decisions, facts, and work history.

89|13|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/SpillwaveSolutions/project-memory --skill project-memory-spillwavesolutions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-memory
Source: https://github.com/SpillwaveSolutions/project-memory
Command: npx skills add https://github.com/SpillwaveSolutions/project-memory --skill project-memory-spillwavesolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding assistants start every session with zero knowledge of your project, causing repeated debugging of solved bugs, architectural decisions that conflict with past choices, and constant re-asking for configuration details. This Skill establishes a persistent institutional knowledge system in docs/project_notes/ so context survives across sessions, team members, and AI tools. ## Core Features & Use Cases - Memory Infrastructure Setup: Creates four structured files in docs/project_notes/: bugs.md (bug log with solutions), decisions.md (Architectural Decision Records), key_facts.md (project configuration), and issues.md (work log with ticket references). - Memory-Aware Configuration: Updates CLAUDE.md and AGENTS.md with protocols so AI tools check memory files before proposing changes, search for known bug solutions, and document new decisions automatically. - Templates and Security Guidelines: Provides ready-to-use templates for all four memory files, including explicit rules about never storing credentials or secrets in version-controlled files. - Use Case: A deployment fails with a Pulumi state drift error. Instead of 45 minutes of debugging, the AI searches bugs.md, finds the documented solution (pulumi refresh --yes), and applies the fix in minutes. ## Quick Start Ask the AI to set up project memory in this repository so it creates the docs/project_notes memory files and configures CLAUDE.md to track bugs, decisions, and key facts.

Frequently Asked Questions about project-memory

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

FAQPage Schema
How do I set up project memory for Claude Code?▼

Install the skill into ~/.claude/skills/ or your project's .claude/skills/ directory, then invoke /project-memory in Claude Code. It creates docs/project_notes/ with four memory files and updates CLAUDE.md with memory-aware protocols.

What files does a project memory system create?▼

It creates four Markdown files in docs/project_notes/: bugs.md for bug logs with solutions, decisions.md for Architectural Decision Records, key_facts.md for project configuration, and issues.md for work logs with ticket references.

Does project memory work with Cursor and GitHub Copilot?▼

Yes, the memory system works across AI tools because it stores knowledge in standard Markdown files and configures both CLAUDE.md and AGENTS.md. Cursor, Copilot, and other tools that read project configuration files can follow the same protocols.

Can I store API keys or passwords in key_facts.md?▼

No, never store passwords, API keys, tokens, or credentials in key_facts.md since it is committed to version control. Store only non-sensitive references like hostnames, ports, and project IDs; keep secrets in .env files or secrets managers.

Why is the memory directory called project_notes instead of memory?▼

The docs/project_notes/ naming makes the files look like standard engineering documentation rather than AI-specific tooling. This increases adoption and maintenance by human developers on the team.