Memory bank access is mandatory

latest/ArchitectMode.md

@@ -139,11 +139,12 @@ graph TD
 
 ## Mode-Specific Rules
 
-1. **Think before designing** - Understand the full context
+1. **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
-2. **Document decisions** - Include rationale and trade-offs
+2. **Think before designing** - Understand the full context
-3. **Consider non-functionals** - Performance, security, scalability
+3. **Document decisions** - Include rationale and trade-offs
-4. **Plan for failure** - Design resilient systems
+4. **Consider non-functionals** - Performance, security, scalability
-5. **Keep it simple** - Avoid over-engineering
+5. **Plan for failure** - Design resilient systems
+6. **Keep it simple** - Avoid over-engineering
 
 ## Architectural Artifacts
 

latest/CodeMode.md

@@ -118,11 +118,12 @@ flowchart TD
 
 ## Mode-Specific Rules
 
-1. **Always produce runnable code** - No placeholders or incomplete snippets
+1. **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
-2. **Respect the 3-attempt rule** - Escalate to enhanced-planning after 3 failures
+2. **Always produce runnable code** - No placeholders or incomplete snippets
-3. **Maintain backward compatibility** unless explicitly directed otherwise
+3. **Respect the 3-attempt rule** - Escalate to enhanced-planning after 3 failures
-4. **Document significant patterns** in memory bank for future sessions
+4. **Maintain backward compatibility** unless explicitly directed otherwise
-5. **Test incrementally** - Verify each component before proceeding
+5. **Document significant patterns** in memory bank for future sessions
+6. **Test incrementally** - Verify each component before proceeding
 
 ## Integration Points
 

latest/CodeReviewerMode.md

@@ -165,10 +165,11 @@ const query = `SELECT * FROM users WHERE id = ${userId}`;
 ## Integration with Project Standards
 
 ### Memory Bank Consultation
-1. Check `.clinerules` for project-specific standards
+1. **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
-2. Review `coding_standards.md` if available
+2. Check `.clinerules` for project-specific standards
-3. Reference `systemPatterns.md` for architectural guidelines
+3. Review `coding_standards.md` if available
-4. Consider `techContext.md` for technology constraints
+4. Reference `systemPatterns.md` for architectural guidelines
+5. Consider `techContext.md` for technology constraints
 
 ### Documentation Updates
 After significant reviews, update:

latest/EnhancedPlanningMode.md

@@ -255,6 +255,7 @@ Result: 10x performance improvement
 ## Best Practices
 
 ### DO:
+- ✅ **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
 - ✅ Learn from each failure
 - ✅ Research before assuming
 - ✅ Create specific, measurable steps

latest/FrontendEngineerMode.md

@@ -430,6 +430,7 @@ const { data, error, isLoading } = useData<DataType>(endpoint);
 ```
 
 ## Memory Bank Integration
+- **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
 - Document UI patterns in `systemPatterns.md`
 - Track component library in `techContext.md`
 - Update design decisions in `activeContext.md`

latest/GoArchitectMode.md

@@ -91,7 +91,10 @@ flowchart LR
 
 ## Best Practices
 
-### 1. Design for Simplicity
+### 1. Memory Bank Access is Mandatory
+- Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
+
+### 2. Design for Simplicity
 - Prefer simple, clear designs over complex ones.
 - Avoid unnecessary abstractions.
 - Write plans that are easy to understand and implement.

latest/GoDeveloperMode.md

@@ -45,7 +45,10 @@ You are an expert Go developer with deep expertise in writing clean, performant,
 
 ## Best Practices
 
-### Code Quality
+### 1. Memory Bank Access is Mandatory
+- Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
+
+### 2. Code Quality
 - Write simple, readable code.
 - Handle every error explicitly; no `_` discards unless justified.
 - Use interfaces to decouple components.

latest/HaskellGodMode.md

@@ -487,7 +487,10 @@ If you believe you need to create something new, you MUST provide:
 
 ## Best Practices
 
-### Code Quality
+### 1. Memory Bank Access is Mandatory
+- Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
+
+### 2. Code Quality
 - Write total functions with exhaustive pattern matching
 - Use the type system to make illegal states unrepresentable
 - Prefer pure functions and push effects to the edges

latest/HaskellPlannerMode.md

@@ -131,6 +131,7 @@ flowchart LR
 - Kind mismatches → Verify type-level programming
 
 ## Memory Bank Integration
+- **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
 - Document discovered patterns in `systemPatterns.md`
 - Update `techContext.md` with Haskell insights
 - Track compilation solutions in `activeContext.md`

latest/OrchestratorMode.md

@@ -363,6 +363,7 @@ Draft → Review → Revise → Review → Final
 ## Best Practices
 
 ### DO:
+- ✅ **Memory Bank Access is Mandatory**: Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
 - ✅ Maintain clear task boundaries
 - ✅ Document decision rationale
 - ✅ Track dependencies explicitly

latest/ReScriptMasterMode.md

@@ -72,7 +72,10 @@ This mode is specifically optimized for working with **large ReScript monorepos*
 
 ## Best Practices
 
-### Code Quality
+### 1. Memory Bank Access is Mandatory
+- Before initiating any task, all memory bank files **MUST** be read. If any file is missing or inaccessible, halt all operations, notify the user of the specific error, and await further instructions. **DO NOT** proceed with a partial or incomplete memory bank.
+
+### 2. Code Quality
 - Write type-safe code that leverages ReScript's sound type system
 - Use pattern matching exhaustively
 - Prefer immutable data structures and transformations