docs: update code quality and frontend rules for Vite cache management and icon usage

- Added guidelines for clearing Vite cache after updating npm packages
- Emphasized the use of Redis UI icons and provided instructions for icon usage and exceptions for custom icons

Author: valkirilov

.ai/rules/code-quality.md

@@ -64,6 +64,21 @@ alwaysApply: true
 - Clean up subscriptions and timers
 - Use constants instead of magic numbers
 
+## Vite Cache Management
+
+When updating npm packages (especially `@redis-ui/*` packages):
+
+1. **Clear Vite cache** after `yarn install`:
+
+   ```bash
+   rm -rf node_modules/.vite
+   rm -rf redisinsight/ui/node_modules/.vite
+   ```
+
+2. **Restart dev server** to rebuild dependencies
+
+3. This ensures new package versions are properly loaded
+
 ## Pre-Commit Checklist
 
 - [ ] `yarn lint` passes
@@ -75,3 +90,4 @@ alwaysApply: true
 - [ ] Descriptive variable names
 - [ ] Low cognitive complexity
 - [ ] No duplicate code
+- [ ] Vite cache cleared (if updated dependencies)

.ai/rules/frontend.md

@@ -270,6 +270,24 @@ import { EuiButton } from '@elastic/eui';
 - ❌ Do not import directly from `@redis-ui/*`
 - ❌ Do not add new Elastic UI imports
 
+## Icons
+
+**⚠️ IMPORTANT**: Always use icons from Redis UI library instead of custom SVGs.
+
+### Icon Usage
+
+- **Use Redis UI icons** from `@redis-ui/icons` via `iconRegistry.tsx`
+- Icons are automatically exported via `export * from '@redis-ui/icons'` in `iconRegistry.tsx`
+- Use `RiIcon` component with icon type: `<RiIcon type="FolderOpenIcon" />`
+- **DO NOT create custom SVG icons** - check if the icon exists in Redis UI library first
+
+### Custom Icons (Exception)
+
+Only create custom SVG icons if:
+
+- The icon doesn't exist in Redis UI library
+- It's a project-specific icon that won't be added to the library
+
 ## Testing Components
 
 ### Always Use Shared `renderComponent` Helper