This project provides a modular, graph-based task management framework for the Cursor IDE, designed to structure AI-assisted development workflows. It targets developers seeking a more organized and guided approach to coding, offering persistent memory and visual process maps across distinct development phases (Initialization, Planning, Design, Implementation).

How It Works

The system leverages Cursor's custom modes, extending them beyond simple AI personas into interconnected workflow components. It employs a Just-In-Time (JIT) rule loading architecture, ensuring only relevant rules are active for each phase, optimizing context usage. Modes transition logically (VAN → PLAN → CREATIVE → IMPLEMENT), with shared memory and adaptive behavior based on project complexity. QA functions are integrated and callable from any mode for technical validation.

Quick Start & Requirements

• Install: Clone the repository (git clone https://github.com/vanzan01/cursor-memory-bank.git) into your project directory.
• Prerequisites: Cursor Editor v0.48+, Custom Modes feature enabled, Claude 3.7 Sonnet recommended.
• Setup: Manually configure four custom modes in Cursor (VAN, PLAN, CREATIVE, IMPLEMENT) by pasting instruction content from the custom_modes/ directory into the "Advanced options" text box for each mode.
• Docs: Cursor Custom Modes Documentation, Memory Bank Upgrade Guide, CREATIVE Mode and Claude's "Think" Tool.

Highlighted Details

• Graph-based mode integration for workflow progression.
• JIT rule loading for optimized context usage.
• Mode-specific visual maps and decision trees.
• Integrated QA functions callable from any mode.

Maintenance & Community

This is a personal hobby project. Feedback and suggestions are welcomed. The README is subject to change.

Licensing & Compatibility

The repository does not explicitly state a license. Compatibility for commercial use or closed-source linking is not specified.

Limitations & Caveats

This is a beta version (v0.6-beta) under active development, intended for new projects and experimental use. There is no formal migration path from the legacy version. Custom mode setup is described as critical and challenging.