OpenCut-app
diff --git a/‎.cursor/rules/ultracite.mdc‎
Lines changed: 14 additions & 1 deletion b/‎.cursor/rules/ultracite.mdc‎
Lines changed: 14 additions & 1 deletion
@@ -5,15 +5,18 @@ alwaysApply: true
 ---
 
 # Project Context
+
 Ultracite enforces strict type safety, accessibility standards, and consistent code quality for JavaScript/TypeScript projects using Biome's lightning-fast formatter and linter.
 
 ## Key Principles
+
 - Zero configuration required
 - Subsecond performance
 - Maximum type safety
 - AI-friendly code generation
 
 ## Before Writing Code
+
 1. Analyze existing patterns in the codebase
 2. Consider edge cases and error scenarios
 3. Follow the rules below strictly
@@ -23,45 +26,53 @@ Ultracite enforces strict type safety, accessibility standards, and consistent c
 ## Rules
 
 ### Accessibility (a11y)
+
 - Always include a `title` element for icons unless there's text beside the icon.
 - Always include a `type` attribute for button elements.
 - Accompany `onClick` with at least one of: `onKeyUp`, `onKeyDown`, or `onKeyPress`.
 - Accompany `onMouseOver`/`onMouseOut` with `onFocus`/`onBlur`.
 
 ### Code Complexity and Quality
+
 - Don't use primitive type aliases or misleading types.
 - Don't use the comma operator.
 - Use for...of statements instead of Array.forEach.
 - Don't initialize variables to undefined.
 - Use .flatMap() instead of map().flat() when possible.
 
 ### React and JSX Best Practices
+
 - Don't import `React` itself.
 - Don't define React components inside other components.
 - Don't use both `children` and `dangerouslySetInnerHTML` props on the same element.
 - Don't insert comments as text nodes.
 - Use `<>...</>` instead of `<Fragment>...</Fragment>`.
 
 ### Function Parameters and Props
+
 - Always use destructured props objects instead of individual parameters in functions.
 - Example: `function helloWorld({ prop }: { prop: string })` instead of `function helloWorld(param: string)`.
 - This applies to all functions, not just React components.
 
 ### Correctness and Safety
+
 - Don't assign a value to itself.
 - Avoid unused imports and variables.
 - Don't use await inside loops.
 - Don't hardcode sensitive data like API keys and tokens.
 - Don't use the TypeScript directive @ts-ignore.
 - Make sure the `preconnect` attribute is used when using Google Fonts.
 - Don't use the `delete` operator.
+- Don't use `require()` in TypeScript/ES modules - use proper `import` statements.
 
 ### TypeScript Best Practices
+
 - Don't use TypeScript enums.
 - Use either `T[]` or `Array<T>` consistently.
 - Don't use the `any` type.
 
 ### Style and Consistency
+
 - Don't use global `eval()`.
 - Use `String.slice()` instead of `String.substr()` and `String.substring()`.
 - Don't use `else` blocks when the `if` block breaks early.
@@ -70,17 +81,19 @@ Ultracite enforces strict type safety, accessibility standards, and consistent c
 - Use `String.trimStart()` and `String.trimEnd()` over `String.trimLeft()` and `String.trimRight()`.
 
 ### Next.js Specific Rules
+
 - Don't use `<img>` elements in Next.js projects.
 - Don't use `<head>` elements in Next.js projects.
 
 ## Example: Error Handling
+
 ```typescript
 // ✅ Good: Comprehensive error handling
 try {
   const result = await fetchData();
   return { success: true, data: result };
 } catch (error) {
-  console.error('API call failed:', error);
+  console.error("API call failed:", error);
   return { success: false, error: error.message };
 }