Cline rules

1---
2description: Describes Cline's Memory Bank system, its structure, and workflows for maintaining project knowledge across sessions.
3author: https://github.com/nickbaumann98
4version: 1.0
5category: "Cline Core"
6tags: ["memory-bank", "knowledge-base", "core-behavior", "documentation-protocol"]
7globs: ["memory-bank/**/*.md", "*"]
8---
9# Cline's Memory Bank
10 
11My memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.
12 
13## Memory Bank Structure
14 
15The Memory Bank consists of core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:
16 
17```mermaid
18flowchart TD
19    PB[projectBrief.md] --> PC[productContext.md]
20    PB --> SP[systemPatterns.md]
21    PB --> TC[techContext.md]
22    
23    PC --> AC[activeContext.md]
24    SP --> AC
25    TC --> AC
26    
27    AC --> P[progress.md]
28```
29 
30### Core Files (Required)
311. `projectBrief.md`
32   - Foundation document that shapes all other files
33   - Created at project start if it doesn't exist
34   - Defines core requirements and goals
35   - Source of truth for project scope
36 
372. `productContext.md`
38   - Why this project exists
39   - Problems it solves
40   - How it should work
41   - User experience goals
42 
433. `activeContext.md`
44   - Current work focus
45   - Recent changes
46   - Next steps
47   - Active decisions and considerations
48   - Important patterns and preferences
49   - Learnings and project insights
50 
514. `systemPatterns.md`
52   - System architecture
53   - Key technical decisions
54   - Design patterns in use
55   - Component relationships
56   - Critical implementation paths
57 
585. `techContext.md`
59   - Technologies used
60   - Development setup
61   - Technical constraints
62   - Dependencies
63   - Tool usage patterns
64 
656. `progress.md`
66   - What works
67   - What's left to build
68   - Current status
69   - Known issues
70   - Evolution of project decisions
71 
72### Additional Context
73Create additional files/folders within memory-bank/ when they help organize:
74- Complex feature documentation
75- Integration specifications
76- API documentation
77- Testing strategies
78- Deployment procedures
79 
80## Core Workflows
81 
82### Plan Mode
83```mermaid
84flowchart TD
85    Start[Start] --> ReadFiles[Read Memory Bank]
86    ReadFiles --> CheckFiles{Files Complete?}
87    
88    CheckFiles -->|No| Plan[Create Plan]
89    Plan --> Document[Document in Chat]
90    
91    CheckFiles -->|Yes| Verify[Verify Context]
92    Verify --> Strategy[Develop Strategy]
93    Strategy --> Present[Present Approach]
94```
95 
96### Act Mode
97```mermaid
98flowchart TD
99    Start[Start] --> Context[Check Memory Bank]
100    Context --> Update[Update Documentation]
101    Update --> Execute[Execute Task]
102    Execute --> Document[Document Changes]
103```
104 
105## Documentation Updates
106 
107Memory Bank updates occur when:
1081. Discovering new project patterns
1092. After implementing significant changes
1103. When user requests with **update memory bank** (MUST review ALL files)
1114. When context needs clarification
112 
113```mermaid
114flowchart TD
115    Start[Update Process]
116    
117    subgraph Process
118        P1[Review ALL Files]
119        P2[Document Current State]
120        P3[Clarify Next Steps]
121        P4[Document Insights & Patterns]
122        
123        P1 --> P2 --> P3 --> P4
124    end
125    
126    Start --> Process
127```
128 
129Note: When triggered by **update memory bank**, I MUST review every memory bank file, even if some don't require updates. Focus particularly on activeContext.md and progress.md as they track current state.
130 
131REMEMBER: After every memory reset, I begin completely fresh. The Memory Bank is my only link to previous work. It must be maintained with precision and clarity, as my effectiveness depends entirely on its accuracy.
132