A symbolic, ultra-efficient AI prompt framework for software development assistance with code protection, context reference, and permission management capabilities.
Current version: RIPERsigma1.0.4.mdc
Try out CursorRIPER.sigma-lite, a Lite version without context references, permissions, or code protection.
CursorRIPER♦Σ is a highly optimized, symbolic implementation of the CursorRIPER framework designed to enhance AI-assisted software development. It uses a symbolic notation system with mathematical operators, emojis, and Greek letters to compress complex development workflows into a minimal, yet comprehensive, token footprint.
The framework reduces ~15,000 words of instructions to under 1,000 while preserving full functionality, making it dramatically more efficient for AI token usage. The idea came from Tof
- Symbolic Notation: Uses Greek letters (Ω, Π, Σ, Δ, Γ, ℙ), subscripts, and emoji for extreme conciseness
- RIPER Workflow Modes: Research, Innovate, Plan, Execute, Review (🔍R, 💡I, 📝P, ⚙️E, 🔎RV)
- Structured Memory System: Standardized file templates with cross-referencing
- Phase-based Project Management: Tracks project progress from initialization to maintenance
- Automatic Memory: Creates and maintains a structured memory bank for project context
- Code Protection System: Protects critical code sections with intelligent comment annotations
- Context Reference System: Manages and tracks file, code, and document references
- Permission System: Enforces mode-specific CRUD operations and handles violations
Ω₁ = 🔍R ⟶ ℙ(Ω₁) ⟶ Research: Gather information and document findings
Ω₂ = 💡I ⟶ ℙ(Ω₂) ⟶ Innovate: Explore options and suggest ideas
Ω₃ = 📝P ⟶ ℙ(Ω₃) ⟶ Plan: Create specifications and sequence steps
Ω₄ = ⚙️E ⟶ ℙ(Ω₄) ⟶ Execute: Implement code according to plan
Ω₅ = 🔎RV ⟶ ℙ(Ω₅) ⟶ Review: Validate output against requirements
Π₁ = 🌱UNINITIATED ⟶ Framework installed but not started
Π₂ = 🚧INITIALIZING ⟶ Setup in progress
Π₃ = 🏗️DEVELOPMENT ⟶ Main development work
Π₄ = 🔧MAINTENANCE ⟶ Long-term support
σ₁ = 📋projectbrief.md ⟶ Requirements, scope, criteria
σ₂ = 🏛️systemPatterns.md ⟶ Architecture, components, decisions
σ₃ = 💻techContext.md ⟶ Stack, environment, dependencies
σ₄ = 🔮activeContext.md ⟶ Focus, changes, next steps, context references
σ₅ = 📊progress.md ⟶ Status, milestones, issues
σ₆ = 🛡️protection.md ⟶ Protected regions, history, approvals, violations
Ψ₁ = PROTECTED ⟶ Highest protection, do not modify
Ψ₂ = GUARDED ⟶ Ask before modifying
Ψ₃ = INFO ⟶ Context note
Ψ₄ = DEBUG ⟶ Debugging code
Ψ₅ = TEST ⟶ Testing code
Ψ₆ = CRITICAL ⟶ Business logic, highest protection
Γ₁ = 📄 @Files ⟶ File references
Γ₂ = 📁 @Folders ⟶ Folder references
Γ₃ = 💻 @Code ⟶ Code references
Γ₄ = 📚 @Docs ⟶ Documentation references
Γ₅ = 📏 @Rules ⟶ Cursor rules references
Γ₆ = 🔄 @Git ⟶ Git history references
Γ₇ = 📝 @Notepads ⟶ Notepad references
Γ₈ = 📌 #Files ⟶ Pinned file references
ℙ = {C: create, R: read, U: update, D: delete}
ℙ(Ω₁) = {R: ✓, C: ✗, U: ✗, D: ✗} // Research mode
ℙ(Ω₂) = {R: ✓, C: ~, U: ✗, D: ✗} // Innovate mode (~: conceptual only)
ℙ(Ω₃) = {R: ✓, C: ✓, U: ~, D: ✗} // Plan mode (~: plan changes only)
ℙ(Ω₄) = {R: ✓, C: ✓, U: ✓, D: ~} // Execute mode (~: limited scope)
ℙ(Ω₅) = {R: ✓, C: ✗, U: ✗, D: ✗} // Review mode
- Create a memory bank directory in your project:
mkdir -p /memory-bank/backups-
Copy the CursorRIPER♦Σ framework
.mdcfiles to your project rules folder:.cursor/rules/ -
Initialize the framework with the AI assistant:
/start
Change modes by using the following commands with your AI assistant:
/research (or /r) - Research mode
/innovate (or /i) - Innovate mode
/plan (or /p) - Plan mode
/execute (or /e) - Execute mode
/review (or /rev) - Review mode
The framework automatically maintains six key memory files:
- Project Brief (σ₁): Defines requirements, success criteria, and scope
- System Patterns (σ₂): Captures architecture, components, and design decisions
- Technical Context (σ₃): Records technology stack, environment, and dependencies
- Active Context (σ₄): Tracks current focus, recent changes, next steps, and context references
- Progress Tracker (σ₅): Monitors project status, features, issues, and milestones
- Protection Registry (σ₆): Tracks protected code regions, history, approvals, and permission violations
The framework includes a robust code protection system that helps preserve critical code sections from unintended modifications:
- PROTECTED: Code that must not be modified under any circumstances
- GUARDED: Code that requires explicit permission before modification
- INFO: Context information relevant to understanding code
- DEBUG: Temporary code used for debugging purposes
- TEST: Code related to testing functionality
- CRITICAL: Business logic that must be treated with extreme care
Add code protection with shorthand commands:
!cp - Add PROTECTED comment
!cg - Add GUARDED comment
!ci - Add INFO comment
!cd - Add DEBUG comment
!ct - Add TEST comment
!cc - Add CRITICAL comment
See Protection Commands for full documentation.
The context reference system allows tracking and managing important files, code, and documents:
- @Files: Important files in the project
- @Folders: Relevant directories or folder structures
- @Code: Code sections, functions, or classes
- @Docs: Documentation or specification references
- @Rules: Cursor project rules references
- @Git: Git history or commit references
- @Notepads: Notepad content references
- #Files: Pinned file references
Manage context references with shorthand commands:
!af - Add file reference
!ad - Add directory reference
!ac - Add code reference
!adoc - Add documentation reference
!ar - Add rules reference
!ag - Add git reference
!an - Add notepad reference
!pf - Pin file to context
See Context Usage Guide for more details.
The permission system enforces appropriate operations for each mode and handles violations:
Each mode has a specific set of allowed CRUD operations:
- Research Mode: Read only
- Innovate Mode: Read and conceptual creation
- Plan Mode: Read, create, and plan updates
- Execute Mode: Read, create, update, and limited deletion
- Review Mode: Read only
Check and verify permissions with shorthand commands:
!ckp - Check permissions for current mode
!pm - Check if operation is permitted
!sp - Show permissions for specified mode
!vm - Verify mode appropriate for operation
See Permission Reference for quick reference.
- Automatic backups before destructive operations
- Confirmation prompts for critical actions
- Phase transition verification
- Error recovery suggestions
- Code protection system with mode-aware behavior
- Permission violation detection and recovery
- Context tracking with status indicators
See the Symbol Reference Guide for a complete list of symbols and notation used in the framework.
Contributions are welcome! Please feel free to submit a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.
CursorRIPER♦Σ: Symbolic efficiency for AI-assisted development with intelligent code protection, context awareness, and permission enforcement.