clean up pair programming

.cursor/mcp.json

@@ -2,16 +2,23 @@
   "mcpServers": {
     "shadcn-ui-server": {
       "command": "npx",
-      "args": ["-y", "shadcn-ui-mcp-server"]
+      "args": [
+        "-y",
+        "shadcn-ui-mcp-server"
+      ]
     },
     "plate": {
       "description": "Plate editors, plugins, components, and docs",
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "shadcn@canary", "registry:mcp"],
+      "args": [
+        "-y",
+        "shadcn@canary",
+        "registry:mcp"
+      ],
       "env": {
         "REGISTRY_URL": "https://platejs.org/r/registry.json"
       }
     }
   }
-}
+}

.cursor/rules/data-management.mdc

@@ -1,6 +1,6 @@
 ---
 description: Interaction with the database.
-globs: **/*.{js,jsx,ts,tsx}
+globs: **/*{.js,.jsx,.ts,.tsx}
 alwaysApply: false
 ---
 - Interact with the database exclusively using Prisma ORM client

.cursor/rules/error-handling.mdc

@@ -1,6 +1,6 @@
 ---
 description: Enfore friendly and logical error handling.
-globs: **/*.{js,jsx,ts,tsx}
+globs: **/*{.js,.jsx,.ts,.tsx}
 ---
 - Implement robust error handling and logging mechanisms.
 - Implement robust error handling using the established `ServerActionResult<T>` pattern

.cursor/rules/general-principles.mdc

@@ -3,7 +3,6 @@ description: Applies general principles across the project.
 globs: */**
 ---
 - You are an expert in TypeScript, Node.js, Next.js with the app router, React, shadcn/ui, Tailwind, Auth.js and Prisma.
-- You are an expert in TypeScript, Node.js, Next.js (App Router), React, Shadcn/UI, Tailwind, and Prisma
 - Write clean, concise and well-commented TypeScript code
 - Favor functional and declarative programming patterns over object-oriented approaches
 - Prioritize code reuse and modularization over duplication

.cursor/rules/media-handling.mdc

@@ -5,8 +5,8 @@ alwaysApply: false
 ---
 ## Media Handling Guidelines
 
-- Use UploadThing for all file upload operations
-- Follow the established patterns in `lib/uploadthing.ts` and `hooks/use-upload-file.ts`
+- Use Supabase Storage for all file upload operations
+- Follow the established patterns in `lib/supabase/storage.ts` and `hooks/use-upload-file.ts`
 - Implement proper file validation (type, size, format)
 - Use the established image processing utilities in `lib/imaging/`
 - Handle upload errors gracefully with appropriate user feedback

.cursor/rules/naming-conventions.mdc

@@ -2,7 +2,6 @@
 description: Enforces a consistent naming convention across the project.
 globs: */**
 ---
-- Use PascalCase for class names and type definitions.
 - Use PascalCase for React components and type definitions
 - Utilize camelCase for variables, functions and methods
 - Employ kebab-case for file and directory names

.cursor/rules/nextjs.mdc

@@ -1,7 +1,8 @@
 ---
 description: Applies optimal Next.js rules and best practices.
-globs: **/*.{js,jsx,ts,tsx}
+globs: **/*{.js,.jsx,.ts,.tsx}
 ---
+
 - Favor React Server Components (RSC) where possible.
 - Minimize `'use client'` directives - only use for interactivity.
 - Optimize for performance and Web Vitals.