CI / changes (push) Successful in 8s
CI / commitlint (push) Has been skipped
CI / openapi (push) Has been skipped
CI / web (push) Successful in 31s
CI / go (push) Successful in 51s
CI / bird2 (push) Successful in 15s
CI / release (push) Successful in 3m48s
Enhanced the MaintenancePoliciesTab by integrating a schedule editor for maintenance policies. Users can now select schedule modes, input custom cron expressions, and dynamically update the schedule preview. This update improves the user interface and experience for managing maintenance schedules.
2.2 KiB
2.2 KiB
VAN Command - Initialization & Entry Point
This command initializes the Memory Bank system, performs platform detection, determines task complexity, and routes to appropriate workflows.
Memory Bank Integration
CRITICAL: All Memory Bank files are located in memory-bank/ directory:
memory-bank/tasks.md- Source of truth for task trackingmemory-bank/activeContext.md- Current focusmemory-bank/progress.md- Implementation statusmemory-bank/projectbrief.md- Project foundation
Progressive Rule Loading
This command loads rules progressively to optimize context usage:
Step 1: Load Core Rules (Always Required)
Load: .cursor/rules/isolation_rules/main.mdc
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
Load: .cursor/rules/isolation_rules/Core/platform-awareness.mdc
Load: .cursor/rules/isolation_rules/Core/file-verification.mdc
Step 2: Load VAN Mode Map
Load: .cursor/rules/isolation_rules/visual-maps/van_mode_split/van-mode-map.mdc
Step 3: Load Complexity-Specific Rules (Based on Task Analysis)
After determining complexity level, load:
- Level 1:
.cursor/rules/isolation_rules/Level1/workflow-level1.mdc - Level 2-4: Load plan mode rules (transition to PLAN command)
Workflow
-
Platform Detection
- Detect operating system
- Adapt commands for platform
- Set path separators
-
Memory Bank Verification
- Check if
memory-bank/directory exists - If not, create Memory Bank structure
- Verify essential files exist
- Check if
-
Task Analysis
- Read
memory-bank/tasks.mdif exists - Analyze task requirements
- Determine complexity level (1-4)
- Read
-
Route Based on Complexity
- Level 1: Continue in VAN mode, proceed to implementation
- Level 2-4: Transition to
/plancommand
-
Update Memory Bank
- Update
memory-bank/tasks.mdwith complexity determination - Update
memory-bank/activeContext.mdwith current focus
- Update
Usage
Type /van followed by your task description or initialization request.
Example:
/van Initialize project for adding user authentication feature
Next Steps
- Level 1 tasks: Proceed directly to
/buildcommand - Level 2-4 tasks: Use
/plancommand for detailed planning