geminize 1.0.0 → 1.2.0

data/.cursor/rules/isolation_rules/Level3/task-tracking-intermediate.mdc

@@ -0,0 +1,135 @@
+---
+description: task tracking intermediate
+globs: task-tracking-intermediate.mdc
+alwaysApply: false
+---
+# LEVEL 3 INTERMEDIATE TASK TRACKING
+
+> **TL;DR:** This document provides structured task tracking guidelines for Level 3 (Intermediate Feature) tasks, using visual tracking elements and clear checkpoints.
+
+## 🔍 TASK TRACKING WORKFLOW
+
+```mermaid
+graph TD
+    Start["Task Start"] --> Init["📋 Initialize<br>Task Entry"]
+    Init --> Struct["🏗️ Create Task<br>Structure"]
+    Struct --> Track["📊 Progress<br>Tracking"]
+    Track --> Update["🔄 Regular<br>Updates"]
+    Update --> Complete["✅ Task<br>Completion"]
+    
+    Struct --> Components["Components:"]
+    Components --> Req["Requirements"]
+    Components --> Steps["Implementation<br>Steps"]
+    Components --> Creative["Creative Phase<br>Markers"]
+    Components --> Check["Checkpoints"]
+    
+    Track --> Status["Track Status:"]
+    Status --> InProg["🔄 In Progress"]
+    Status --> Block["⛔ Blocked"]
+    Status --> Done["✅ Complete"]
+    Status --> Skip["⏭️ Skipped"]
+    
+    style Start fill:#4da6ff,stroke:#0066cc,color:white
+    style Init fill:#ffa64d,stroke:#cc7a30,color:white
+    style Struct fill:#4dbb5f,stroke:#36873f,color:white
+    style Track fill:#d94dbb,stroke:#a3378a,color:white
+    style Update fill:#4dbbbb,stroke:#368787,color:white
+    style Complete fill:#d971ff,stroke:#a33bc2,color:white
+```
+
+## 📋 TASK ENTRY TEMPLATE
+
+```markdown
+# [Task Title]
+
+## Requirements
+- [ ] Requirement 1
+- [ ] Requirement 2
+- [ ] Requirement 3
+
+## Components Affected
+- Component 1
+- Component 2
+- Component 3
+
+## Implementation Steps
+1. [ ] Step 1
+2. [ ] Step 2
+3. [ ] Step 3
+
+## Creative Phases Required
+- [ ] 🎨 UI/UX Design
+- [ ] 🏗️ Architecture Design
+- [ ] ⚙️ Algorithm Design
+
+## Checkpoints
+- [ ] Requirements verified
+- [ ] Creative phases completed
+- [ ] Implementation tested
+- [ ] Documentation updated
+
+## Current Status
+- Phase: [Current Phase]
+- Status: [In Progress/Blocked/Complete]
+- Blockers: [If any]
+```
+
+## 🔄 PROGRESS TRACKING VISUALIZATION
+
+```mermaid
+graph TD
+    subgraph "TASK PROGRESS"
+    P1["✓ Requirements<br>Defined"]
+    P2["✓ Components<br>Identified"]
+    P3["→ Creative Phase<br>In Progress"]
+    P4["□ Implementation"]
+    P5["□ Testing"]
+    P6["□ Documentation"]
+    end
+    
+    style P1 fill:#4dbb5f,stroke:#36873f,color:white
+    style P2 fill:#4dbb5f,stroke:#36873f,color:white
+    style P3 fill:#ffa64d,stroke:#cc7a30,color:white
+    style P4 fill:#d94dbb,stroke:#a3378a,color:white
+    style P5 fill:#4dbbbb,stroke:#368787,color:white
+    style P6 fill:#d971ff,stroke:#a33bc2,color:white
+```
+
+## ✅ UPDATE PROTOCOL
+
+```mermaid
+sequenceDiagram
+    participant Task as Task Entry
+    participant Status as Status Update
+    participant Creative as Creative Phase
+    participant Implementation as Implementation
+    
+    Task->>Status: Update Progress
+    Status->>Creative: Flag for Creative Phase
+    Creative->>Implementation: Complete Design
+    Implementation->>Status: Update Status
+    Status->>Task: Mark Complete
+```
+
+## 🎯 CHECKPOINT VERIFICATION
+
+| Phase | Verification Items | Status |
+|-------|-------------------|--------|
+| Requirements | All requirements documented | [ ] |
+| Components | Affected components listed | [ ] |
+| Creative | Design decisions documented | [ ] |
+| Implementation | Code changes tracked | [ ] |
+| Testing | Test results recorded | [ ] |
+| Documentation | Updates completed | [ ] |
+
+## 🔄 DOCUMENT MANAGEMENT
+
+```mermaid
+graph TD
+    Current["Current Documents"] --> Active["Active:<br>- task-tracking-intermediate.md<br>- planning-comprehensive.md"]
+    Current --> Required["Required Next:<br>- creative-phase-enforcement.md<br>- implementation-phase-reference.md"]
+    
+    style Current fill:#4da6ff,stroke:#0066cc,color:white
+    style Active fill:#4dbb5f,stroke:#36873f,color:white
+    style Required fill:#ffa64d,stroke:#cc7a30,color:white
+``` 

data/.cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc

@@ -0,0 +1,187 @@
+---
+description: creative phase architecture
+globs: creative-phase-architecture.md
+alwaysApply: false
+---
+
+# CREATIVE PHASE: ARCHITECTURE DESIGN
+
+> **TL;DR:** This document provides structured guidance for architectural design decisions during creative phases, ensuring comprehensive evaluation of options and clear documentation of architectural choices.
+
+## 🏗️ ARCHITECTURE DESIGN WORKFLOW
+
+```mermaid
+graph TD
+    Start["Architecture<br>Design Start"] --> Req["1. Requirements<br>Analysis"]
+    Req --> Comp["2. Component<br>Identification"]
+    Comp --> Options["3. Architecture<br>Options"]
+    Options --> Eval["4. Option<br>Evaluation"]
+    Eval --> Decision["5. Decision &<br>Documentation"]
+    Decision --> Valid["6. Validation &<br>Verification"]
+    
+    style Start fill:#4da6ff,stroke:#0066cc,color:white
+    style Req fill:#ffa64d,stroke:#cc7a30,color:white
+    style Comp fill:#4dbb5f,stroke:#36873f,color:white
+    style Options fill:#d94dbb,stroke:#a3378a,color:white
+    style Eval fill:#4dbbbb,stroke:#368787,color:white
+    style Decision fill:#d971ff,stroke:#a33bc2,color:white
+    style Valid fill:#ff71c2,stroke:#c23b8a,color:white
+```
+
+## 📋 ARCHITECTURE DECISION TEMPLATE
+
+```markdown
+# Architecture Decision Record
+
+## Context
+- System Requirements:
+  - [Requirement 1]
+  - [Requirement 2]
+- Technical Constraints:
+  - [Constraint 1]
+  - [Constraint 2]
+
+## Component Analysis
+- Core Components:
+  - [Component 1]: [Purpose/Role]
+  - [Component 2]: [Purpose/Role]
+- Interactions:
+  - [Interaction 1]
+  - [Interaction 2]
+
+## Architecture Options
+### Option 1: [Name]
+- Description: [Brief description]
+- Pros:
+  - [Pro 1]
+  - [Pro 2]
+- Cons:
+  - [Con 1]
+  - [Con 2]
+- Technical Fit: [High/Medium/Low]
+- Complexity: [High/Medium/Low]
+- Scalability: [High/Medium/Low]
+
+### Option 2: [Name]
+[Same structure as Option 1]
+
+## Decision
+- Chosen Option: [Option name]
+- Rationale: [Explanation]
+- Implementation Considerations:
+  - [Consideration 1]
+  - [Consideration 2]
+
+## Validation
+- Requirements Met:
+  - [✓] Requirement 1
+  - [✓] Requirement 2
+- Technical Feasibility: [Assessment]
+- Risk Assessment: [Evaluation]
+```
+
+## 🎯 ARCHITECTURE EVALUATION CRITERIA
+
+```mermaid
+graph TD
+    subgraph "EVALUATION CRITERIA"
+    C1["Scalability"]
+    C2["Maintainability"]
+    C3["Performance"]
+    C4["Security"]
+    C5["Cost"]
+    C6["Time to Market"]
+    end
+    
+    style C1 fill:#4dbb5f,stroke:#36873f,color:white
+    style C2 fill:#ffa64d,stroke:#cc7a30,color:white
+    style C3 fill:#d94dbb,stroke:#a3378a,color:white
+    style C4 fill:#4dbbbb,stroke:#368787,color:white
+    style C5 fill:#d971ff,stroke:#a33bc2,color:white
+    style C6 fill:#ff71c2,stroke:#c23b8a,color:white
+```
+
+## 📊 ARCHITECTURE VISUALIZATION TEMPLATES
+
+### Component Diagram Template
+```mermaid
+graph TD
+    subgraph "SYSTEM ARCHITECTURE"
+    C1["Component 1"]
+    C2["Component 2"]
+    C3["Component 3"]
+    
+    C1 -->|"Interface 1"| C2
+    C2 -->|"Interface 2"| C3
+    end
+    
+    style C1 fill:#4dbb5f,stroke:#36873f,color:white
+    style C2 fill:#ffa64d,stroke:#cc7a30,color:white
+    style C3 fill:#d94dbb,stroke:#a3378a,color:white
+```
+
+### Data Flow Template
+```mermaid
+sequenceDiagram
+    participant C1 as Component 1
+    participant C2 as Component 2
+    participant C3 as Component 3
+    
+    C1->>C2: Request
+    C2->>C3: Process
+    C3-->>C2: Response
+    C2-->>C1: Result
+```
+
+## ✅ VERIFICATION CHECKLIST
+
+```markdown
+## Architecture Design Verification
+- [ ] All system requirements addressed
+- [ ] Component responsibilities defined
+- [ ] Interfaces specified
+- [ ] Data flows documented
+- [ ] Security considerations addressed
+- [ ] Scalability requirements met
+- [ ] Performance requirements met
+- [ ] Maintenance approach defined
+
+## Implementation Readiness
+- [ ] All components identified
+- [ ] Dependencies mapped
+- [ ] Technical constraints documented
+- [ ] Risk assessment completed
+- [ ] Resource requirements defined
+- [ ] Timeline estimates provided
+```
+
+## 🔄 ARCHITECTURE REVIEW PROCESS
+
+```mermaid
+graph TD
+    subgraph "REVIEW PROCESS"
+    R1["Technical<br>Review"]
+    R2["Security<br>Review"]
+    R3["Performance<br>Review"]
+    R4["Final<br>Approval"]
+    end
+    
+    R1 --> R2 --> R3 --> R4
+    
+    style R1 fill:#4dbb5f,stroke:#36873f,color:white
+    style R2 fill:#ffa64d,stroke:#cc7a30,color:white
+    style R3 fill:#d94dbb,stroke:#a3378a,color:white
+    style R4 fill:#4dbbbb,stroke:#368787,color:white
+```
+
+## 🔄 DOCUMENT MANAGEMENT
+
+```mermaid
+graph TD
+    Current["Current Document"] --> Active["Active:<br>- creative-phase-architecture.md"]
+    Current --> Related["Related:<br>- creative-phase-enforcement.md<br>- planning-comprehensive.md"]
+    
+    style Current fill:#4da6ff,stroke:#0066cc,color:white
+    style Active fill:#4dbb5f,stroke:#36873f,color:white
+    style Related fill:#ffa64d,stroke:#cc7a30,color:white
+``` 

data/.cursor/rules/isolation_rules/main.mdc

@@ -0,0 +1,123 @@
+---
+description: main rule
+globs: main.mdc
+alwaysApply: false
+---
+
+# 🔍 ISOLATION-FOCUSED MEMORY BANK SYSTEM
+
+> **TL;DR:** This system is designed to work with Cursor custom modes, where each mode loads only the rules it needs. The system uses visual Mermaid diagrams and selective document loading to optimize context usage.
+
+## 🧭 MODE-SPECIFIC VISUAL MAPS
+
+```mermaid
+graph TD
+    subgraph Modes["Cursor Custom Modes"]
+        VAN["VAN MODE<br>Initialization"] --> PLAN["PLAN MODE<br>Task Planning"]
+        PLAN --> Creative["CREATIVE MODE<br>Design Decisions"]
+        Creative --> Implement["IMPLEMENT MODE<br>Code Implementation"]
+        Implement --> Reflect["REFLECT MODE<br>Task Review"]
+        Reflect --> Archive["ARCHIVE MODE<br>Documentation"]
+    end
+    
+    VAN -.->|"Loads"| VANRules["• main.md<br>• platform-awareness.md<br>• file-verification.md<br>• workflow-init.md"]
+    PLAN -.->|"Loads"| PLANRules["• main.md<br>• task-tracking.md<br>• planning-process.md"]
+    Creative -.->|"Loads"| CreativeRules["• main.md<br>• creative-phase.md<br>• design-patterns.md"]
+    Implement -.->|"Loads"| ImplementRules["• main.md<br>• command-execution.md<br>• implementation-guide.md"]
+    Reflect -.->|"Loads"| ReflectRules["• main.md<br>• reflection-format.md"]
+    Archive -.->|"Loads"| ArchiveRules["• main.md<br>• archiving-guide.md"]
+```
+
+## 📚 VISUAL PROCESS MAPS
+
+Each mode has its own visual process map:
+
+- [VAN Mode Map](mdc:visual-maps/van-mode-map.md)
+- [PLAN Mode Map](mdc:visual-maps/plan-mode-map.md)
+- [CREATIVE Mode Map](mdc:visual-maps/creative-mode-map.md)
+- [IMPLEMENT Mode Map](mdc:visual-maps/implement-mode-map.md)
+- [REFLECT Mode Map](mdc:visual-maps/reflect-mode-map.md)
+- [ARCHIVE Mode Map](mdc:visual-maps/archive-mode-map.md)
+
+## 🔄 FILE STATE VERIFICATION
+
+In this isolation-focused approach, Memory Bank files maintain continuity between modes:
+
+```mermaid
+graph TD
+    subgraph "Memory Bank Files"
+        tasks["tasks.md<br>Source of Truth"]
+        active["activeContext.md<br>Current Focus"]
+        creative["creative-*.md<br>Design Decisions"]
+        progress["progress.md<br>Implementation Status"]
+    end
+    
+    VAN["VAN MODE"] -->|"Creates/Updates"| tasks
+    VAN -->|"Creates/Updates"| active
+    
+    PLAN["PLAN MODE"] -->|"Reads"| tasks
+    PLAN -->|"Reads"| active
+    PLAN -->|"Updates"| tasks
+    
+    Creative["CREATIVE MODE"] -->|"Reads"| tasks
+    Creative -->|"Creates"| creative
+    Creative -->|"Updates"| tasks
+    
+    Implement["IMPLEMENT MODE"] -->|"Reads"| tasks
+    Implement -->|"Reads"| creative
+    Implement -->|"Updates"| tasks
+    Implement -->|"Updates"| progress
+    
+    Reflect["REFLECT MODE"] -->|"Reads"| tasks
+    Reflect -->|"Reads"| progress
+    Reflect -->|"Updates"| tasks
+    
+    Archive["ARCHIVE MODE"] -->|"Reads"| tasks
+    Archive -->|"Reads"| progress
+    Archive -->|"Archives"| creative
+```
+
+## 📋 MODE TRANSITION PROTOCOL
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant CurrentMode
+    participant NextMode
+    
+    CurrentMode->>CurrentMode: Complete Phase Requirements
+    CurrentMode->>User: "Phase complete. NEXT MODE: [mode name]"
+    User->>CurrentMode: End Current Mode
+    User->>NextMode: Start Next Mode
+    NextMode->>NextMode: Verify Required File State
+    
+    alt File State Valid
+        NextMode->>User: "Continuing from previous mode..."
+    else File State Invalid
+        NextMode->>User: "Required files not in expected state"
+        NextMode->>User: "Return to [previous mode] to complete requirements"
+    end
+```
+
+## 💻 PLATFORM-SPECIFIC COMMANDS
+
+| Action | Windows | Mac/Linux |
+|--------|---------|-----------|
+| Create file | `echo. > file.ext` | `touch file.ext` |
+| Create directory | `mkdir directory` | `mkdir -p directory` |
+| Change directory | `cd directory` | `cd directory` |
+| List files | `dir` | `ls` |
+| Show file content | `type file.ext` | `cat file.ext` |
+
+## ⚠️ COMMAND EFFICIENCY GUIDANCE
+
+For optimal performance, use efficient command chaining when appropriate:
+
+```
+# Efficient command chaining examples:
+mkdir -p project/{src,tests,docs} && cd project
+grep "TODO" $(find . -name "*.js")
+npm install && npm start
+```
+
+Refer to [command-execution.md](mdc:Core/command-execution.md) for detailed guidance.