---
description: Operational guidelines for Lootah Robotics G1 3D Configurator development
alwaysApply: true
---

# Lootah Robotics G1 3D Configurator - Operational Rules

## Prompt Adherence

- **Strict Following**: Always adhere to prompt instructions including Context, Objective, Constraints, File Structure, and Implementation Details
- **No Deviations**: Do NOT introduce features, libraries, or architectural changes not explicitly requested
- **Sequential Execution**: Execute prompts sequentially; output of previous prompt forms context for next
- **Contextual Awareness**: Maintain awareness of overall project goal and progress made

## Coding Standards

- Write clean, readable, well-structured code; adhere to ESLint/Prettier conventions
- **TypeScript First**: Use TypeScript for all new code; avoid `any` unless absolutely necessary
- **Performance Minded**: Prioritize performance for 3D rendering and state management; use memoization and lazy loading
- **Error Handling**: Implement robust error handling with informative feedback and logging
- **Modularity**: Design components with clear responsibilities; favor composition over inheritance

## UI/UX & Design

- **Design System**: Adhere to `yslootahtech.com` corporate dark-tech theme with glassmorphism design
- **Responsiveness**: All UI and 3D scene must be fully responsive
- **Accessibility (WCAG)**: Keyboard navigation, ARIA attributes, sufficient color contrast
- **Immersive Experience**: Smooth transitions, intuitive interactions, subtle animations
- **User Feedback**: Clear and immediate visual feedback for all interactions

## Asset Management

- All 3D models (GLB/GLTF), textures, media must be optimized for web delivery
- External models loaded dynamically and attached without altering base model geometry/materials
- Use relative paths for assets (e.g., `public/g1-model.glb`)

## Operational Rules

- **No Unapproved Dependencies**: Do NOT add external libraries unless explicitly approved
- **Self-Correction**: Analyze errors, identify root cause, fix properly; don't repeat mistakes
- **Documentation**: Clear inline comments for complex logic; self-documenting code structure
- **Testing**: Automated tests for critical functionalities (state management, 3D interactions)