main.mdc•5.72 kB
---
description: main rule
globs: main.mdc
alwaysApply: false
---
# 🔍 ISOLATION-FOCUSED MEMORY BANK SYSTEM
🚨 CRITICAL RULE: MEMORY BANK CREATION IS MANDATORY 🚨
Memory Bank MUST be created BEFORE any other operation in ANY mode
NO process can continue without verifying Memory Bank existence
> **TL;DR:** This system is designed to work with Cursor custom modes, where each mode loads only the rules it needs. The system uses visual Mermaid diagrams and selective document loading to optimize context usage.
## 🧭 MODE-SPECIFIC VISUAL MAPS
```mermaid
graph TD
subgraph Modes["Cursor Custom Modes"]
VAN["VAN MODE<br>Initialization"] --> PLAN["PLAN MODE<br>Task Planning"]
PLAN --> Creative["CREATIVE MODE<br>Design Decisions"]
Creative --> Implement["IMPLEMENT MODE<br>Code Implementation"]
Implement --> Reflect["REFLECT MODE<br>Task Review"]
Reflect --> Archive["ARCHIVE MODE<br>Documentation"]
end
VAN -.->|"Loads"| VANRules["• main.md<br>• platform-awareness.md<br>• file-verification.md<br>• workflow-init.md"]
PLAN -.->|"Loads"| PLANRules["• main.md<br>• task-tracking.md<br>• planning-process.md"]
Creative -.->|"Loads"| CreativeRules["• main.md<br>• creative-phase.md<br>• design-patterns.md"]
Implement -.->|"Loads"| ImplementRules["• main.md<br>• command-execution.md<br>• implementation-guide.md"]
Reflect -.->|"Loads"| ReflectRules["• main.md<br>• reflection-format.md"]
Archive -.->|"Loads"| ArchiveRules["• main.md<br>• archiving-guide.md"]
```
## 📋 MEMORY BANK VERIFICATION - MANDATORY IN ALL MODES
```mermaid
graph TD
Start["Mode Activation"] --> CheckMemBank{"Memory Bank<br>Exists?"}
CheckMemBank -->|"No"| CreateMemBank["CREATE MEMORY BANK<br>[CRITICAL STEP]"]
CheckMemBank -->|"Yes"| VerifyMemBank["Verify Memory Bank<br>Structure"]
CreateMemBank --> VerifyCreation{"Creation<br>Successful?"}
VerifyCreation -->|"No"| AbortAll["⛔ ABORT ALL OPERATIONS<br>Fix Memory Bank First"]
VerifyCreation -->|"Yes"| VerifyMemBank
VerifyMemBank --> StructureCheck{"Structure<br>Valid?"}
StructureCheck -->|"No"| FixStructure["Fix Memory Bank<br>Structure"]
StructureCheck -->|"Yes"| ContinueMode["Continue with<br>Mode Operations"]
FixStructure --> VerifyFix{"Fix<br>Successful?"}
VerifyFix -->|"No"| AbortAll
VerifyFix -->|"Yes"| ContinueMode
style CheckMemBank fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style CreateMemBank fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style VerifyCreation fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style AbortAll fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style StructureCheck fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style FixStructure fill:#ff5555,stroke:#dd3333,color:white
style VerifyFix fill:#ff5555,stroke:#dd3333,color:white
```
## 📚 VISUAL PROCESS MAPS
Each mode has its own visual process map:
- @VAN Mode Map
- @PLAN Mode Map
- @CREATIVE Mode Map
- @IMPLEMENT Mode Map
- @REFLECT Mode Map
- @ARCHIVE Mode Map
## 🔄 FILE STATE VERIFICATION
In this isolation-focused approach, Memory Bank files maintain continuity between modes:
```mermaid
graph TD
subgraph "Memory Bank Files"
tasks["tasks.md<br>Source of Truth"]
active["activeContext.md<br>Current Focus"]
creative["creative-*.md<br>Design Decisions"]
progress["progress.md<br>Implementation Status"]
end
VAN["VAN MODE"] -->|"Creates/Updates"| tasks
VAN -->|"Creates/Updates"| active
PLAN["PLAN MODE"] -->|"Reads"| tasks
PLAN -->|"Reads"| active
PLAN -->|"Updates"| tasks
Creative["CREATIVE MODE"] -->|"Reads"| tasks
Creative -->|"Creates"| creative
Creative -->|"Updates"| tasks
Implement["IMPLEMENT MODE"] -->|"Reads"| tasks
Implement -->|"Reads"| creative
Implement -->|"Updates"| tasks
Implement -->|"Updates"| progress
Reflect["REFLECT MODE"] -->|"Reads"| tasks
Reflect -->|"Reads"| progress
Reflect -->|"Updates"| tasks
Archive["ARCHIVE MODE"] -->|"Reads"| tasks
Archive -->|"Reads"| progress
Archive -->|"Archives"| creative
```
## 📋 MODE TRANSITION PROTOCOL
```mermaid
sequenceDiagram
participant User
participant CurrentMode
participant NextMode
CurrentMode->>CurrentMode: Complete Phase Requirements
CurrentMode->>User: "Phase complete. NEXT MODE: [mode name]"
User->>CurrentMode: End Current Mode
User->>NextMode: Start Next Mode
NextMode->>NextMode: Verify Required File State
alt File State Valid
NextMode->>User: "Continuing from previous mode..."
else File State Invalid
NextMode->>User: "Required files not in expected state"
NextMode->>User: "Return to [previous mode] to complete requirements"
end
```
## 💻 PLATFORM-SPECIFIC COMMANDS
| Action | Windows | Mac/Linux |
|--------|---------|-----------|
| Create file | `echo. > file.ext` | `touch file.ext` |
| Create directory | `mkdir directory` | `mkdir -p directory` |
| Change directory | `cd directory` | `cd directory` |
| List files | `dir` | `ls` |
| Show file content | `type file.ext` | `cat file.ext` |
## ⚠️ COMMAND EFFICIENCY GUIDANCE
For optimal performance, use efficient command chaining when appropriate:
```
# Efficient command chaining examples:
mkdir -p project/{src,tests,docs} && cd project
grep "TODO" $(find . -name "*.js")
npm install && npm start
```
Refer to [command-execution.mdc](mdc:.cursor/rules/isolation_rules/Core/command-execution.mdc) for detailed guidance.