When does Claude proactively save to memory?

The skill triggers whenever you finalize a technology choice, solve a complex bug, establish a new convention, or explicitly use keywords like 'remember' or 'important'.

What kind of information should I store in the memory bank?

You should store architectural choices, trade-offs (e.g., 'sacrificing X for Y'), technology justifications, and business requirements that impact code structure.

How does Hindsight help with architectural decisions?

It automatically searches your project's memory bank before suggesting design patterns, ensuring new recommendations align with your established architectural history.

Can I search for specific past decisions?

Yes, you can use the recall command with specific queries and adjustable budget levels (low, mid, high) to find historical context related to any topic.

Hindsight Memory Bank

Name: Hindsight Memory Bank
Author: abix5

byabix5

Productivity & Workflow

Enhances Claude's long-term memory to track architectural decisions, technology choices, and project trade-offs across development sessions.

About

The Hindsight Memory Workflow provides Claude with a persistent memory bank to store and retrieve critical project context. It automates the process of documenting architectural decisions, complex bug fixes, and development conventions, ensuring that Claude remains aligned with established patterns. By proactively recalling past discussions and retaining new insights, it prevents context loss and helps maintain consistency in large-scale software development projects, acting as an automated 'ADR' (Architecture Decision Record) system.

Key Features

Automated retention of decisions, bug fixes, and trade-offs with context tracking
0 GitHub stars
AI-driven reflection to analyze historical patterns and project conventions
Proactive memory recall before making architectural or technology recommendations
Automatic bank resolution based on git repositories or directory structures
Structured categorization including architecture, tech-stack, bugs, and lessons

Use Cases

Onboarding Claude to a project's specific conventions and previous tech-stack choices
Maintaining architectural consistency during long-term feature development
Documenting the rationale behind complex bug fixes to prevent future regressions

About

Key Features

Automated retention of decisions, bug fixes, and trade-offs with context tracking
0 GitHub stars
AI-driven reflection to analyze historical patterns and project conventions
Proactive memory recall before making architectural or technology recommendations
Automatic bank resolution based on git repositories or directory structures
Structured categorization including architecture, tech-stack, bugs, and lessons

Use Cases

Onboarding Claude to a project's specific conventions and previous tech-stack choices
Maintaining architectural consistency during long-term feature development
Documenting the rationale behind complex bug fixes to prevent future regressions