memory-bank — for Claude Code memory-bank, claude-code-deprecated, community, for Claude Code, ide skills, architecture.md, decisions.md, patterns.md, troubleshooting.md, api-surface.md

v1.0.0
GitHub

Acerca de este Skill

Escenario recomendado: Ideal for AI agents that need skill: memory bank — structured project knowledge sync. Resumen localizado: Acts as a long-term knowledge layer that survives context compaction and session resets. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Características

Skill: Memory Bank — Structured Project Knowledge Sync
Build and maintain a structured memory bank at .claude/memory/ that stays
synchronized with code changes. Acts as a long-term knowledge layer that survives
context compaction and session resets.
Inspired by russbeye/claude-memory-bank.

# Core Topics

for Claude Code architecture.md decisions.md patterns.md troubleshooting.md api-surface.md
Wellux Wellux
[1]
[0]
Updated: 4/6/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
70
Canonical Locale
en
Detected Body Locale
en

Escenario recomendado: Ideal for AI agents that need skill: memory bank — structured project knowledge sync. Resumen localizado: Acts as a long-term knowledge layer that survives context compaction and session resets. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Por qué usar esta habilidad?

Recomendacion: memory-bank helps agents skill: memory bank — structured project knowledge sync. Acts as a long-term knowledge layer that survives context compaction and session resets. This AI agent skill supports

Mejor para

Escenario recomendado: Ideal for AI agents that need skill: memory bank — structured project knowledge sync.

↓ Casos de uso accionables for memory-bank

Caso de uso: Applying Skill: Memory Bank — Structured Project Knowledge Sync
Caso de uso: Applying Build and maintain a structured memory bank at .claude/memory/ that stays
Caso de uso: Applying synchronized with code changes. Acts as a long-term knowledge layer that survives

! Seguridad y limitaciones

  • Limitacion: Use /context-diff first to understand what changed, then update only the relevant warm-tier files.
  • Limitacion: Requires repository-specific context from the skill documentation
  • Limitacion: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is memory-bank?

Escenario recomendado: Ideal for AI agents that need skill: memory bank — structured project knowledge sync. Resumen localizado: Acts as a long-term knowledge layer that survives context compaction and session resets. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install memory-bank?

Run the command: npx killer-skills add Wellux/claude-code-deprecated/memory-bank. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for memory-bank?

Key use cases include: Caso de uso: Applying Skill: Memory Bank — Structured Project Knowledge Sync, Caso de uso: Applying Build and maintain a structured memory bank at .claude/memory/ that stays, Caso de uso: Applying synchronized with code changes. Acts as a long-term knowledge layer that survives.

Which IDEs are compatible with memory-bank?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for memory-bank?

Limitacion: Use /context-diff first to understand what changed, then update only the relevant warm-tier files.. Limitacion: Requires repository-specific context from the skill documentation. Limitacion: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Wellux/claude-code-deprecated/memory-bank. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use memory-bank immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

memory-bank

Acts as a long-term knowledge layer that survives context compaction and session resets. This AI agent skill supports Claude Code, Cursor, and Windsurf

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Skill: Memory Bank — Structured Project Knowledge Sync

Role

Build and maintain a structured memory bank at .claude/memory/ that stays synchronized with code changes. Acts as a long-term knowledge layer that survives context compaction and session resets. Inspired by russbeye/claude-memory-bank.

Memory Bank Structure

.claude/memory/
├── hot/
│   └── hot-memory.md          # Always loaded (≤50 lines, key active context)
├── warm/
│   ├── architecture.md        # System design, component relationships
│   ├── decisions.md           # Key decisions with rationale
│   ├── patterns.md            # Recurring code patterns, idioms
│   ├── troubleshooting.md     # Known issues, workarounds, gotchas
│   └── api-surface.md         # Public API contracts and conventions
└── glacier/
    └── YYYY-MM-DD-<slug>.md   # Archived decisions + historical context

When to invoke

  • After a major refactor (sync architecture.md)
  • After resolving a tricky bug (sync troubleshooting.md)
  • After adding a new API endpoint (sync api-surface.md)
  • After making an architectural decision (sync decisions.md)
  • Periodically to keep memory current

Instructions

Full sync

  1. Read all source files in scope (or all of src/ for full sync)
  2. Compare against existing warm-tier files
  3. Update each warm-tier file with what's changed:
    • architecture.md: component diagram, module responsibilities, data flow
    • decisions.md: key choices with WHY, not just what
    • patterns.md: recurring idioms, anti-patterns seen
    • troubleshooting.md: tricky bugs, gotchas, workarounds
    • api-surface.md: endpoint signatures, request/response models
  4. Update hot-memory.md with any critical new facts (keep ≤50 lines)
  5. Archive stale but important context to glacier

After a specific change

Use /context-diff first to understand what changed, then update only the relevant warm-tier files.

Query mode

/memory-bank query "src/auth/**" — surface relevant warm-tier documentation for a path

Path-Filtered Query

When given a path argument:

  1. Identify which warm-tier file covers that domain
  2. Return the relevant section
  3. Note if it's stale (last updated >2 weeks ago)

Output

## Memory Bank Sync: <scope>

### Updated
- warm/architecture.md → added FastAPI middleware order diagram
- warm/decisions.md → logged setuptools.build_meta decision
- warm/troubleshooting.md → added exc_info filtering gotcha

### Hot memory: updated active_feature key

### No changes needed
- warm/api-surface.md (current)
- warm/patterns.md (current)

### Archived to glacier
- Old routing design (pre-v0.9.0) → glacier/2026-04-05-routing-v1.md

Habilidades relacionadas

Looking for an alternative to memory-bank or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Generar complementos de widgets personalizables para el sistema de feeds de prompts.chat

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

El Marco de React

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Tensores y redes neuronales dinámicas en Python con fuerte aceleración de GPU

★ 98.6k
⑂ 0
Desarrollador