One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill memory-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/memory
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill memory-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing important project context, architectural decisions, and team preferences when starting new Claude Code sessions, eliminating the need to repeatedly re-explain foundational project details to the AI.

Core Features & Use Cases

  • Multi-type memory storage: Save and categorize memories as decisions, patterns, context, preferences, warnings, or todos for organized retrieval.
  • Auto-recall on session start: Automatically surfaces critical importance memories and recent entries (last 7 days) when you launch a new session, so you don't have to manually re-share context.
  • Search and export functionality: Search memories by content, context, or tags, and export all stored memories for backup or sharing with team members.
  • Use Case: For example, if your team decides to switch validation libraries from Joi to Zod, you can save this as a high-importance decision memory, and every new Claude Code session will automatically know to use Zod for all validation tasks.

Quick Start

Use the memory skill to save your team's decision to use Zod for API validation as a high-importance memory so it is automatically recalled in all future coding sessions.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I persist project context across Claude Code sessions?

To persist project context across Claude Code sessions, store architectural decisions, team preferences, and coding context as tagged, importance-ranked memories with auto-recall triggers for critical entries, eliminating redundant context re-explanation in new sessions.

What is cross-session knowledge retention for coding projects?

Cross-session knowledge retention is storing critical project context, architectural decisions, and team preferences so new sessions automatically recall them. It prevents inconsistent implementation choices and repeated onboarding of foundational context in long-running software engineering projects.

How do I stop re-explaining architectural decisions to AI in every new session?

Save architectural decisions as high-importance memory entries with auto-recall triggers. When you launch a new session, critical importance memories and recent entries from the last 7 days are automatically surfaced, ensuring consistent implementation choices without manual re-explanation.

Can I categorize saved memories by type for organized retrieval?

Yes, you can save and categorize memories as decisions, patterns, context, preferences, warnings, or todos for organized retrieval. This multi-type memory storage allows structured management of different kinds of project knowledge across coding sessions.

How do I share saved project knowledge with team members?

Export all stored memories for backup or sharing with team members. The search functionality also allows you to find specific memories by content, context, or tags, making it easy to distribute critical project context across your engineering team.

Does this memory management skill work for long-running software engineering projects?

Yes, this memory management skill is designed specifically for long-running software engineering projects where session state loss causes repeated onboarding of foundational context and inconsistent implementation choices, satisfying cross-session knowledge retention requirements through tagged, importance-ranked memories.