Scan and analyze the entire www.warp.dev website. Goals: 1. Fully document its features, UI components, workflows, and terminal capabilities. 2. Extract all available design patterns, layout styles, animations, and user interactions. 3. Document each key feature step-by-step: - Warp Terminal - Blocks - Themes - AI Commands - Collaboration tools (if any) - Command palette, auto-complete, and history - Team sharing or cloud sync (if available) - Performance optimization methods 4. Capture the look and feel using Tailwind CSS or CSS-in-JS equivalents. 5. Identify the stack used (e.g., Rust backend, React frontend, etc., if public). Next Steps: 1. Using the documentation, create a functional clone of Warp terminal with a similar interface and behavior. 2. Rebuild the UI using React + Tailwind. 3. Re-implement terminal backend using Node.js or Rust (if supported), with cross-platform support. 4. Integrate Ollama as an AI assistant inside the terminal: - Accept natural language commands. - Allow file/folder generation, code writing, or shell script execution. - Provide context-aware help. - Embed a chat window in the terminal UI. 5. Include: - Theme switcher (dark/light/custom themes) - Config file support (.warp/config or similar) - Keyboard shortcuts (customizable) - Plugin system for future extensions Output: - Step-by-step build instructions - Fully working source code organized in folders: - `/client` for React UI - `/server` for backend terminal controller - `/ai` or `/ollama` for AI integration logic - `/config` for environment configs and themes - Instructions for setting up the dev environment - Optional: Docker and Electron packaging steps Use best practices, clean code, and comments throughout. Maintain high performance, low memory footprint, and real-time terminal responsiveness. All results should be local-first with optional cloud sync features.