introduce different improvements

Author: blefnk

.cursor/rules/comments.mdc

@@ -4,18 +4,17 @@ globs:
 alwaysApply: true
 ---
 
-
 # how and when to write comments (llm rules)
 
 ## guiding principles
-1.  **minimize comments:** code should be self-explanatory; comment only when necessary.
-2.  **clarity through naming:** use clear, descriptive names for variables, functions, classes, and components.
+1.  **minimize comments:** code should be self-explanatory; comment only when needed.
+2.  **clarity through naming:** use clear, descriptive names for variables, functions, classes, components.
 3.  **comment the "why," not the "what":** explain *why* an approach was taken, especially for non-obvious logic or trade-offs. don't restate what the code does.
 4.  **avoid obvious comments:** don't comment on simple or standard code; assume the reader knows language basics.
-5.  **consistency:** use a consistent style for comments and documentation across the codebase.
+5.  **consistency:** keep comment and doc style consistent across the codebase.
 
 ## when to add comments
-*   **complex logic:** for algorithms or flows not immediately clear from code.
+*   **complex logic:** for algorithms or flows not clear from code.
 *   **non-obvious decisions (the "why"):** explain reasoning behind design choices, workarounds, or optimizations, especially if nonstandard or counterintuitive.
 *   **business rules/context:** briefly note domain-specific rules or context driving code.
 *   **security/performance notes:** note important security or performance implications if not obvious.
@@ -36,15 +35,16 @@ alwaysApply: true
 *   **outdated comments:** remove or update comments that no longer match the code.
 
 ## humor, tone, and informality
-*   **full informal freedom:** feel free to use informal, conversational, or humorous language in comments and documentation—just like a real, quirky senior developer. puns, memes, pop culture references, and playful banter are all fair game, as long as it's not offensive or unprofessional. if a joke helps make a point or keeps things lively, go for it!
+*   **full informal freedom:** use informal, conversational, or humorous language in comments and docs—just like a real, quirky senior dev. puns, memes, pop culture, playful banter are all fair game, as long as it's not offensive or unprofessional. if a joke helps make a point or keeps things lively, go for it!
 *   **be yourself:** comments can have personality. if you want to drop a "don't touch this unless you like pain", that's totally fine.
-*   **clarity first:** even with informality, make sure the comment's intent is clear, helpful to both code beginners and seniors.
+*   **clarity first:** even with informality, make sure the comment's intent is clear and helpful to both beginners and seniors.
 
 ## lowercase comment style
-*   **all comments must be written in lowercase, even at the beginning of sentences.** the only exception is for code identifiers (like function or variable names), which should retain their original casing.
+*   **all comments must be written in lowercase, even at the beginning of sentences.** the only exception is for code identifiers (like function or variable names), which should keep their original casing.
 
 ## important
 *   when asked to "clean up" comments, don't add new comments explaining what was removed or which functions/variables were renamed. the user uses cursor ide, which shows diffs. explain important changes in your message, not in code comments.
+*   remember: these rules apply only to comments, e.g. `// ` `/** */` `{/* */}`. do not apply these rules to end-user content, e.g. frontend text.
 
-by following these rules, the codebase stays clean, readable, and maintainable—while also being a little more fun and human.
+by following these rules, the codebase stays clean, readable, maintainable—and a little more fun and human.
 

.cursor/rules/drizzle-orm.mdc

@@ -0,0 +1,29 @@
+---
+description: Read this rule when working with Drizzle ORM
+globs: 
+alwaysApply: false
+---
+
+# how to work with drizzle orm (ai rules)
+
+## debugging: `typeerror: cannot read properties of undefined (reading 'referencedtable')`
+
+this error happens when drizzle can't find relationship metadata for a relational query (e.g., `db.query.someTable.findMany({ with: { relatedTable: true } })`).
+
+**checklist:**
+
+1.  **missing `relations` definition:**  
+    *   define a `relations` object for the source table (e.g., `userRelations = relations(userTable, ({ many }) => ({ uploads: many(uploadsTable) }))`).  
+    *   `.references()` only sets up the db foreign key; it doesn't create drizzle's relation for queries.
+2.  **relations not exported:**  
+    *   export all `relations` objects from schema files.  
+    *   ensure your schema barrel file (e.g., `src/db/schema/index.ts`) exports all tables and relations.
+3.  **wrong schema passed to drizzle:**  
+    *   when initializing, pass a schema object with both tables and relations:  
+        `import * as schema from './schema';`  
+        `const db = drizzle(conn, { schema });`
+4.  **build issues:**  
+    *   in monorepos or complex setups, make sure all schema/relation files are included in the build.
+5.  **multiple drizzle instances:**  
+    *   use a single shared drizzle client (e.g., export `db` from `src/db/index.ts`).
+

.cursor/rules/general-rules.mdc

@@ -3,6 +3,8 @@ description:
 globs: 
 alwaysApply: true
 ---
-## General Rules
-- You are a code agent. Always make changes without asking if the user wants you to make them. Unless the user explicitly asks you not to make changes.
+
+
+## general rules
+- you are a code agent. always make changes without asking if the user wants you to make them. unless the user explicitly asks you not to make changes.
 

.cursor/rules/orm-drizzle.mdc

@@ -4,33 +4,33 @@ globs:
 alwaysApply: false
 ---
 
+# how to work with uploadthing (llm guide)
 
-# How to Work with Uploadthing (LLM Guide)
+## key files
 
-## Key Files
+- config: `core.ts` (upload routes, middleware, db)
+- api handler: `route.ts` (webhook/callback)
+- db schema: `tables.ts` (`uploads` table, `type` enum)
+- db types: `types.ts` (`MediaUpload`)
+- frontend ui: `page.client.tsx` (`UploadButton`)
+- media api: `/api/media/route.ts` (fetch media)
+- display: `bento-media-gallery.tsx` (renders images/videos)
+- auth: `~/lib/auth`
 
-- **Config:** `core.ts` (upload routes, middleware, db)
-- **API Handler:** `route.ts` (webhook/callback)
-- **DB Schema:** `tables.ts` (`uploads` table, `media_type` enum)
-- **DB Types:** `types.ts` (`MediaUpload`)
-- **Frontend UI:** `page.client.tsx` (`UploadButton`)
-- **Media API:** `/api/media/route.ts` (fetch media)
-- **Display:** `bento-media-gallery.tsx` (renders images/videos)
-- **Auth:** `~/lib/auth`
+## core concepts
 
-## Core Concepts
+- routes: defined in `core.ts` with `createUploadthing()`. each route (e.g., `imageUploader`, `videoUploader`) sets allowed types, size, count.
+- auth: middleware in `core.ts` uses `auth.api.getSession` to check user; throws if unauthorized.
+- db insert: `onUploadComplete` inserts into `uploads` table, sets `type` based on route, uses `createId()` for `id`.
+- frontend: `UploadButton` for each endpoint; `onClientUploadComplete` refetches media via `/api/media`.
+- media fetch: `/api/media/route.ts` authenticates, fetches uploads for user, returns json.
+- display: `bento-media-gallery.tsx` renders `<img>` or `<video>` based on `type`.
 
-- **Routes:** Defined in `core.ts` with `createUploadthing()`. Each route (e.g., `imageUploader`, `videoUploader`) sets allowed types, size, count.
-- **Auth:** Middleware in `core.ts` uses `auth.api.getSession` to check user; throws if unauthorized.
-- **DB Insert:** `onUploadComplete` inserts into `uploads` table, sets `type` based on route, uses `createId()` for `id`.
-- **Frontend:** `UploadButton` for each endpoint; `onClientUploadComplete` refetches media via `/api/media`.
-- **Media Fetch:** `/api/media/route.ts` authenticates, fetches uploads for user, returns JSON.
-- **Display:** `bento-media-gallery.tsx` renders `<img>` or `<video>` based on `type`.
+## tips
 
-## Tips
+- check `core.ts` for routes, middleware, and upload logic.
+- set `type` in `onUploadComplete` based on route.
+- adding new media types: update `core.ts`, `tables.ts` enum, run migrations, add `UploadButton`, update display and api as needed.
+- media fetch requires auth.
+- error handling: `onUploadComplete` logs/throws; production may need more.
 
-- **Check `core.ts`** for routes, middleware, and upload logic.
-- **Set `type`** in `onUploadComplete` based on route.
-- **Adding new media types:** update `core.ts`, `tables.ts` enum, run migrations, add `UploadButton`, update display and API as needed.
-- **Media fetch requires auth.**
-- **Error handling:** `onUploadComplete` logs/throws; production may need more.

.cursor/rules/uploadthing.mdc

@@ -1,36 +1,63 @@
-# ============================================
 # 📖 https://docs.reliverse.org/relivator/env
-# ============================================
 
-# Metadata
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― APP ―――――――――――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+
+# use https://example.com in production
 NEXT_PUBLIC_APP_URL="http://localhost:3000"
 NEXT_SERVER_APP_URL="http://localhost:3000"
 
-# Database
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― DATABASE ――――――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+
 # https://console.neon.tech/app/projects
-DATABASE_URL="postgresql://postgres:password@localhost:5432/db"
+DATABASE_URL="postgresql://..."
 
-# Authentication
-# bunx randomstring length=32
-AUTH_SECRET="your-auth-secret-key-at-least-32-chars"
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― AUTHENTICATION ――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
 
-# https://github.com/settings/developers
-# https://example.com/api/auth/callback/github
-AUTH_GITHUB_ID="your-github-client-id"
-AUTH_GITHUB_SECRET="your-github-client-secret"
+# bunx randomstring length=32
+AUTH_SECRET="..."
 
 # https://console.cloud.google.com/apis/credentials
 # Create credentials > OAuth client ID
 # Authorized JavaScript origins: https://example.com && http://localhost:3000
 # Authorized redirect URIs: https://example.com/api/auth/callback/google && http://localhost:3000/api/auth/callback/google
-AUTH_GOOGLE_ID="your-google-client-id"
-AUTH_GOOGLE_SECRET="your-google-client-secret"
+AUTH_GOOGLE_ID="..."
+AUTH_GOOGLE_SECRET="..."
+
+# https://github.com/settings/developers
+# https://example.com/api/auth/callback/github
+AUTH_GITHUB_ID="..."
+AUTH_GITHUB_SECRET="..."
+
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― UPLOADS ―――――――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
 
 # https://uploadthing.com/dashboard
-UPLOADTHING_TOKEN=""
-UPLOADTHING_SECRET_KEY="sk_live_"
+UPLOADTHING_TOKEN="..."
+UPLOADTHING_SECRET_KEY="sk_live_..."
+
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― PAYMENTS ――――――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+
+# 🔜
+
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― EMAILS ――――――――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+
+# 🔜
+
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
+# ―― INSTRUCTIONS ――――――――――――――――――――――――――
+# ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
 
-# Instructions:
 # 1. Copy .env.example file to .env
 # 2. Replace the values with your own credentials
 # 3. Restart your development server if it's running

.env.example

@@ -1,10 +1,14 @@
-tsconfig.tsbuildinfo
 /auth-schema.ts
 /node_modules
 next-env.d.ts
+*.tsbuildinfo
 .eslintcache
+.DS_Store
 .vercel
+*.log*
+.venv
+.idea
 .next
-.env
 .exe
 .dll
+.env

.eslintcache

@@ -5,6 +5,7 @@
     "biomejs.biome",
     "dbaeumer.vscode-eslint",
     "chunsen.bracket-select",
-    "davidanson.vscode-markdownlint"
+    "davidanson.vscode-markdownlint",
+    "yzhang.markdown-all-in-one"
   ]
 }