Productivity & Workflow⌨️cursor🌐universal

Cursor AI Rules Framework

Comprehensive AI prompting framework for Cursor IDE - Autonomous Principal Engineer operational doctrine

Quick Start

Install this Skill

npx skills add xLUPOx/cursor-ai-rules-framework
# Cursor AI Rules Framework

A comprehensive, evidence-first prompting framework designed to elevate AI agents from simple command executors to **Autonomous Principal Engineers**.

## 🎯 Philosophy

**Autonomy through discipline. Trust through verification.**

This framework enforces a rigorous workflow of reconnaissance, planning, safe execution, and self-improvement, ensuring every action is deliberate, verifiable, and aligned with senior engineering best practices.

## 📁 Framework Overview

### Core Components
- **GLOBAL-RULES.mdc** - Main operational doctrine and protocols
- **commands/** - Workflow commands for doctrine evolution (`retro`, `retro-integrate`) - Location: `.cursor/commands/`
- **doctrine-evolution/** - Doctrine evolution log and lessons tracking - Location: `.cursor/doctrine-evolution/`
- **workflow/** - Planning and execution rules for development tasks
- **docs/** - Context-aware documentation system (corporate vs startup)
- **estensions/** - Specialized rules for specific domains

### Documentation System
- **Guidelines** - Template base for creating feature-specific guidelines (corporate/startup contexts)
- **Templates** - Reusable starting points for features and tasks
- **Active Work** - Current development with feature-specific guidelines that extend and integrate with general guidelines
- **Workflow Integration** - Automated execution with safety protocols using integrated guidelines approach

## 🚀 Quick Start

### 1. Install the Core Doctrine

**For Global Use (Recommended):**
- Install `GLOBAL-RULES.mdc` as a global rule in your Cursor IDE
- This ensures all your projects benefit from this disciplined foundation

**For Project-Specific Use:**
- Place the content in a project-specific `.cursor/rules/` directory
- This will override global settings for specific projects

### 2. Use the Workflow Commands (Recommended)

**Activate workflows using command references in chat:**

| Command | Purpose | How to Use |
|---------|---------|------------|
| **`/retro`** | Self-Improvement Loop | Type `/retro` in chat at end of session |
| **`/retro-integrate`** | Integrate Lessons into Doctrine | Type `/retro-integrate [lesson-id]` in chat after reviewing `.cursor/doctrine-evolution/log.md` |

**Example Usage:**
```
/retro
```

**Note:** GLOBAL-RULES.mdc contains all operational protocols (Phase 0-5 workflows). No separate `request` or `refresh` commands needed when `alwaysApply: true`. Use `/retro` only for doctrine evolution at end of sessions.

### 2b. Legacy Playbooks (Alternative)

**Legacy templates available in `OLD/` directory - copy and paste into chat:**

| Playbook | Purpose | How to Use |
|----------|---------|------------|
| **`OLD/02 - request.md`** | Standard Operating Procedure | Copy full content, replace placeholder with your goal, paste in chat |
| **`OLD/03 - refresh.md`** | Root Cause Analysis | Use when bugs persist and simpler attempts failed |
| **`OLD/04 - retro.md`** | Self-Improvement Loop | Use at end of session to capture learnings and improve the framework |

**Note:** Command `/retro` enables doctrine evolution workflow. GLOBAL-RULES.mdc contains all operational protocols (no need for separate request/refresh commands when `alwaysApply: true`).

### 3. Apply Optional Directives

**These are user rules - install in Cursor settings or append to playbooks:**

| Directive | Type | Function | How to Use |
|-----------|------|----------|------------|
| **`05 - concise.md`** | User Rule | Radically concise communication | Install as global rule or append to playbooks |
| **`06 - no-absolute-right.md`** | User Rule | Professional communication guidelines | Install as global rule to avoid sycophantic language |

## 📁 Framework Components

### Core Files

- **`GLOBAL-RULES.mdc`** - Main framework documentation and operational doctrine
- **`commands/retro.md`** - Retrospective and doctrine evolution command (location: `.cursor/commands/retro.md`)
- **`commands/retro-integrate.md`** - Semi-automatic doctrine integration protocol (location: `.cursor/commands/retro-integrate.md`)
- **`workflow/plan.md`** - Planning phase protocols
- **`workflow/execute.md`** - Execution phase protocols

### Specialized Extensions

**These are user rules - install in Cursor settings for specific domains:**

| Extension File | Type | Function | When to Use |
|----------------|------|----------|-------------|
| **`07 - notebook-management.md`** | User Rule | Jupyter notebook protocols | When working with Jupyter notebooks |
| **`08 - notebook-testing.md`** | User Rule | Notebook testing patterns | For notebook testing workflows |
| **`09 - notebook-analytics.md`** | User Rule | Analytics workflows | For data analysis projects |
| **`10 - pinescript-management.md`** | User Rule | Pine Script development | When developing TradingView indicators |
| **`11 - pinescript-advanced.md`** | User Rule | Advanced Pine Script patterns | For complex Pine Script implementations |

### Legacy Files

**Hist

... (truncated)
Repository
3stars
5forks
View on GitHub
Details
DiscoveredJan 19, 2026
Last UpdatedDec 30, 2025
Author@xLUPOx
Quality Score
33/100