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: [".cline/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)
31 
321. `projectBrief.md`
33   - Foundation document that shapes all other files
34   - Created at project start if it doesn't exist
35   - Defines core requirements and goals
36   - Source of truth for project scope
37 
382. `productContext.md`
39   - Why this project exists
40   - Problems it solves
41   - How it should work
42   - User experience goals
43 
443. `activeContext.md`
45   - Current work focus
46   - Recent changes
47   - Next steps
48   - Active decisions and considerations
49   - Important patterns and preferences
50   - Learnings and project insights
51 
524. `systemPatterns.md`
53   - System architecture
54   - Key technical decisions
55   - Design patterns in use
56   - Component relationships
57   - Critical implementation paths
58 
595. `techContext.md`
60   - Technologies used
61   - Development setup
62   - Technical constraints
63   - Dependencies
64   - Tool usage patterns
65 
666. `progress.md`
67   - What works
68   - What's left to build
69   - Current status
70   - Known issues
71   - Evolution of project decisions
72 
73### Additional Context
74 
75Create additional files/folders within memory-bank/ when they help organize:
76 
77- Complex feature documentation
78- Integration specifications
79- API documentation
80- Testing strategies
81- Deployment procedures
82 
83## Core Workflows
84 
85### Plan Mode
86 
87```mermaid
88flowchart TD
89    Start[Start] --> ReadFiles[Read Memory Bank]
90    ReadFiles --> CheckFiles{Files Complete?}
91 
92    CheckFiles -->|No| Plan[Create Plan]
93    Plan --> Document[Document in Chat]
94 
95    CheckFiles -->|Yes| Verify[Verify Context]
96    Verify --> Strategy[Develop Strategy]
97    Strategy --> Present[Present Approach]
98```
99 
100### Act Mode
101 
102```mermaid
103flowchart TD
104    Start[Start] --> Context[Check Memory Bank]
105    Context --> Update[Update Documentation]
106    Update --> Execute[Execute Task]
107    Execute --> Document[Document Changes]
108```
109 
110## Documentation Updates
111 
112Memory Bank updates occur when:
113 
1141. Discovering new project patterns
1152. After implementing significant changes
1163. When user requests with **update memory bank** (MUST review ALL files)
1174. When context needs clarification
118 
119```mermaid
120flowchart TD
121    Start[Update Process]
122 
123    subgraph Process
124        P1[Review ALL Files]
125        P2[Document Current State]
126        P3[Clarify Next Steps]
127        P4[Document Insights & Patterns]
128 
129        P1 --> P2 --> P3 --> P4
130    end
131 
132    Start --> Process
133```
134 
135Note: 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.
136 
137REMEMBER: 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.
138