[CHORE] Introduce optimized Cursor rules for SubZilla.

Author: onyxdevs

.cursor/README.md

@@ -0,0 +1,51 @@
+# Cursor Rules Structure
+
+This directory contains optimized rules for Cursor AI assistance in the SubZilla project.
+
+## 📁 Rule Files
+
+### `subzilla-essentials.mdc`
+
+Main development rules covering:
+
+- Core execution principles (SEARCH FIRST, REUSE PATTERNS)
+- Architecture patterns and monorepo structure
+- TypeScript conventions
+- Development workflow
+
+### `ai-corrections.mdc`
+
+Specific corrections for common AI mistakes:
+
+- Prevents unnecessary file creation
+- Enforces emoji logging
+- Blocks skeleton code generation
+- Maintains existing patterns
+
+### `quick-reference.mdc`
+
+Copy-paste examples for:
+
+- Service class patterns
+- CLI command structure
+- Import conventions
+- Error handling templates
+
+## 🚀 Usage
+
+These rules are automatically loaded by Cursor based on file globs:
+
+- `subzilla-essentials.mdc`: Manual reference (not always applied)
+- `ai-corrections.mdc`: Always applied to prevent common mistakes
+- `quick-reference.mdc`: Manual reference for code examples
+
+## 📝 Maintenance
+
+- Keep rules focused on AI behavior, not documentation
+- Update `ai-corrections.mdc` when noticing repeated AI mistakes
+- Add new patterns to `quick-reference.mdc` as they emerge
+- Review quarterly and remove outdated rules
+
+## 🔄 Migration
+
+Old verbose rules are backed up in `.cursor/rules.backup/` if needed for reference.

.cursor/rules/ai-corrections.mdc

@@ -0,0 +1,42 @@
+---
+description: Specific corrections for common AI mistakes in SubZilla
+globs: ['**/*.ts']
+alwaysApply: true
+---
+
+# AI Behavior Corrections
+
+## ❌ Common AI Mistakes to Prevent
+
+### 1. Creating Unnecessary Files
+
+**WRONG:** Creating new utility files for simple functions
+**RIGHT:** Add to existing service classes or utils
+
+### 2. Forgetting Emoji Logging
+
+**WRONG:** `console.log('Processing file...')`
+**RIGHT:** `console.log('🔄 Processing file...')`
+
+### 3. Skeleton Code
+
+**WRONG:** `// TODO: Implement error handling`
+**RIGHT:** Complete implementation with try/catch and context
+
+### 4. Over-Complex Solutions
+
+**WRONG:** Creating abstract factories for 2 implementations
+**RIGHT:** Simple strategy pattern or conditional logic
+
+### 5. Ignoring Existing Patterns
+
+**WRONG:** New error handling approach
+**RIGHT:** Follow existing FormattingStripper/SubtitleProcessor patterns
+
+## ✅ AI Should Always
+
+- Search codebase before implementing
+- Extend existing classes/patterns
+- Use workspace imports for cross-package refs
+- Include comprehensive error handling
+- Test with `yarn start` before claiming completion