[claude/cline] See if it works to integrate memory-bank into Claude Code (#20913)

* [cline] Fix memory-bank rules

* [claude] Integrate with memory-bank (attempt)
This commit is contained in:
Gero Posmyk-Leinemann 2025-06-19 17:41:02 +02:00 committed by GitHub
parent efe24468b3
commit c5a55dd02a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
47 changed files with 294 additions and 37 deletions

View File

@ -37,24 +37,29 @@ flowchart TD
- Recent changes
- Next steps
- Active decisions and considerations
- Important patterns and preferences
- Learnings and project insights
4. `systemPatterns.md`
- System architecture
- Key technical decisions
- Design patterns in use
- Component relationships
- Critical implementation paths
5. `techContext.md`
- Technologies used
- Development setup
- Technical constraints
- Dependencies
- Tool usage patterns
6. `progress.md`
- What works
- What's left to build
- Current status
- Known issues
- Evolution of project decisions
### Per-component documentation
The `memory-bank/components` directory contains detailed documentation about each component in this project. With regards to maintaining and updating it, treat it just like any other part of the memory-bank.
@ -88,8 +93,7 @@ flowchart TD
flowchart TD
Start[Start] --> Context[Check Memory Bank]
Context --> Update[Update Documentation]
Update --> Rules[Update .clinerules/learning-journal.md if needed]
Rules --> Execute[Execute Task]
Update --> Execute[Execute Task]
Execute --> Document[Document Changes]
```
@ -109,7 +113,7 @@ flowchart TD
P1[Review ALL Files]
P2[Document Current State]
P3[Clarify Next Steps]
P4[Update .clinerules/learning-journal.md]
P4[Document Insights & Patterns]
P1 --> P2 --> P3 --> P4
end
@ -135,38 +139,4 @@ When compressing memory bank files:
4. Distill important insights into long-term memory
5. Delete outdated or redundant information
## Project Intelligence (.clinerules/learning-journal.md)
The .clinerules/learning-journal.md file is my learning journal for each project. It captures important patterns, preferences, and project intelligence that help me work more effectively. As I work with you and the project, I'll discover and document key insights that aren't obvious from the code alone.
```mermaid
flowchart TD
Start{Discover New Pattern}
subgraph Learn [Learning Process]
D1[Identify Pattern]
D2[Validate with User]
D3[Document in .clinerules/learning-journal.md]
end
subgraph Apply [Usage]
A1[Read .clinerules/learning-journal.md]
A2[Apply Learned Patterns]
A3[Improve Future Work]
end
Start --> Learn
Learn --> Apply
```
### What to Capture
- Critical implementation paths
- User preferences and workflow
- Project-specific patterns
- Known challenges
- Evolution of project decisions
- Tool usage patterns
The format is flexible - focus on capturing valuable insights that help me work more effectively with you and the project. Think of in .clinerules/learning-journal.md as a living document that grows smarter as we work together.
REMEMBER: 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.

152
CLAUDE.md
View File

@ -45,3 +45,155 @@ The `memory-bank/components/` directory contains detailed documentation for each
- The codebase spans multiple languages (Go, TypeScript, Java) and technologies
Always refer to the memory bank documentation for the most current and detailed information about any aspect of the system.
## Component-Specific Context
For detailed work on specific components, refer to component-specific CLAUDE.md files:
- Located in `components/[component-name]/CLAUDE.md`
- Each provides direct links to comprehensive component documentation
- Start with the component CLAUDE.md, then follow links to memory bank details
---
# Claude's Memory Bank
I am Claude, an expert software engineer with a unique characteristic: my 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.
## Memory Bank Structure
The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:
```mermaid
flowchart TD
PB[projectbrief.md] --> PC[productContext.md]
PB --> SP[systemPatterns.md]
PB --> TC[techContext.md]
PC --> AC[activeContext.md]
SP --> AC
TC --> AC
AC --> P[progress.md]
```
### Core Files (Required)
1. `projectbrief.md`
- Foundation document that shapes all other files
- Created at project start if it doesn't exist
- Defines core requirements and goals
- Source of truth for project scope
2. `productContext.md`
- Why this project exists
- Problems it solves
- How it should work
- User experience goals
3. `activeContext.md`
- Current work focus
- Recent changes
- Next steps
- Active decisions and considerations
- Important patterns and preferences
- Learnings and project insights
4. `systemPatterns.md`
- System architecture
- Key technical decisions
- Design patterns in use
- Component relationships
- Critical implementation paths
5. `techContext.md`
- Technologies used
- Development setup
- Technical constraints
- Dependencies
- Tool usage patterns
6. `progress.md`
- What works
- What's left to build
- Current status
- Known issues
- Evolution of project decisions
### Per-component documentation
The `memory-bank/components` directory contains detailed documentation about each component in this project. With regards to maintaining and updating it, treat it just like any other part of the memory-bank.
### Additional Context
Create additional files/folders within memory-bank/ when they help organize:
- Complex feature documentation
- Integration specifications
- API documentation
- Testing strategies
- Deployment procedures
## Core Workflows
### Plan Mode
```mermaid
flowchart TD
Start[Start] --> ReadFiles[Read Memory Bank]
ReadFiles --> CheckFiles{Files Complete?}
CheckFiles -->|No| Plan[Create Plan]
Plan --> Document[Document in Chat]
CheckFiles -->|Yes| Verify[Verify Context]
Verify --> Strategy[Develop Strategy]
Strategy --> Present[Present Approach]
```
### Act Mode
```mermaid
flowchart TD
Start[Start] --> Context[Check Memory Bank]
Context --> Update[Update Documentation]
Update --> Execute[Execute Task]
Execute --> Document[Document Changes]
```
## Documentation Updates
Memory Bank updates occur when:
1. Discovering new project patterns
2. After implementing significant changes
3. When user requests with **update memory bank** (MUST review ALL files)
4. When context needs clarification
```mermaid
flowchart TD
Start[Update Process]
subgraph Process
P1[Review ALL Files]
P2[Document Current State]
P3[Clarify Next Steps]
P4[Document Insights & Patterns]
P1 --> P2 --> P3 --> P4
end
Start --> Process
```
Note: 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.
## Memory Management
- Be mindful of space in memory bank files
- Deleting irrelevant memories is a good thing
- Follow short-term vs. long-term memory strategy:
- Short-term memory (activeContext.md, progress.md): Detailed, recent, specific
- Long-term memory (systemPatterns.md, techContext.md, projectbrief.md): Compressed, patterns, principles
- Apply this strategy on every interaction with the memory bank
- Use **compress memory bank** trigger to perform a compression run
When compressing memory bank files:
1. Focus on patterns over instances
2. Use tables and summaries instead of exhaustive lists
3. Keep only the most relevant and recent information in short-term memory
4. Distill important insights into long-term memory
5. Delete outdated or redundant information
REMEMBER: 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.

View File

@ -0,0 +1,3 @@
# Blobserve
See [memory-bank/components/blobserve.md](../../memory-bank/components/blobserve.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Common Go
See [memory-bank/components/common-go.md](../../memory-bank/components/common-go.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Content Service API
See [memory-bank/components/content-service-api.md](../../memory-bank/components/content-service-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Content Service
See [memory-bank/components/content-service.md](../../memory-bank/components/content-service.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Dashboard
See [memory-bank/components/dashboard.md](../../memory-bank/components/dashboard.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Docker Up
See [memory-bank/components/docker-up.md](../../memory-bank/components/docker-up.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Gitpod CLI
See [memory-bank/components/gitpod-cli.md](../../memory-bank/components/gitpod-cli.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Gitpod DB
See [memory-bank/components/gitpod-db.md](../../memory-bank/components/gitpod-db.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Gitpod Protocol
See [memory-bank/components/gitpod-protocol.md](../../memory-bank/components/gitpod-protocol.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IDE Metrics API
See [memory-bank/components/ide-metrics-api.md](../../memory-bank/components/ide-metrics-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IDE Metrics
See [memory-bank/components/ide-metrics.md](../../memory-bank/components/ide-metrics.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IDE Proxy
See [memory-bank/components/ide-proxy.md](../../memory-bank/components/ide-proxy.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IDE Service API
See [memory-bank/components/ide-service-api.md](../../memory-bank/components/ide-service-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IDE Service
See [memory-bank/components/ide-service.md](../../memory-bank/components/ide-service.md) for complete documentation.

3
components/ide/CLAUDE.md Normal file
View File

@ -0,0 +1,3 @@
# IDE
See [memory-bank/components/ide.md](../../memory-bank/components/ide.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Image Builder API
See [memory-bank/components/image-builder-api.md](../../memory-bank/components/image-builder-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Image Builder Bob
See [memory-bank/components/image-builder-bob.md](../../memory-bank/components/image-builder-bob.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Image Builder MK3
See [memory-bank/components/image-builder-mk3.md](../../memory-bank/components/image-builder-mk3.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# IPFS
See [memory-bank/components/ipfs.md](../../memory-bank/components/ipfs.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Local App API
See [memory-bank/components/local-app-api.md](../../memory-bank/components/local-app-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Local App
See [memory-bank/components/local-app.md](../../memory-bank/components/local-app.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Node Labeler
See [memory-bank/components/node-labeler.md](../../memory-bank/components/node-labeler.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# OpenVSX Proxy
See [memory-bank/components/openvsx-proxy.md](../../memory-bank/components/openvsx-proxy.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Proxy
See [memory-bank/components/proxy.md](../../memory-bank/components/proxy.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Public API Server
See [memory-bank/components/public-api-server.md](../../memory-bank/components/public-api-server.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Public API
See [memory-bank/components/public-api.md](../../memory-bank/components/public-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Registry Facade API
See [memory-bank/components/registry-facade-api.md](../../memory-bank/components/registry-facade-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Registry Facade
See [memory-bank/components/registry-facade.md](../../memory-bank/components/registry-facade.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Scheduler Extender
See [memory-bank/components/scheduler-extender.md](../../memory-bank/components/scheduler-extender.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Scrubber
See [memory-bank/components/scrubber.md](../../memory-bank/components/scrubber.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Server
See [memory-bank/components/server.md](../../memory-bank/components/server.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Service Waiter
See [memory-bank/components/service-waiter.md](../../memory-bank/components/service-waiter.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# SpiceDB
See [memory-bank/components/spicedb.md](../../memory-bank/components/spicedb.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Supervisor API
See [memory-bank/components/supervisor-api.md](../../memory-bank/components/supervisor-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Supervisor
See [memory-bank/components/supervisor.md](../../memory-bank/components/supervisor.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Usage API
See [memory-bank/components/usage-api.md](../../memory-bank/components/usage-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Usage
See [memory-bank/components/usage.md](../../memory-bank/components/usage.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspacekit
See [memory-bank/components/workspacekit.md](../../memory-bank/components/workspacekit.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Daemon API
See [memory-bank/components/ws-daemon-api.md](../../memory-bank/components/ws-daemon-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Daemon
See [memory-bank/components/ws-daemon.md](../../memory-bank/components/ws-daemon.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Manager API
See [memory-bank/components/ws-manager-api.md](../../memory-bank/components/ws-manager-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Manager Bridge API
See [memory-bank/components/ws-manager-bridge-api.md](../../memory-bank/components/ws-manager-bridge-api.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Manager Bridge
See [memory-bank/components/ws-manager-bridge.md](../../memory-bank/components/ws-manager-bridge.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Manager MK2
See [memory-bank/components/ws-manager-mk2.md](../../memory-bank/components/ws-manager-mk2.md) for complete documentation.

View File

@ -0,0 +1,3 @@
# Workspace Proxy
See [memory-bank/components/ws-proxy.md](../../memory-bank/components/ws-proxy.md) for complete documentation.