This file provides foundational context and instructions for Gemini CLI when working in the `kit-ui` workspace.
## 🚀 Project Overview
**Kit UI** is a high-performance, aesthetically pleasing toolkit built with **Next.js 16**, **React 19**, and **Tailwind CSS 4**. It provides four core specialized applications:
1.**Tailwind 4**: Use the new CSS-first approach. Avoid `tailwind.config.js`. Define theme variables and utilities in `app/globals.css`.
2.**Glassmorphism**: Use the `@utility glass` for translucent components.
3.**WASM Orchestration**: Heavy processing should stay in `lib/[tool]/` and utilize WASM where possible. Refer to `lib/media/wasm/wasmLoader.ts` for pattern-loading FFmpeg/ImageMagick.
4.**Client-Side Only**: Since this is a static export toolkit that relies on browser APIs (WASM, File API), ensure components using these are marked with `'use client'`.
5.**Icons**: Exclusively use `lucide-react`.
## 🧠 Strategic Instructions for Gemini
- **Surgical Updates**: When modifying tools, ensure the logic remains in `lib/` and the UI in `components/`.
- **WASM Handling**: Do not attempt to run WASM-dependent logic in the terminal/Node environment unless specifically configured. These tools are designed for the browser.
- **Styling**: Adhere to the `glass` and gradient utilities (`gradient-purple-blue`, etc.) defined in `app/globals.css`.
- **Component Consistency**: Use shadcn components from `components/ui/` as the building blocks for new features.