### Usage Example: /van Command Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md Provides an example of how to use the /van command with a task description. This command serves as the entry point for project initialization. ```text /van [task description] ``` -------------------------------- ### Usage Example: /plan Command Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md Demonstrates the usage of the /plan command, which is used to create detailed implementation plans based on the task requirements and project complexity. ```text /plan ``` -------------------------------- ### Plan Task with /plan Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md The `/plan` command is used for the planning phase of a task, particularly for Level 3 features as indicated in the example workflow. ```bash # Step 2: Plan (VAN routes to PLAN for Level 3) /plan ``` -------------------------------- ### Basic Workflow Example: Level 2 Simple Enhancement Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md Illustrates the command sequence for a Level 2 complexity task, such as a simple enhancement. This workflow includes planning before implementation. ```text /van → /plan → /do → /reflect → /archive ``` -------------------------------- ### Basic Workflow Example: Level 3-4 Feature/System Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md Shows the command sequence for higher complexity tasks (Level 3-4), involving planning, creative design decisions, implementation, reflection, and archiving. ```text /van → /plan → /creative → /do → /reflect → /archive ``` -------------------------------- ### Initialize Workflow with /van Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md The `/van` command is used to initialize the workflow, often for adding a new task. In the example, it's shown initializing with a user authentication task. ```bash # Step 1: Initialize /van Add user authentication with OAuth2 support ``` -------------------------------- ### Basic Workflow Example: Level 1 Bug Fix Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md Demonstrates the command sequence for a Level 1 complexity task, typically a quick bug fix. This workflow involves initialization, direct implementation, reflection, and archiving. ```text /van → /do → /reflect → /archive ``` -------------------------------- ### Implement Feature with /do Command (Bash) Source: https://context7.com/angry-robot-deals/cursor-memory-bank-angry/llms.txt Executes the /do command to implement planned changes using test-driven development. It reads implementation plans from memory-bank/tasks.md and design decisions from memory-bank/creative/creative-oauth-architecture.md. This command orchestrates setup, implementation, and testing phases, enforcing AI Quality Rules. ```bash # Implement the planned feature /do # Reads from: # - memory-bank/tasks.md (implementation plan) # - memory-bank/creative/creative-oauth-architecture.md (design decisions) # Implementation workflow (Level 3): # Phase 1: Setup dependencies # Tests: Verify passport and passport-oauth2 installation npm install passport passport-oauth2 npm install --save-dev @types/passport @types/passport-oauth2 # Phase 2: Implement OAuth provider # File: src/auth/oauth-provider.ts # Tests: Unit tests for strategy configuration, token exchange, profile parsing describe('OAuthProvider', () => { it('should initialize with correct client credentials', () => { const provider = new OAuthProvider(config); expect(provider.clientId).toBe(config.clientId); }); it('should exchange authorization code for tokens', async () => { const tokens = await provider.exchangeCode('auth_code_123'); expect(tokens.access_token).toBeDefined(); }); }); # Phase 3: Implement authentication middleware # File: src/auth/auth-middleware.ts # Tests: Integration tests for authentication flow # Enforces: Max 50 lines per method, 7±2 objects per method (AI Quality Rules) # Phase 4: Create auth routes # File: src/routes/auth-routes.ts # Tests: E2E tests for OAuth callback flow # Execute tests: npm test -- --coverage # Results documented in: # - memory-bank/tasks.md (phase completion checkboxes) # - memory-bank/progress.md (build status, test results) # Routes to: /reflect command after all phases pass ``` -------------------------------- ### Clone Memory Bank Repository Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md This command clones the Memory Bank repository into your current project directory, setting up the necessary files for its operation. Ensure you have Git installed and configured. ```bash git clone https://github.com/vanzan01/cursor-memory-bank.git ``` -------------------------------- ### Initialize Project with /van Command Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md The /van command is used to initialize a new project within the Memory Bank system. It analyzes the project, determines task complexity, and sets up the Memory Bank structure if it doesn't exist. ```text /van Initialize project for adding user authentication feature ``` -------------------------------- ### Initialize Project with /van Command Source: https://context7.com/angry-robot-deals/cursor-memory-bank-angry/llms.txt The /van command initializes the Memory Bank system. It detects the operating platform, analyzes task requirements, determines a complexity level (1-4), and directs the user to the appropriate subsequent workflow commands. It creates a standard directory structure for storing project information. ```bash # Initialize a new feature task /van Add user authentication with OAuth2 support # Expected behavior: # 1. Detects operating system (Linux/macOS/Windows) # 2. Creates memory-bank/ directory structure if not exists # 3. Analyzes task: "user authentication with OAuth2" # 4. Determines complexity: Level 3 (new feature with design decisions) # 5. Updates memory-bank/tasks.md with task metadata # 6. Routes to: /plan command # For a simple bug fix /van Fix null pointer exception in login handler # Expected behavior: # 1. Analyzes task: "bug fix in single component" # 2. Determines complexity: Level 1 (quick fix) # 3. Routes to: /do command (skips planning) # Memory Bank structure created: # memory-bank/ # ├── tasks.md # Task tracking and checklists # ├── activeContext.md # Current development focus # ├── progress.md # Implementation status # ├── projectbrief.md # Project foundation # ├── creative/ # Design decision documents # ├── reflection/ # Task reflection documents # └── archive/ # Completed task archives ``` -------------------------------- ### Implement Code with /do Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md The `/do` command implements planned changes based on tasks and creative decisions. It follows a TDD approach, tests the implementation, and updates task and progress files. It reads from `memory-bank/tasks.md` and creative phase documents. ```bash # Step 4: Implement the feature /do ``` -------------------------------- ### Reflect on Implementation with /reflect Source: https://github.com/angry-robot-deals/cursor-memory-bank-angry/blob/main/README.md The `/reflect` command facilitates structured reflection on completed implementation. It compares the work against the plan, documents successes, challenges, and lessons learned, creating `memory-bank/reflection/reflection-[task_id].md` files. ```bash # Step 5: Reflect on the implementation /reflect ```