geminize 1.0.0 → 1.2.0

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-main.mdc

@@ -0,0 +1,142 @@
+---
+description: Visual process map for VAN QA mode (Technical Validation Entry Point)
+globs: van-qa-main.mdc
+alwaysApply: false
+---
+# VAN MODE: QA TECHNICAL VALIDATION (Main Entry)
+
+> **TL;DR:** This is the entry point for the QA validation process that executes *after* CREATIVE mode and *before* BUILD mode. It ensures technical requirements are met before implementation begins.
+
+## 📣 HOW TO USE THESE QA RULES
+
+To access any QA validation rule or component, use the `fetch_rules` tool with exact rule names:
+
+```
+// CRITICAL: Always use fetch_rules to load validation components
+// For detailed examples and guidance, load:
+// isolation_rules/visual-maps/van-qa-utils/rule-calling-guide
+```
+
+## 🚀 VAN QA MODE ACTIVATION
+
+After completing CREATIVE mode, when the user types "VAN QA", respond:
+
+```mermaid
+graph TD
+    UserQA["User Types: QA"] --> HighPriority["⚠️ HIGH PRIORITY COMMAND"]
+    HighPriority --> CurrentTask["Pause Current Task/Process"]
+    CurrentTask --> LoadQA["Load QA Main Map (This File)"]
+    LoadQA --> RunQA["Execute QA Validation Process"]
+    RunQA --> QAResults{"QA Results"}
+    
+    QAResults -->|"PASS"| ResumeFlow["Resume Prior Process Flow"]
+    QAResults -->|"FAIL"| FixIssues["Fix Identified Issues"]
+    FixIssues --> ReRunQA["Re-run QA Validation"]
+    ReRunQA --> QAResults
+    
+    style UserQA fill:#f8d486,stroke:#e8b84d,color:black
+    style HighPriority fill:#ff0000,stroke:#cc0000,color:white,stroke-width:3px
+    style LoadQA fill:#4da6ff,stroke:#0066cc,color:white
+    style RunQA fill:#4da6ff,stroke:#0066cc,color:white
+    style QAResults fill:#f6546a,stroke:#c30052,color:white
+```
+
+### QA Interruption Rules
+
+1. **Immediate Precedence:** `QA` command interrupts everything.
+2. **Load & Execute:** Load this map (`van-qa-main.mdc`) and its components (see below).
+3. **Remediation Priority:** Fixes take priority over pending mode switches.
+4. **Resume:** On PASS, resume the previous flow.
+
+```
+⚠️ QA OVERRIDE ACTIVATED
+All other processes paused
+QA validation checks now running...
+Any issues found MUST be remediated before continuing with normal process flow
+```
+
+## 🔍 TECHNICAL VALIDATION OVERVIEW
+
+Four-point validation process with selective loading:
+
+```mermaid
+graph TD
+    VANQA["VAN QA MODE"] --> FourChecks["FOUR-POINT VALIDATION"]
+    
+    FourChecks --> DepCheck["1️⃣ DEPENDENCY VERIFICATION
+    Load: van-qa-checks/dependency-check.mdc"]
+    DepCheck --> ConfigCheck["2️⃣ CONFIGURATION VALIDATION
+    Load: van-qa-checks/config-check.mdc"]
+    ConfigCheck --> EnvCheck["3️⃣ ENVIRONMENT VALIDATION
+    Load: van-qa-checks/environment-check.mdc"]
+    EnvCheck --> MinBuildCheck["4️⃣ MINIMAL BUILD TEST
+    Load: van-qa-checks/build-test.mdc"]
+    
+    MinBuildCheck --> ValidationResults{"All Checks<br>Passed?"}
+    ValidationResults -->|"Yes"| SuccessReport["GENERATE SUCCESS REPORT
+    Load: van-qa-utils/reports.mdc"]
+    ValidationResults -->|"No"| FailureReport["GENERATE FAILURE REPORT
+    Load: van-qa-utils/reports.mdc"]
+    
+    SuccessReport --> BUILD_Transition["Trigger BUILD Mode
+    Load: van-qa-utils/mode-transitions.mdc"]
+    FailureReport --> FixIssues["Fix Technical Issues
+    Load: van-qa-utils/common-fixes.mdc"]
+    FixIssues --> ReValidate["Re-validate (Re-run VAN QA)"]
+    ReValidate --> FourChecks
+    
+    style VANQA fill:#4da6ff,stroke:#0066cc,color:white
+    style FourChecks fill:#f6546a,stroke:#c30052,color:white
+    style ValidationResults fill:#f6546a,stroke:#c30052,color:white
+    style BUILD_Transition fill:#10b981,stroke:#059669,color:white
+    style FixIssues fill:#ff5555,stroke:#dd3333,color:white
+```
+
+## 🔄 INTEGRATION WITH DESIGN DECISIONS
+
+Reads Creative Phase outputs to inform validation:
+
+```mermaid
+graph TD
+    Start["Read Design Decisions"] --> ReadCreative["Parse Creative Phase<br>Documentation"]
+    ReadCreative --> ExtractTech["Extract Technology<br>Choices"]
+    ExtractTech --> ExtractDeps["Extract Required<br>Dependencies"]
+    ExtractDeps --> BuildValidationPlan["Build Validation<br>Plan"]
+    BuildValidationPlan --> StartValidation["Start Four-Point<br>Validation Process"]
+    
+    style Start fill:#4da6ff,stroke:#0066cc,color:white
+    style ExtractTech fill:#f6546a,stroke:#c30052,color:white
+    style BuildValidationPlan fill:#10b981,stroke:#059669,color:white
+    style StartValidation fill:#f6546a,stroke:#c30052,color:white
+```
+
+## 📋 COMPONENT LOADING SEQUENCE
+
+The QA validation process follows this selective loading sequence:
+
+1. **Main Entry (This File)**: `van-qa-main.mdc`
+2. **Validation Checks**:
+   - `van-qa-checks/dependency-check.mdc`
+   - `van-qa-checks/config-check.mdc`
+   - `van-qa-checks/environment-check.mdc`
+   - `van-qa-checks/build-test.mdc`
+3. **Utilities (As Needed)**:
+   - `van-qa-utils/reports.mdc`
+   - `van-qa-utils/common-fixes.mdc`
+   - `van-qa-utils/mode-transitions.mdc`
+
+## 📋 FINAL QA VALIDATION CHECKPOINT
+
+```
+✓ SECTION CHECKPOINT: QA VALIDATION
+- Dependency Verification Passed? [YES/NO]
+- Configuration Validation Passed? [YES/NO]
+- Environment Validation Passed? [YES/NO]
+- Minimal Build Test Passed? [YES/NO]
+
+→ If all YES: Ready for BUILD mode transition.
+→ If any NO: Fix identified issues and re-run VAN QA.
+```
+
+**Next Step (on PASS):** Trigger BUILD mode (load `van-qa-utils/mode-transitions.mdc`).
+**Next Step (on FAIL):** Address issues (load `van-qa-utils/common-fixes.mdc`) and re-run `VAN QA`. 

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/common-fixes.mdc

@@ -0,0 +1,92 @@
+---
+description: Utility for VAN QA common validation fixes
+globs: van-qa-utils/common-fixes.mdc
+alwaysApply: false
+---
+# VAN QA: COMMON VALIDATION FIXES
+
+> **TL;DR:** This component provides common fixes for issues that may arise during the QA validation process.
+
+## 🧪 COMMON QA VALIDATION FIXES BY CATEGORY
+
+### Dependency Issues
+
+| Issue | Fix |
+|-------|-----|
+| **Missing Node.js** | Download and install Node.js from https://nodejs.org/ |
+| **Outdated npm** | Run `npm install -g npm@latest` to update |
+| **Missing packages** | Run `npm install` or `npm install [package-name]` |
+| **Package version conflicts** | Adjust versions in package.json and run `npm install` |
+| **Dependency resolution issues** | Run `npm cache clean -f` and try installing again |
+
+### Configuration Issues
+
+| Issue | Fix |
+|-------|-----|
+| **Invalid JSON** | Use a JSON validator (e.g., jsonlint) to check syntax |
+| **Missing React plugin** | Add `import react from '@vitejs/plugin-react'` and `plugins: [react()]` to vite.config.js |
+| **Incompatible TypeScript config** | Update `tsconfig.json` with correct React settings |
+| **Mismatched version references** | Ensure consistent versions across configuration files |
+| **Missing entries in config files** | Add required fields to configuration files |
+
+### Environment Issues
+
+| Issue | Fix |
+|-------|-----|
+| **Permission denied** | Run terminal as administrator (Windows) or use sudo (Mac/Linux) |
+| **Port already in use** | Kill process using the port: `netstat -ano \| findstr :PORT` then `taskkill /F /PID PID` (Windows) or `lsof -i :PORT` then `kill -9 PID` (Mac/Linux) |
+| **Missing build tools** | Install required command-line tools (git, node, etc.) |
+| **Environment variable issues** | Set required environment variables: `$env:VAR_NAME = "value"` (PowerShell) or `export VAR_NAME="value"` (Bash) |
+| **Disk space issues** | Free up disk space, clean npm/package cache files |
+
+### Build Test Issues
+
+| Issue | Fix |
+|-------|-----|
+| **Build fails** | Check console for specific error messages |
+| **Test fails** | Verify minimal configuration is correct |
+| **Path issues** | Ensure paths use correct separators for the platform (`\` for Windows, `/` for Mac/Linux) |
+| **Missing dependencies** | Make sure all required dependencies are installed |
+| **Script permissions** | Ensure script files have execution permissions (chmod +x on Unix) |
+
+## 📝 ISSUE DIAGNOSIS PROCEDURES
+
+### 1. Dependency Diagnosis
+```powershell
+# Find conflicting dependencies
+npm ls [package-name]
+
+# Check for outdated packages
+npm outdated
+
+# Check for vulnerabilities
+npm audit
+```
+
+### 2. Configuration Diagnosis
+```powershell
+# List all configuration files
+Get-ChildItem -Recurse -Include "*.json","*.config.js" | Select-Object FullName
+
+# Find missing references in tsconfig.json
+if (Test-Path "tsconfig.json") { 
+    $tsconfig = Get-Content "tsconfig.json" -Raw | ConvertFrom-Json
+    if (-not $tsconfig.compilerOptions.jsx) {
+        Write-Output "Missing jsx setting in tsconfig.json"
+    }
+}
+```
+
+### 3. Environment Diagnosis
+```powershell
+# Check process using a port (Windows)
+netstat -ano | findstr ":3000"
+
+# List environment variables
+Get-ChildItem Env:
+
+# Check disk space
+Get-PSDrive C | Select-Object Used,Free
+```
+
+**Next Step:** Return to the validation process or follow the specific fix recommendations provided above. 

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/mode-transitions.mdc

@@ -0,0 +1,101 @@
+---
+description: Utility for VAN QA mode transitions
+globs: van-qa-utils/mode-transitions.mdc
+alwaysApply: false
+---
+# VAN QA: MODE TRANSITIONS
+
+> **TL;DR:** This component handles transitions between modes, particularly the QA validation to BUILD mode transition, and prevents BUILD mode access without successful QA validation.
+
+## 🔒 BUILD MODE PREVENTION MECHANISM
+
+The system prevents moving to BUILD mode without passing QA validation:
+
+```mermaid
+graph TD
+    Start["User Types: BUILD"] --> CheckQA{"QA Validation<br>Completed?"}
+    CheckQA -->|"Yes and Passed"| AllowBuild["Allow BUILD Mode"]
+    CheckQA -->|"No or Failed"| BlockBuild["BLOCK BUILD MODE"]
+    BlockBuild --> Message["Display:<br>⚠️ QA VALIDATION REQUIRED"]
+    Message --> ReturnToVANQA["Prompt: Type VAN QA"]
+    
+    style CheckQA fill:#f6546a,stroke:#c30052,color:white
+    style BlockBuild fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
+    style Message fill:#ff5555,stroke:#dd3333,color:white
+    style ReturnToVANQA fill:#4da6ff,stroke:#0066cc,color:white
+```
+
+### Implementation Example (PowerShell):
+```powershell
+# Check QA status before allowing BUILD mode
+function Check-QAValidationStatus {
+    $qaStatusFile = "memory-bank\.qa_validation_status" # Assumes status is written by reports.mdc
+    
+    if (Test-Path $qaStatusFile) {
+        $status = Get-Content $qaStatusFile -Raw
+        if ($status -match "PASS") {
+            return $true
+        }
+    }
+    
+    # Display block message
+    Write-Output "`n`n"
+    Write-Output "🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫"
+    Write-Output "⛔️ BUILD MODE BLOCKED: QA VALIDATION REQUIRED"
+    Write-Output "⛔️ You must complete QA validation before proceeding to BUILD mode"
+    Write-Output "`n"
+    Write-Output "Type 'VAN QA' to perform technical validation"
+    Write-Output "`n"
+    Write-Output "🚫 NO IMPLEMENTATION CAN PROCEED WITHOUT VALIDATION 🚫"
+    Write-Output "🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫🚫"
+    
+    return $false
+}
+```
+
+## 🚨 MODE TRANSITION TRIGGERS
+
+### CREATIVE to VAN QA Transition:
+After completing the CREATIVE phase, trigger this message to prompt QA validation:
+
+```
+⏭️ NEXT MODE: VAN QA
+To validate technical requirements before implementation, please type 'VAN QA'
+```
+
+### VAN QA to BUILD Transition (On Success):
+After successful QA validation, trigger this message to allow BUILD mode:
+
+```
+✅ TECHNICAL VALIDATION COMPLETE
+All prerequisites verified successfully
+You may now proceed to BUILD mode
+Type 'BUILD' to begin implementation
+```
+
+### Manual BUILD Mode Access (When QA Already Passed):
+When the user manually types 'BUILD', check the QA status before allowing access:
+
+```powershell
+# Handle BUILD mode request
+function Handle-BuildModeRequest {
+    if (Check-QAValidationStatus) {
+        # Allow transition to BUILD mode
+        Write-Output "`n"
+        Write-Output "✅ QA VALIDATION CHECK: PASSED"
+        Write-Output "Loading BUILD mode..."
+        Write-Output "`n"
+        
+        # Here you would load the BUILD mode map
+        # [Code to load BUILD mode map]
+        
+        return $true
+    }
+    
+    # QA validation failed or not completed, BUILD mode blocked
+    return $false
+}
+```
+
+**Next Step (on QA SUCCESS):** Continue to BUILD mode.
+**Next Step (on QA FAILURE):** Return to QA validation process. 

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/reports.mdc

@@ -0,0 +1,149 @@
+---
+description: Utility for VAN QA validation reports
+globs: van-qa-utils/reports.mdc
+alwaysApply: false
+---
+# VAN QA: VALIDATION REPORTS
+
+> **TL;DR:** This component contains the formats for comprehensive success and failure reports generated upon completion of the QA validation process.
+
+## 📋 COMPREHENSIVE SUCCESS REPORT FORMAT
+
+After all four validation points pass, generate this success report:
+
+```
+╔═════════════════════ 🔍 QA VALIDATION REPORT ══════════════════════╗
+│ PROJECT: [Project Name] | TIMESTAMP: [Current Date/Time]            │
+├─────────────────────────────────────────────────────────────────────┤
+│ 1️⃣ DEPENDENCIES: ✓ Compatible                                       │
+│ 2️⃣ CONFIGURATION: ✓ Valid & Compatible                             │
+│ 3️⃣ ENVIRONMENT: ✓ Ready                                             │
+│ 4️⃣ MINIMAL BUILD: ✓ Successful & Passed                            │
+├─────────────────────────────────────────────────────────────────────┤
+│ 🚨 FINAL VERDICT: PASS                                              │
+│ ➡️ Clear to proceed to BUILD mode                                   │
+╚═════════════════════════════════════════════════════════════════════╝
+```
+
+### Success Report Generation Example:
+```powershell
+function Generate-SuccessReport {
+    param (
+        [string]$ProjectName = "Current Project"
+    )
+    
+    $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
+    
+    $report = @"
+╔═════════════════════ 🔍 QA VALIDATION REPORT ══════════════════════╗
+│ PROJECT: $ProjectName | TIMESTAMP: $timestamp            │
+├─────────────────────────────────────────────────────────────────────┤
+│ 1️⃣ DEPENDENCIES: ✓ Compatible                                       │
+│ 2️⃣ CONFIGURATION: ✓ Valid & Compatible                             │
+│ 3️⃣ ENVIRONMENT: ✓ Ready                                             │
+│ 4️⃣ MINIMAL BUILD: ✓ Successful & Passed                            │
+├─────────────────────────────────────────────────────────────────────┤
+│ 🚨 FINAL VERDICT: PASS                                              │
+│ ➡️ Clear to proceed to BUILD mode                                   │
+╚═════════════════════════════════════════════════════════════════════╝
+"@
+    
+    # Save validation status (used by BUILD mode prevention mechanism)
+    "PASS" | Set-Content -Path "memory-bank\.qa_validation_status"
+    
+    return $report
+}
+```
+
+## ❌ FAILURE REPORT FORMAT
+
+If any validation step fails, generate this detailed failure report:
+
+```
+⚠️⚠️⚠️ QA VALIDATION FAILED ⚠️⚠️⚠️
+
+The following issues must be resolved before proceeding to BUILD mode:
+
+1️⃣ DEPENDENCY ISSUES:
+- [Detailed description of dependency issues]
+- [Recommended fix]
+
+2️⃣ CONFIGURATION ISSUES:
+- [Detailed description of configuration issues]
+- [Recommended fix]
+
+3️⃣ ENVIRONMENT ISSUES:
+- [Detailed description of environment issues]
+- [Recommended fix]
+
+4️⃣ BUILD TEST ISSUES:
+- [Detailed description of build test issues]
+- [Recommended fix]
+
+⚠️ BUILD MODE IS BLOCKED until these issues are resolved.
+Type 'VAN QA' after fixing the issues to re-validate.
+```
+
+### Failure Report Generation Example:
+```powershell
+function Generate-FailureReport {
+    param (
+        [string[]]$DependencyIssues = @(),
+        [string[]]$ConfigIssues = @(),
+        [string[]]$EnvironmentIssues = @(),
+        [string[]]$BuildIssues = @()
+    )
+    
+    $report = @"
+⚠️⚠️⚠️ QA VALIDATION FAILED ⚠️⚠️⚠️
+
+The following issues must be resolved before proceeding to BUILD mode:
+
+"@
+    
+    if ($DependencyIssues.Count -gt 0) {
+        $report += @"
+1️⃣ DEPENDENCY ISSUES:
+$(($DependencyIssues | ForEach-Object { "- $_" }) -join "`n")
+
+"@
+    }
+    
+    if ($ConfigIssues.Count -gt 0) {
+        $report += @"
+2️⃣ CONFIGURATION ISSUES:
+$(($ConfigIssues | ForEach-Object { "- $_" }) -join "`n")
+
+"@
+    }
+    
+    if ($EnvironmentIssues.Count -gt 0) {
+        $report += @"
+3️⃣ ENVIRONMENT ISSUES:
+$(($EnvironmentIssues | ForEach-Object { "- $_" }) -join "`n")
+
+"@
+    }
+    
+    if ($BuildIssues.Count -gt 0) {
+        $report += @"
+4️⃣ BUILD TEST ISSUES:
+$(($BuildIssues | ForEach-Object { "- $_" }) -join "`n")
+
+"@
+    }
+    
+    $report += @"
+⚠️ BUILD MODE IS BLOCKED until these issues are resolved.
+Type 'VAN QA' after fixing the issues to re-validate.
+"@
+    
+    # Save validation status (used by BUILD mode prevention mechanism)
+    "FAIL" | Set-Content -Path "memory-bank\.qa_validation_status"
+    
+    return $report
+}
+```
+
+**Next Step (on SUCCESS):** Load `van-qa-utils/mode-transitions.mdc` to handle BUILD mode transition.
+**Next Step (on FAILURE):** Load `van-qa-utils/common-fixes.mdc` for issue remediation guidance. 

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-guide.mdc

@@ -0,0 +1,66 @@
+---
+description: Comprehensive guide for calling VAN QA rules
+globs: van-qa-utils/rule-calling-guide.mdc
+alwaysApply: false
+---
+# VAN QA: COMPREHENSIVE RULE CALLING GUIDE
+
+> **TL;DR:** This reference guide shows how to properly call all VAN QA rules at the right time during the validation process.
+
+## 🔍 RULE CALLING BASICS
+
+Remember these key principles:
+1. Always use the `fetch_rules` tool to load rules
+2. Use exact rule paths
+3. Load components only when needed
+
+## 📋 MAIN QA ENTRY POINT
+
+When user types "VAN QA", load the main entry point:
+
+```
+fetch_rules with "isolation_rules/visual-maps/van-qa-main"
+```
+
+## 📋 VALIDATION CHECKS
+
+Load these components sequentially during validation:
+
+```
+1. fetch_rules with "isolation_rules/visual-maps/van-qa-checks/dependency-check"
+2. fetch_rules with "isolation_rules/visual-maps/van-qa-checks/config-check"
+3. fetch_rules with "isolation_rules/visual-maps/van-qa-checks/environment-check"
+4. fetch_rules with "isolation_rules/visual-maps/van-qa-checks/build-test"
+```
+
+## 📋 UTILITY COMPONENTS
+
+Load these when needed based on validation results:
+
+```
+- For reports: fetch_rules with "isolation_rules/visual-maps/van-qa-utils/reports"
+- For fixes: fetch_rules with "isolation_rules/visual-maps/van-qa-utils/common-fixes"
+- For transitions: fetch_rules with "isolation_rules/visual-maps/van-qa-utils/mode-transitions"
+```
+
+## ⚠️ CRITICAL REMINDERS
+
+Remember to call these rules at these specific points:
+- ALWAYS load the main QA entry point when "VAN QA" is typed
+- ALWAYS load dependency-check before starting validation
+- ALWAYS load reports after completing validation
+- ALWAYS load mode-transitions after successful validation
+- ALWAYS load common-fixes after failed validation
+
+## 🔄 FULL VALIDATION SEQUENCE
+
+Complete sequence for a QA validation process:
+
+1. Load main entry: `isolation_rules/visual-maps/van-qa-main`
+2. Load first check: `isolation_rules/visual-maps/van-qa-checks/dependency-check`
+3. Load second check: `isolation_rules/visual-maps/van-qa-checks/config-check`
+4. Load third check: `isolation_rules/visual-maps/van-qa-checks/environment-check`
+5. Load fourth check: `isolation_rules/visual-maps/van-qa-checks/build-test`
+6. If pass, load: `isolation_rules/visual-maps/van-qa-utils/reports`
+7. If pass, load: `isolation_rules/visual-maps/van-qa-utils/mode-transitions` 
+8. If fail, load: `isolation_rules/visual-maps/van-qa-utils/common-fixes` 

data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-help.mdc

@@ -0,0 +1,19 @@
+---
+description: Utility for remembering how to call VAN QA rules
+globs: van-qa-utils/rule-calling-help.mdc
+alwaysApply: false
+---
+# VAN QA: HOW TO CALL RULES
+
+> **TL;DR:** This file provides examples and reminders on how to properly call VAN QA rules using the fetch_rules tool.
+
+## 🚨 RULE CALLING SYNTAX
+
+Always use the `fetch_rules` tool with the correct syntax:
+
+```
+<function_calls>
+<invoke name="fetch_rules">
+<parameter name="rule_names">["isolation_rules/visual-maps/rule-name"]
+</invoke>
+</function_calls>