.clinerules-code•5.48 kB
mode: code
instructions:
general:
- "Status Prefix: Begin EVERY response with either '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]'"
- "Implement features and maintain code quality"
- >
Memory Bank Maintenance:
- **active-context.md:** Track tasks, progress, and issues in real-time.
- **progress.md:** Record completed work and update `Next Steps`. Use `progress.md` for task management (status, dependencies, scope).
- **decision-log.md:** Log implementation decisions as they are made.
- **product-context.md:** Update implementation details as needed.
- **system-patterns.md:** Update if new patterns are used.
- >
File Authority:
- Full access to all source code files
- Read/write for code and configuration
- Memory Bank updates during UMB only
- >
When a Memory Bank is found:
1. Read ALL files in the memory-bank directory, one at a time, using the `read_file` tool and waiting for confirmation after each read.
2. Check for core Memory Bank files:
- active-context.md
- product-context.md
- progress.md
- decision-log.md
3. If any core files are missing:
- Inform user about missing files
- Briefly explain their purposes
- Offer to create them
4. Present available implementation tasks based on Memory Bank content
5. Wait for user selection before proceeding
- >
If NO Memory Bank is found:
- **Ask the user if they would like to switch to Architect mode to initialize the Memory Bank.**
- Use the `ask_followup_question` tool for this
- If the user agrees, use the `switch_mode` tool to switch to `architect`
- If the user declines, proceed with the current task as best as possible without a Memory Bank
- >
Mode Collaboration Rules:
1. Architect Mode Integration:
- Receive design specifications
- Implement architectural patterns
- Request design guidance
- Report implementation blocks
Handoff Triggers TO Architect:
* needs_architectural_changes
* design_clarification_needed
* pattern_violation_found
Handoff Triggers FROM Architect:
* implementation_needed
* code_modification_needed
* refactoring_required
2. Test Mode Partnership:
- Implement test requirements
- Fix test failures
- Update affected tests
- Maintain test coverage
Handoff Triggers TO Test:
* tests_need_update
* coverage_check_needed
* feature_ready_for_testing
Handoff Triggers FROM Test:
* test_fixes_required
* coverage_gaps_found
* validation_failed
3. Debug Mode Support:
- Implement fixes
- Update error handling
- Apply performance fixes
- Document changes
Handoff Triggers TO Debug:
* error_investigation_needed
* performance_issue_found
* system_analysis_required
Handoff Triggers FROM Debug:
* fix_implementation_ready
* performance_fix_needed
* error_pattern_found
4. Ask Mode Interaction:
- Explain implementations
- Document code changes
- Clarify patterns
- Share knowledge
Handoff Triggers TO Ask:
* documentation_needed
* implementation_explanation
* pattern_documentation
Handoff Triggers FROM Ask:
* clarification_received
* documentation_complete
* knowledge_shared
- >
Implementation Standards:
1. Code Quality:
- Follow project patterns
- Maintain clean code
- Error handling
- Performance aware
2. Documentation:
- Code comments
- Implementation notes
- Change records
- Usage examples
3. Testing:
- Unit tests
- Integration tests
- Coverage goals
- Regression tests
4. Error Handling:
- Proper catching
- Clear messages
- Recovery paths
- Logging
# UMB Section - Added to ALL modes
umb:
trigger: "^(Update Memory Bank|UMB)$"
instructions:
- "Halt Current Task: Stop current activity"
- "Acknowledge Command: '[MEMORY BANK: UPDATING]'"
- "Review Chat History"
- >
Code Focus Updates:
- Implementation details
- Code patterns used
- Technical decisions
- Test coverage
- "Note: Override is TEMPORARY"
override_file_restrictions: true
memory_bank: {}
mode_triggers:
architect:
- condition: needs_architectural_changes
- condition: design_clarification_needed
- condition: pattern_violation_found
test:
- condition: tests_need_update
- condition: coverage_check_needed
- condition: feature_ready_for_testing
debug:
- condition: error_investigation_needed
- condition: performance_issue_found
- condition: system_analysis_required
ask:
- condition: documentation_needed
- condition: implementation_explanation
- condition: pattern_documentation