memory-bank

Scaffold a memory_bank directory with five markdown files and templates.

2|Updated Apr 3, 2026

Search Tags:#templates #documentation #context #memory #persistence #knowledge #cursor10x

Ready to run

npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill memory-bank-kscius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-bank
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/memory-bank
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill memory-bank-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Scaffold and maintain a /memory_bank/ directory in any project to provide persistent, human-readable context that survives tool changes and supplements session memory.

Core Features & Use Cases

Five-file memory spine: creates and updates a stable set of files that capture project overview, technical context, system patterns, active focus, and progress.
Templates and templates reuse: includes reference templates to guide content creation and consistency across teams.
Lifecycle integration: harmonizes with devcontext and cursor10x workflows to enrich memory and decision history in Cursor.
Use Case: starting a new project, resuming after a long gap, or when users request to "set up memory" or "create a memory bank" for a project.

Quick Start

Create the memory_bank/ directory at the project root, then initialize the five markdown files using the provided templates.

Frequently Asked Questions about memory-bank

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

FAQPage Schema

How do I preserve project context across sessions when changing tools?▼

To preserve project context across sessions, scaffold a memory_bank directory containing five markdown files that capture project overview, technical context, system patterns, active focus, and progress for persistent human-readable reference.

What is the best way to set up persistent documentation for a new project?▼

Setting up persistent documentation involves creating a memory_bank directory at your project root and initializing five markdown files using provided reference templates to ensure consistent context and knowledge capture across teams.

How does a memory bank structure work with Cursor workflows?▼

A memory bank structure integrates with devcontext and cursor10x workflows by maintaining a stable five-file spine of markdown documentation that enriches memory and anchors decision history directly within the Cursor environment.

Can I use reference templates to maintain consistent project context across teams?▼

Yes, you can use included reference templates to guide content creation within the memory_bank directory, ensuring stable and consistent documentation of technical context and project patterns across your entire team.

When do I need to create a memory bank for my project?▼

You need to create a memory bank during project initiation, when resuming work after a long absence, or when you explicitly request a memory setup to anchor and supplement session context.

What files are required to scaffold a memory bank directory?▼

Scaffolding a memory bank directory requires creating five markdown files that respectively capture project overview, technical context, system patterns, active focus, and progress, along with their associated reference templates.