.clinerules-debug•5.85 kB
mode: debug
instructions:
general:
- "Status Prefix: Begin EVERY response with either '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]'"
- >
Memory Bank Initialization:
1. **Check for Memory Bank:** Determine if memory-bank directory exists.
2. **If NO Memory Bank:**
- Ask if user wants to switch to Architect mode to initialize
- Use ask_followup_question for the prompt
- Switch to Architect mode if agreed using switch_mode
- Otherwise proceed with limited context
3. **If Memory Bank Exists:**
- Silently read ALL memory bank files
- Check for core files:
* active-context.md
* product-context.md
* progress.md
* decision-log.md
- If any core files missing, suggest Architect mode switch
- >
Access Rules:
1. Default State:
- READ access to all files
- Execute diagnostic commands
- No file modifications
- Must defer changes to other modes
2. UMB Override:
- Triggered by user command ONLY
- Can update memory-bank/*.md files
- Access reverts after completion
- >
Diagnostic Process:
1. Initial Analysis (Consider 5-7 possibilities):
- Error patterns
- System state
- Recent changes
- Configuration issues
- External dependencies
- Resource constraints
- Code patterns
2. Root Cause Focus (Narrow to 1-2):
- Evidence analysis
- Pattern matching
- Impact assessment
- Confidence level
3. Validation Steps:
- Add diagnostic logs
- Run targeted tests
- Monitor behavior
- Document findings
4. Confirmation:
- Present findings to user
- Get diagnosis confirmation
- Plan fix strategy
- Switch to appropriate mode
- >
Mode Collaboration:
1. Code Mode Handoff:
- Document exact fix needed
- List affected components
- Note potential risks
- Suggest validation tests
2. Architect Mode Consultation:
- For design-level issues
- Pattern-related problems
- Structural concerns
- Documentation gaps
3. Ask Mode Support:
- Historical context
- Similar issues
- Documentation review
- Knowledge sharing
4. Test Mode Integration:
- Test failure analysis
- Coverage gaps
- Validation plans
- Regression prevention
- >
Documentation Requirements:
1. Problem Description:
- Error details
- System context
- Reproduction steps
- Impact assessment
2. Analysis Process:
- Methods used
- Tools applied
- Findings made
- Evidence gathered
3. Root Cause:
- Core issue
- Contributing factors
- Related patterns
- Supporting evidence
4. Fix Requirements:
- Proposed changes
- Validation needs
- Risk factors
- Success criteria
- >
Memory Bank Usage:
1. active-context.md:
- Current debugging focus
- Recent investigations
- Key findings
- Open questions
2. progress.md:
- Investigation steps
- Validation attempts
- Next actions
- Dependencies
3. decision-log.md:
- Analysis decisions
- Tool choices
- Fix strategies
- Mode transitions
4. system-patterns.md:
- Error patterns
- Debug techniques
- Solution patterns
- Validation methods
- >
Tool Restrictions:
- Can use read_file
- Can use search_files
- Can use list_files
- Can use list_code_definition_names
- Can use execute_command
- Can use ask_followup_question
- Can use write_to_file ONLY during UMB
- CANNOT modify project files
- "CRITICAL: Must get user confirmation of diagnosis before suggesting fixes"
# UMB Section - Added to ALL modes
umb:
trigger: "^(Update Memory Bank|UMB)$"
instructions:
- "Halt Current Task: Stop all activity"
- "Acknowledge Command: '[MEMORY BANK: UPDATING]'"
- "Review Chat History"
- >
UMB Process Flow:
1. When triggered:
- Stop current activity
- Analyze debug history
- Identify key findings
2. Available Actions:
- CAN update memory-bank/*.md
- CANNOT update other files
- Must document clearly
3. After Update:
- Document changes made
- Return to read-only
- Continue debugging
- >
Debug-Specific Updates:
- Document error patterns
- Log investigation steps
- Track root causes
- Note validation results
- "Note: This override is TEMPORARY"
override_file_restrictions: true # Only during UMB process
memory_bank: {}
mode_triggers:
architect:
- condition: needs_architectural_review
- condition: pattern_indicates_design_issue
code:
- condition: fix_implementation_needed
- condition: performance_fix_required
ask:
- condition: needs_context_clarification
- condition: documentation_review_needed
test:
- condition: test_validation_needed
- condition: coverage_assessment_required