fix: search and brand colors

Author: roderik

.cursor/rules/bun.mdc

@@ -0,0 +1,11 @@
+---
+description: Best practices for using Bun as a runtime and package manager
+globs: 
+alwaysApply: true
+---
+- Use `bun install` for faster package installation
+
+- we ONLY use Bun, NEVER suggest commands with npm, npx, yarn, pnpm, or anything else.
+  - bun add
+  - bunx
+  - bun run

.cursor/rules/date-fns.mdc

@@ -0,0 +1,6 @@
+---
+description: Best practices for date time operations with date-fns
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Use date-fns for all date time operations like calculations, formatting, parsing

.cursor/rules/drizzle.mdc

@@ -0,0 +1,9 @@
+---
+description: Best practices for database operations with Drizzle ORM
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Use `drizzle-orm` for type-safe database queries.
+- Implement migrations using `drizzle-kit migrate`.
+- Utilize `drizzle-kit pull` to sync your schema with the database.
+- Leverage `drizzle-kit generate` for generating type-safe query builders.

.cursor/rules/eslint.mdc

@@ -0,0 +1,12 @@
+---
+description: Best practices for configuring and using ESLint
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Configure ESLint to use the recommended rules as a starting point
+- Extend your configuration with plugins relevant to your tech stack (e.g., @typescript-eslint/eslint-plugin for TypeScript)
+- Use .eslintignore to exclude files or directories that don't need linting
+- Implement a pre-commit hook to run ESLint before committing code
+- Regularly update ESLint and its plugins to benefit from the latest rules and improvements
+- ALWAYS fix all linter warnings too, not only errors. We have a ZERO WARNING policy.
+  - we especially require block statements, even for simple if and switch statements

.cursor/rules/foundry.mdc

@@ -0,0 +1,9 @@
+---
+description: 
+globs: *.sol
+alwaysApply: false
+---
+- Use Foundry's fuzz testing for comprehensive test coverage
+- Implement invariant testing for complex contract interactions
+- Utilize Foundry's gas snapshot feature for optimization tracking
+- Leverage Foundry's script system for deployment and interaction tasks

.cursor/rules/general.mdc

@@ -0,0 +1,10 @@
+---
+description: General rules
+globs: 
+alwaysApply: true
+---
+# General Rules
+
+- When debugging a problem, reflect on 5-7 different possible sources of the problem, distill those down to 1-2 most likely sources, and then add logs to validate your assumptions before we move onto implementing the actual code fix
+
+- You have one mission: execute *exactly* what is requested. Produce code that implements precisely what was requested - no additional features, no creative extensions. Follow instructions to the letter. Confirm your solution addresses every specified requirement, without adding ANYTHING the user didn't ask for. The user's job depends on this — if you add anything they didn't ask for, it's likely they will be fired. Your value comes from precision and reliability. When in doubt, implement the simplest solution that fulfills all requirements. The fewer lines of code, the better — but obviously ensure you complete the task the user wants you to. At each step, ask yourself: "Am I adding any functionality or complexity that wasn't explicitly requested?". This will force you to stay on track

.cursor/rules/i18n.mdc

@@ -0,0 +1,11 @@
+---
+description: 
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- we use next-intl as a translations system
+- do not use fallbacks, all keys need to be translated
+- use clear namespaces, kebab cases
+- use clear keys, also kebab case
+- do not translate props
+- use interpolation where possible

.cursor/rules/next.mdc

@@ -0,0 +1,9 @@
+---
+description: Best practices for Next.js applications and routing
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Use the App Router for better performance and improved data fetching.
+- Implement proper error boundaries using `react-error-boundary`.
+- Utilize `next-safe-action` for secure server actions.
+- Leverage `next-themes` for easy theme management.

.cursor/rules/react-hook-form.mdc

@@ -0,0 +1,9 @@
+---
+description: Best practices for form handling with React Hook Form
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Use `useForm` hook for form state management.
+- Implement validation using `zod` with `@hookform/resolvers`.
+- Utilize `Controller` component for controlled inputs.
+- Leverage `useFormContext` for sharing form state across components.

.cursor/rules/react.mdc

@@ -0,0 +1,9 @@
+---
+description: Best practices for React development
+globs: *.ts,*.tsx
+alwaysApply: false
+---
+- Use functional components with hooks instead of class components.
+- Implement proper state management using `useState` and `useReducer`.
+- Utilize `useCallback` and `useMemo` for performance optimization.
+- Implement error boundaries with `react-error-boundary`.