Skip to content
Prompt

zhuagui_cocos — Cursor Rules

by zhaolei828

AI Summary

CursorRIPER is an ambitious framework for structured AI-assisted development using RIPER modes (Research, Innovate, Plan, Execute, Review) with memory management, designed for developers seeking systematic project workflows in Cursor. However, its complex notation and incomplete implementation limit practical adoption.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "zhuagui_cocos — Cursor Rules" prompt rules to my project.
Repository: https://github.com/zhaolei828/zhuagui_cocos

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

use these rules for every chat

📚 Path & Index Definitions

📂 = "/memory-bank/" 📦 = "/memory-bank/backups/" 𝕋 = [read_files, ask_questions, observe_code, document_findings, suggest_ideas, explore_options, evaluate_approaches, create_plan, detail_specifications, sequence_steps, implement_code, follow_plan, test_implementation, validate_output, verify_against_plan, report_deviations] 𝕄 = [📂projectbrief.md, 📂systemPatterns.md, 📂techContext.md, 📂activeContext.md, 📂progress.md]

Ω RIPER Modes - Streamlined

Ω₁ = 🔍R ⟶ +𝕋[0:3] -𝕋[4:15] ⟶ [MODE: RESEARCH]+findings ↪ 🔄(/research, /r) ⟶ update(𝕄[2,3]) Ω₂ = 💡I ⟶ +𝕋[4:6] -𝕋[8:15] ⟶ [MODE: INNOVATE]+possibilities ↪ 🔄(/innovate, /i) ⟶ update(𝕄[3]) Ω₃ = 📝P ⟶ +𝕋[7:9] -𝕋[10:15] ⟶ [MODE: PLAN]+checklist₁₋ₙ ↪ 🔄(/plan, /p) ⟶ update(𝕄[3,4]) Ω₄ = ⚙️E ⟶ +𝕋[10:12] -[improve,create,deviate] ⟶ [MODE: EXECUTE]+progress ↪ 🔄(/execute, /e) ⟶ update(𝕄[3,4]) Ω₅ = 🔎RV ⟶ +𝕋[13:15] -[modify,improve] ⟶ [MODE: REVIEW]+{✅|⚠️} ↪ 🔄(/review, /rev) ⟶ update(𝕄[3,4])

Π Project Phases

Π₁ = 🌱UNINITIATED ⟶ framework_installed ∧ ¬project_started Π₂ = 🚧INITIALIZING ⟶ START_active ∧ setup_ongoing Π₃ = 🏗️DEVELOPMENT ⟶ main_development ∧ RIPER_active Π₄ = 🔧MAINTENANCE ⟶ long_term_support ∧ RIPER_active Π_transitions = { Π₁→Π₂: 🔄"/start", Π₂→Π₃: ✅completion(START_phase), Π₃↔Π₄: 🔄user_request }

🏁 START Phase (Π₂)

S₁₋₅ = [requirements, technology, architecture, scaffolding, environment] START_process = { S₀: create_directory(📂), S₁: gather(requirements) ⟶ create(𝕄[0]), S₂: select(technologies) ⟶ update(𝕄[2]), S₃: define(architecture) ⟶ create(𝕄[1]), S₄: scaffold(project) ⟶ create(directories), S₅: setup(environment) ⟶ update(𝕄[2]), S₆: initialize(memory) ⟶ create(𝕄[0:4]) }

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 7mo ago
Stale
AdoptionUnder 100 stars
0 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Issues0
Updated7mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more