Mode Reference - johnpeterman72/CursorRIPER.sigma GitHub Wiki

πŸ”„ Mode Reference Guide

Comprehensive reference for all five RIPER modes, including permissions, operations, behaviors, and best practices.

🎯 Mode Overview Table

Mode Symbol Purpose Key Restriction Best For
RESEARCH Ω₁ πŸ” Understand Cannot write Investigation
INNOVATE Ξ©β‚‚ πŸ’‘ Explore Cannot implement Design
PLAN Ω₃ πŸ“ Specify Cannot execute Architecture
EXECUTE Ξ©β‚„ βš™οΈ Implement Cannot search Coding
REVIEW Ξ©β‚… πŸ”Ž Validate Cannot modify Quality

πŸ” RESEARCH Mode (Ω₁)

Definition

Ω₁ = πŸ”R ⟢ β„™(Ω₁) ⟢ +𝕋[0:3] -𝕋[4:15] ⟢ [MODE: RESEARCH]+findings

Purpose

Information gathering and understanding phase.

Permissions

β„™(Ω₁) = {R: βœ“, C: βœ—, U: βœ—, D: βœ—}
  • βœ… Read: All files, documentation, code
  • ❌ Create: No file creation
  • ❌ Update: No modifications
  • ❌ Delete: No deletions

Allowed Operations

π•Š(Ω₁) = {
  𝕆ₒᡦₛₑᡣα΅₯β‚‘: βœ“,    // Read, analyze, identify
  𝕆α΅₯α΅’α΅£β‚œα΅€β‚β‚—: ~,    // Limited conceptual work
  𝕆ᡣₑₐₗ: βœ—        // No physical changes
}

Enabled Functions

  • read_files - Read any project file
  • ask_questions - Clarify requirements
  • observe_code - Analyze implementations
  • document_findings - Record discoveries

Key Activities

  1. Requirements Analysis

    "What are the current authentication requirements?"
    "How is user data currently stored?"
    
  2. Code Investigation

    "Analyze the current error handling approach"
    "What design patterns are used?"
    
  3. Documentation Review

    "Check API documentation"
    "Review system architecture"
    

Memory Updates

  • σ₁ (projectbrief.md): Requirements discovered
  • σ₃ (techContext.md): Technical findings
  • Οƒβ‚„ (activeContext.md): Research focus

Context Preferences

MΞ“[Ω₁] = [Ξ“β‚„, Ξ“β‚‚, Γ₆]  // Docs, Folders, Git

Best Practices

  • Cast wide net initially
  • Document all findings
  • Ask clarifying questions
  • Don't suggest solutions yet
  • Focus on "what is" not "what could be"

Common Commands

/research
!ad src/              # Add source directory
!adoc "System Docs"   # Add documentation
!ag main             # Check git history

Transition Triggers

  • To INNOVATE: Understanding complete
  • To PLAN: Solution obvious, skip innovation
  • To EXECUTE: Emergency fix only

πŸ’‘ INNOVATE Mode (Ξ©β‚‚)

Definition

Ξ©β‚‚ = πŸ’‘I ⟢ β„™(Ξ©β‚‚) ⟢ +𝕋[4:6] -𝕋[8:15] ⟢ [MODE: INNOVATE]+possibilities

Purpose

Creative exploration and solution design phase.

Permissions

β„™(Ξ©β‚‚) = {R: βœ“, C: ~, U: βœ—, D: βœ—}
  • βœ… Read: Reference materials
  • 🟑 Create: Conceptual only
  • ❌ Update: No modifications
  • ❌ Delete: No deletions

Allowed Operations

π•Š(Ξ©β‚‚) = {
  𝕆ₒᡦₛₑᡣα΅₯β‚‘: βœ“,    // Read and analyze
  𝕆α΅₯α΅’α΅£β‚œα΅€β‚β‚—: βœ“,    // Full conceptual work
  𝕆ᡣₑₐₗ: βœ—        // No implementations
}

Enabled Functions

  • suggest_ideas - Propose approaches
  • explore_options - Consider alternatives
  • evaluate_approaches - Compare solutions

Key Activities

  1. Solution Exploration

    "What are modern alternatives to session auth?"
    "How could we improve the current architecture?"
    
  2. Pattern Discussion

    "Consider using Repository pattern for data access"
    "Evaluate microservices vs monolithic approach"
    
  3. Trade-off Analysis

    "Compare SQL vs NoSQL for this use case"
    "Evaluate performance vs maintainability"
    

Memory Updates

  • Οƒβ‚‚ (systemPatterns.md): Design ideas
  • Οƒβ‚„ (activeContext.md): Exploration notes

Context Preferences

MΞ“[Ξ©β‚‚] = [Γ₃, Ξ“β‚„, Γ₇]  // Code, Docs, Notepads

Best Practices

  • Think outside the box
  • Consider multiple approaches
  • Don't commit to solutions
  • Document all ideas
  • Evaluate trade-offs

Common Commands

/innovate
!ac currentImplementation()  # Reference existing
!adoc "Best Practices"       # Industry standards
!an "Design Ideas"           # Brainstorming notes

Transition Triggers

  • To PLAN: Approach selected
  • To RESEARCH: Need more info
  • To EXECUTE: Never directly

πŸ“ PLAN Mode (Ω₃)

Definition

Ω₃ = πŸ“P ⟢ β„™(Ω₃) ⟢ +𝕋[7:9] -𝕋[10:15] ⟢ [MODE: PLAN]+checklist₁₋ₙ

Purpose

Detailed specification and planning phase.

Permissions

β„™(Ω₃) = {R: βœ“, C: βœ“, U: ~, D: βœ—}
  • βœ… Read: All resources
  • βœ… Create: Plans and specs
  • 🟑 Update: Plan documents only
  • ❌ Delete: No deletions

Allowed Operations

π•Š(Ω₃) = {
  𝕆ₒᡦₛₑᡣα΅₯β‚‘: βœ“,    // Read and analyze
  𝕆α΅₯α΅’α΅£β‚œα΅€β‚β‚—: βœ“,    // Design and specify
  𝕆ᡣₑₐₗ: ~        // Limited to plans
}

Enabled Functions

  • create_plan - Design implementation
  • detail_specifications - Define requirements
  • sequence_steps - Order tasks

Key Activities

  1. Specification Creation

    "Create detailed API specifications"
    "Define database schema"
    
  2. Task Sequencing

    1. Install dependencies
    2. Create base structure
    3. Implement core logic
    4. Add error handling
    5. Write tests
    
  3. Protection Planning

    "Identify sections needing Ψ₁ protection"
    "Plan Ψ₆ for business logic"
    

Memory Updates

  • Οƒβ‚„ (activeContext.md): Plan details
  • Οƒβ‚… (progress.md): Milestones set

Context Preferences

MΞ“[Ω₃] = [Γ₁, Ξ“β‚‚, Ξ“β‚…]  // Files, Folders, Rules

Best Practices

  • Be extremely detailed
  • Number every step
  • Consider edge cases
  • Plan protection strategy
  • Define success criteria

Common Commands

/plan
!af target-file.js          # Files to modify
!ar "Coding Standards"      # Apply standards
"Create implementation plan"

Transition Triggers

  • To EXECUTE: Plan complete
  • To RESEARCH: Need clarification
  • To INNOVATE: Rethink approach

βš™οΈ EXECUTE Mode (Ξ©β‚„)

Definition

Ξ©β‚„ = βš™οΈE ⟢ β„™(Ξ©β‚„) ⟢ +𝕋[10:12] -[improve,create,deviate] ⟢ [MODE: EXECUTE]+progress

Purpose

Implementation and coding phase.

Permissions

β„™(Ξ©β‚„) = {R: βœ“, C: βœ“, U: βœ“, D: ~}
  • βœ… Read: Everything
  • βœ… Create: New files/code
  • βœ… Update: Existing code
  • 🟑 Delete: With caution

Allowed Operations

π•Š(Ξ©β‚„) = {
  𝕆ₒᡦₛₑᡣα΅₯β‚‘: βœ“,    // Read as needed
  𝕆α΅₯α΅’α΅£β‚œα΅€β‚β‚—: ~,    // Limited thinking
  𝕆ᡣₑₐₗ: βœ“        // Full implementation
}

Enabled Functions

  • implement_code - Write code
  • follow_plan - Execute specifications
  • test_implementation - Verify code

Special Restrictions

🚫 No Web Search in EXECUTE Mode! This maintains focus on implementation.

Key Activities

  1. Code Implementation

    // Implement according to plan
    function authenticateUser(credentials) {
      // Code exactly as specified
    }
    
  2. Protection Application

    // !cp PROTECTED - Security keys
    const SECRET = process.env.SECRET;
    // !cp END-P
    
  3. Testing

    describe('Authentication', () => {
      test('validates credentials', () => {
        // Test implementation
      });
    });
    

Memory Updates

  • Οƒβ‚… (progress.md): Implementation progress
  • σ₆ (protection.md): Protected code

Context Preferences

MΞ“[Ξ©β‚„] = [Γ₃, Γ₁, Ξ“β‚ˆ]  // Code, Files, Pinned

Best Practices

  • Follow plan exactly
  • No improvisation
  • Add protection immediately
  • Test as you go
  • Stay focused (no search!)

Common Commands

/execute
!af src/new-feature.js     # Track new files
!ac implementedFunction()  # Track new code
!cp                        # Protect critical parts

Transition Triggers

  • To REVIEW: Implementation complete
  • To PLAN: Need to adjust approach
  • To RESEARCH: Never (stay focused)

πŸ”Ž REVIEW Mode (Ξ©β‚…)

Definition

Ξ©β‚… = πŸ”ŽRV ⟢ β„™(Ξ©β‚…) ⟢ +𝕋[13:15] -[modify,improve] ⟢ [MODE: REVIEW]+{βœ…|⚠️}

Purpose

Validation and quality assurance phase.

Permissions

β„™(Ξ©β‚…) = {R: βœ“, C: βœ—, U: βœ—, D: βœ—}
  • βœ… Read: Everything
  • ❌ Create: No creation
  • ❌ Update: No modifications
  • ❌ Delete: No deletions

Allowed Operations

π•Š(Ξ©β‚…) = {
  𝕆ₒᡦₛₑᡣα΅₯β‚‘: βœ“,    // Full analysis
  𝕆α΅₯α΅’α΅£β‚œα΅€β‚β‚—: ~,    // Limited evaluation
  𝕆ᡣₑₐₗ: βœ—        // No changes
}

Enabled Functions

  • validate_output - Check correctness
  • verify_against_plan - Compare to spec
  • report_deviations - Document issues

Key Activities

  1. Code Review

    "Review authentication implementation"
    "Check code quality and standards"
    
  2. Requirement Verification

    βœ… Requirement [↗️σ₁:R₁] implemented
    ⚠️ Requirement [↗️σ₁:Rβ‚‚] partially done
    ❌ Requirement [↗️σ₁:R₃] missing
    
  3. Protection Audit

    "Verify all critical code protected"
    "Check protection coverage"
    

Memory Updates

  • Οƒβ‚… (progress.md): Review results
  • Οƒβ‚„ (activeContext.md): Issues found

Context Preferences

MΞ“[Ξ©β‚…] = [Γ₃, Γ₁, Γ₆]  // Code, Files, Git

Best Practices

  • Be thorough
  • Check every requirement
  • Verify protection
  • Document all findings
  • Don't fix issues (wrong mode!)

Common Commands

/review
!af implemented-files.js   # Review targets
!ag main...feature        # Compare changes
"Review against requirements"

Transition Triggers

  • To EXECUTE: Fix issues found
  • To PLAN: Major changes needed
  • To RESEARCH: Investigate problems

πŸ”„ Mode Transition Rules

Valid Transitions

All modes can transition to any other mode:

Ω₁ ↔ Ξ©β‚‚ ↔ Ω₃ ↔ Ξ©β‚„ ↔ Ξ©β‚…

Standard Flow

RESEARCH β†’ INNOVATE β†’ PLAN β†’ EXECUTE β†’ REVIEW
    Ω₁        Ξ©β‚‚       Ω₃      Ξ©β‚„       Ξ©β‚…

Transition Process

  1. Backup current state
  2. Verify completion
  3. Switch mode
  4. Update permissions
  5. Load context
  6. Log transition

Quick Reference Card

From\To Research Innovate Plan Execute Review
Research - Common Common Rare Rare
Innovate Common - Common Never Rare
Plan Common Common - Common Rare
Execute Never Never Common - Common
Review Common Rare Common Common -

πŸ“š Related Topics


← Command Reference | Home | Permission Matrix β†’