vibefast-cli 0.7.0 → 0.7.1

package/2/vf-agent/data/knowledge_base/backend/full-guidelines.md

@@ -1,795 +0,0 @@
----
-description: whenever you have to do anything related to convex, you can use it.
-globs:
-alwaysApply: false
----
-
-these are convex db rules for react with convex, keep them as detailed and everytghign convex related same just change the react bits to react native expo stuff.
-
-# Convex guidelines
-
-> All `convex/...` paths below are relative to the monorepo package at `packages/backend/convex/`.
-
-## Function guidelines
-
-### New function syntax
-
-- ALWAYS use the new function syntax for Convex functions. For example:
-  `typescript
-    import { query } from "./_generated/server";
-    import { v } from "convex/values";
-    export const f = query({
-        args: {},
-        returns: v.null(),
-        handler: async (ctx, args) => {
-        // Function body
-        },
-    });
-    `
-
-### Http endpoint syntax
-
-- HTTP endpoints are defined in `convex/http.ts` and require an `httpAction` decorator. For example:
-  `typescript
-    import { httpRouter } from "convex/server";
-    import { httpAction } from "./_generated/server";
-    const http = httpRouter();
-    http.route({
-        path: "/echo",
-        method: "POST",
-        handler: httpAction(async (ctx, req) => {
-        const body = await req.bytes();
-        return new Response(body, { status: 200 });
-        }),
-    });
-    `
-- HTTP endpoints are always registered at the exact path you specify in the `path` field. For example, if you specify `/api/someRoute`, the endpoint will be registered at `/api/someRoute`.
-
-### Validators
-
-- Below is an example of an array validator:
-  ```typescript
-  import { mutation } from "./\_generated/server";
-  import { v } from "convex/values";
-
-                            export default mutation({
-                            args: {
-                                simpleArray: v.array(v.union(v.string(), v.number())),
-                            },
-                            handler: async (ctx, args) => {
-                                //...
-                            },
-                            });
-                            ```
-
-- Below is an example of a schema with validators that codify a discriminated union type:
-  ```typescript
-  import { defineSchema, defineTable } from "convex/server";
-  import { v } from "convex/values";
-
-                            export default defineSchema({
-                                results: defineTable(
-                                    v.union(
-                                        v.object({
-                                            kind: v.literal("error"),
-                                            errorMessage: v.string(),
-                                        }),
-                                        v.object({
-                                            kind: v.literal("success"),
-                                            value: v.number(),
-                                        }),
-                                    ),
-                                )
-                            });
-                            ```
-
-- Always use the `v.null()` validator when returning a null value. Below is an example query that returns a null value:
-  ```typescript
-  import { query } from "./\_generated/server";
-  import { v } from "convex/values";
-
-                                  export const exampleQuery = query({
-                                    args: {},
-                                    returns: v.null(),
-                                    handler: async (ctx, args) => {
-                                        console.log("This query returns a null value");
-                                        return null;
-                                    },
-                                  });
-                                  ```
-
-- Here are the valid Convex types along with their respective validators:
-  Convex Type | TS/JS type | Example Usage | Validator for argument validation and schemas | Notes |
-  | ----------- | ------------| -----------------------| -----------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-  | Id | string | `doc._id` | `v.id(tableName)` | |
-  | Null | null | `null` | `v.null()` | JavaScript's `undefined` is not a valid Convex value. Functions the return `undefined` or do not return will return `null` when called from a client. Use `null` instead. |
-  | Int64 | bigint | `3n` | `v.int64()` | Int64s only support BigInts between -2^63 and 2^63-1. Convex supports `bigint`s in most modern browsers. |
-  | Float64 | number | `3.1` | `v.number()` | Convex supports all IEEE-754 double-precision floating point numbers (such as NaNs). Inf and NaN are JSON serialized as strings. |
-  | Boolean | boolean | `true` | `v.boolean()` |
-  | String | string | `"abc"` | `v.string()` | Strings are stored as UTF-8 and must be valid Unicode sequences. Strings must be smaller than the 1MB total size limit when encoded as UTF-8. |
-  | Bytes | ArrayBuffer | `new ArrayBuffer(8)` | `v.bytes()` | Convex supports first class bytestrings, passed in as `ArrayBuffer`s. Bytestrings must be smaller than the 1MB total size limit for Convex types. |
-  | Array | Array] | `[1, 3.2, "abc"]` | `v.array(values)` | Arrays can have at most 8192 values. |
-  | Object | Object | `{a: "abc"}` | `v.object({property: value})` | Convex only supports "plain old JavaScript objects" (objects that do not have a custom prototype). Objects can have at most 1024 entries. Field names must be nonempty and not start with "$" or "_". |
-| Record      | Record      | `{"a": "1", "b": "2"}` | `v.record(keys, values)`                       | Records are objects at runtime, but can have dynamic keys. Keys must be only ASCII characters, nonempty, and not start with "$" or "\_". |
-
-### Function registration
-
-- Use `internalQuery`, `internalMutation`, and `internalAction` to register internal functions. These functions are private and aren't part of an app's API. They can only be called by other Convex functions. These functions are always imported from `./_generated/server`.
-- Use `query`, `mutation`, and `action` to register public functions. These functions are part of the public API and are exposed to the public Internet. Do NOT use `query`, `mutation`, or `action` to register sensitive internal functions that should be kept private.
-- You CANNOT register a function through the `api` or `internal` objects.
-- ALWAYS include argument and return validators for all Convex functions. This includes all of `query`, `internalQuery`, `mutation`, `internalMutation`, `action`, and `internalAction`. If a function doesn't return anything, include `returns: v.null()` as its output validator.
-- If the JavaScript implementation of a Convex function doesn't have a return value, it implicitly returns `null`.
-
-### Function calling
-
-- Use `ctx.runQuery` to call a query from a query, mutation, or action.
-- Use `ctx.runMutation` to call a mutation from a mutation or action.
-- Use `ctx.runAction` to call an action from an action.
-- ONLY call an action from another action if you need to cross runtimes (e.g. from V8 to Node). Otherwise, pull out the shared code into a helper async function and call that directly instead.
-- Try to use as few calls from actions to queries and mutations as possible. Queries and mutations are transactions, so splitting logic up into multiple calls introduces the risk of race conditions.
-- All of these calls take in a `FunctionReference`. Do NOT try to pass the callee function directly into one of these calls.
-- When using `ctx.runQuery`, `ctx.runMutation`, or `ctx.runAction` to call a function in the same file, specify a type annotation on the return value to work around TypeScript circularity limitations. For example,
-  ```
-  export const f = query({
-  args: { name: v.string() },
-  returns: v.string(),
-  handler: async (ctx, args) => {
-  return "Hello " + args.name;
-  },
-  });
-
-                            export const g = query({
-                              args: {},
-                              returns: v.null(),
-                              handler: async (ctx, args) => {
-                                const result: string = await ctx.runQuery(api.example.f, { name: "Bob" });
-                                return null;
-                              },
-                            });
-                            ```
-
-### Function references
-
-- Function references are pointers to registered Convex functions.
-- Use the `api` object defined by the framework in `convex/_generated/api.ts` to call public functions registered with `query`, `mutation`, or `action`.
-- Use the `internal` object defined by the framework in `convex/_generated/api.ts` to call internal (or private) functions registered with `internalQuery`, `internalMutation`, or `internalAction`.
-- Convex uses file-based routing, so a public function defined in `convex/example.ts` named `f` has a function reference of `api.example.f`.
-- A private function defined in `convex/example.ts` named `g` has a function reference of `internal.example.g`.
-- Functions can also registered within directories nested within the `convex/` folder. For example, a public function `h` defined in `convex/messages/access.ts` has a function reference of `api.messages.access.h`.
-
-### Api design
-
-- Convex uses file-based routing, so thoughtfully organize files with public query, mutation, or action functions within the `convex/` directory.
-- Use `query`, `mutation`, and `action` to define public functions.
-- Use `internalQuery`, `internalMutation`, and `internalAction` to define private, internal functions.
-
-### Pagination
-
-- Paginated queries are queries that return a list of results in incremental pages.
-- You can define pagination using the following syntax:
-
-                            ```ts
-                            import { v } from "convex/values";
-                            import { query, mutation } from "./_generated/server";
-                            import { paginationOptsValidator } from "convex/server";
-                            export const listWithExtraArg = query({
-                                args: { paginationOpts: paginationOptsValidator, author: v.string() },
-                                handler: async (ctx, args) => {
-                                    return await ctx.db
-                                    .query("messages")
-                                    .filter((q) => q.eq(q.field("author"), args.author))
-                                    .order("desc")
-                                    .paginate(args.paginationOpts);
-                                },
-                            });
-                            ```
-                            Note: `paginationOpts` is an object with the following properties:
-                            - `numItems`: the maximum number of documents to return (the validator is `v.number()`)
-                            - `cursor`: the cursor to use to fetch the next page of documents (the validator is `v.union(v.string(), v.null())`)
-
-- A query that ends in `.paginate()` returns an object that has the following properties: - page (contains an array of documents that you fetches) - isDone (a boolean that represents whether or not this is the last page of documents) - continueCursor (a string that represents the cursor to use to fetch the next page of documents)
-
-## Validator guidelines
-
-- `v.bigint()` is deprecated for representing signed 64-bit integers. Use `v.int64()` instead.
-- Use `v.record()` for defining a record type. `v.map()` and `v.set()` are not supported.
-
-## Schema guidelines
-
-- Always define your schema in `convex/schema.ts`.
-- Always import the schema definition functions from `convex/server`:
-- System fields are automatically added to all documents and are prefixed with an underscore. The two system fields that are automatically added to all documents are `_creationTime` which has the validator `v.number()` and `_id` which has the validator `v.id(tableName)`.
-- Always include all index fields in the index name. For example, if an index is defined as `["field1", "field2"]`, the index name should be "by_field1_and_field2".
-- Index fields must be queried in the same order they are defined. If you want to be able to query by "field1" then "field2" and by "field2" then "field1", you must create separate indexes.
-
-## Typescript guidelines
-
-- You can use the helper typescript type `Id` imported from './\_generated/dataModel' to get the type of the id for a given table. For example if there is a table called 'users' you can use `Id<'users'>` to get the type of the id for that table.
-- If you need to define a `Record` make sure that you correctly provide the type of the key and value in the type. For example a validator `v.record(v.id('users'), v.string())` would have the type `Record<Id<'users'>, string>`. Below is an example of using `Record` with an `Id` type in a query:
-  ```ts
-  import { query } from "./\_generated/server";
-  import { Doc, Id } from "./\_generated/dataModel";
-
-                    export const exampleQuery = query({
-                        args: { userIds: v.array(v.id("users")) },
-                        returns: v.record(v.id("users"), v.string()),
-                        handler: async (ctx, args) => {
-                            const idToUsername: Record<Id<"users">, string> = {};
-                            for (const userId of args.userIds) {
-                                const user = await ctx.db.get(userId);
-                                if (user) {
-                                    users[user._id] = user.username;
-                                }
-                            }
-
-                            return idToUsername;
-                        },
-                    });
-                    ```
-
-- Be strict with types, particularly around id's of documents. For example, if a function takes in an id for a document in the 'users' table, take in `Id<'users'>` rather than `string`.
-- Always use `as const` for string literals in discriminated union types.
-- When using the `Array` type, make sure to always define your arrays as `const array: Array<T> = [...];`
-- When using the `Record` type, make sure to always define your records as `const record: Record<KeyType, ValueType> = {...};`
-- Always add `@types/node` to your `package.json` when using any Node.js built-in modules.
-
-## Full text search guidelines
-
-- A query for "10 messages in channel '#general' that best match the query 'hello hi' in their body" would look like:
-
-const messages = await ctx.db
-.query("messages")
-.withSearchIndex("search_body", (q) =>
-q.search("body", "hello hi").eq("channel", "#general"),
-)
-.take(10);
-
-## Query guidelines
-
-- Do NOT use `filter` in queries. Instead, define an index in the schema and use `withIndex` instead.
-- Convex queries do NOT support `.delete()`. Instead, `.collect()` the results, iterate over them, and call `ctx.db.delete(row._id)` on each result.
-- Use `.unique()` to get a single document from a query. This method will throw an error if there are multiple documents that match the query.
-- When using async iteration, don't use `.collect()` or `.take(n)` on the result of a query. Instead, use the `for await (const row of query)` syntax.
-
-### Ordering
-
-- By default Convex always returns documents in ascending `_creationTime` order.
-- You can use `.order('asc')` or `.order('desc')` to pick whether a query is in ascending or descending order. If the order isn't specified, it defaults to ascending.
-- Document queries that use indexes will be ordered based on the columns in the index and can avoid slow table scans.
-
-## Mutation guidelines
-
-- Use `ctx.db.replace` to fully replace an existing document. This method will throw an error if the document does not exist.
-- Use `ctx.db.patch` to shallow merge updates into an existing document. This method will throw an error if the document does not exist.
-
-## Action guidelines
-
-- Always add `"use node";` to the top of files containing actions that use Node.js built-in modules.
-- Never use `ctx.db` inside of an action. Actions don't have access to the database.
-- Below is an example of the syntax for an action:
-  ```ts
-  import { action } from "./\_generated/server";
-
-                    export const exampleAction = action({
-                        args: {},
-                        returns: v.null(),
-                        handler: async (ctx, args) => {
-                            console.log("This action does not return anything");
-                            return null;
-                        },
-                    });
-                    ```
-
-## Scheduling guidelines
-
-### Cron guidelines
-
-- Only use the `crons.interval` or `crons.cron` methods to schedule cron jobs. Do NOT use the `crons.hourly`, `crons.daily`, or `crons.weekly` helpers.
-- Both cron methods take in a FunctionReference. Do NOT try to pass the function directly into one of these methods.
-- Define crons by declaring the top-level `crons` object, calling some methods on it, and then exporting it as default. For example,
-  ```ts
-  import { cronJobs } from "convex/server";
-  import { internal } from "./\_generated/api";
-  import { internalAction } from "./\_generated/server";
-
-                            const empty = internalAction({
-                              args: {},
-                              returns: v.null(),
-                              handler: async (ctx, args) => {
-                                console.log("empty");
-                              },
-                            });
-
-                            const crons = cronJobs();
-
-                            // Run `internal.crons.empty` every two hours.
-                            crons.interval("delete inactive users", { hours: 2 }, internal.crons.empty, {});
-
-                            export default crons;
-                            ```
-
-- You can register Convex functions within `crons.ts` just like any other file.
-- If a cron calls an internal function, always import the `internal` object from '\_generated/api`, even if the internal function is registered in the same file.
-
-## File storage guidelines
-
-- Convex includes file storage for large files like images, videos, and PDFs.
-- The `ctx.storage.getUrl()` method returns a signed URL for a given file. It returns `null` if the file doesn't exist.
-- Do NOT use the deprecated `ctx.storage.getMetadata` call for loading a file's metadata.
-
-                    Instead, query the `_storage` system table. For example, you can use `ctx.db.system.get` to get an `Id<"_storage">`.
-                    ```
-                    import { query } from "./_generated/server";
-                    import { Id } from "./_generated/dataModel";
-
-                    type FileMetadata = {
-                        _id: Id<"_storage">;
-                        _creationTime: number;
-                        contentType?: string;
-                        sha256: string;
-                        size: number;
-                    }
-
-                    export const exampleQuery = query({
-                        args: { fileId: v.id("_storage") },
-                        returns: v.null();
-                        handler: async (ctx, args) => {
-                            const metadata: FileMetadata | null = await ctx.db.system.get(args.fileId);
-                            console.log(metadata);
-                            return null;
-                        },
-                    });
-                    ```
-
-- Convex storage stores items as `Blob` objects. You must convert all items to/from a `Blob` when using Convex storage.
-
-# Examples:
-
-## Example: chat-app
-
-### Task
-
-```
-Create a real-time chat application backend with AI responses. The app should:
-- Allow creating users with names
-- Support multiple chat channels
-- Enable users to send messages to channels
-- Automatically generate AI responses to user messages
-- Show recent message history
-
-The backend should provide APIs for:
-1. User management (creation)
-2. Channel management (creation)
-3. Message operations (sending, listing)
-4. AI response generation using OpenAI's GPT-4
-
-Messages should be stored with their channel, author, and content. The system should maintain message order
-and limit history display to the 10 most recent messages per channel.
-
-```
-
-### Analysis
-
-1. Task Requirements Summary:
-
-- Build a real-time chat backend with AI integration
-- Support user creation
-- Enable channel-based conversations
-- Store and retrieve messages with proper ordering
-- Generate AI responses automatically
-
-2. Main Components Needed:
-
-- Database tables: users, channels, messages
-- Public APIs for user/channel management
-- Message handling functions
-- Internal AI response generation system
-- Context loading for AI responses
-
-3. Public API and Internal Functions Design:
-   Public Mutations:
-
-- createUser:
-  - file path: convex/index.ts
-  - arguments: {name: v.string()}
-  - returns: v.object({userId: v.id("users")})
-  - purpose: Create a new user with a given name
-- createChannel:
-  - file path: convex/index.ts
-  - arguments: {name: v.string()}
-  - returns: v.object({channelId: v.id("channels")})
-  - purpose: Create a new channel with a given name
-- sendMessage:
-  - file path: convex/index.ts
-  - arguments: {channelId: v.id("channels"), authorId: v.id("users"), content: v.string()}
-  - returns: v.null()
-  - purpose: Send a message to a channel and schedule a response from the AI
-
-Public Queries:
-
-- listMessages:
-  - file path: convex/index.ts
-  - arguments: {channelId: v.id("channels")}
-  - returns: v.array(v.object({
-    \_id: v.id("messages"),
-    \_creationTime: v.number(),
-    channelId: v.id("channels"),
-    authorId: v.optional(v.id("users")),
-    content: v.string(),
-    }))
-  - purpose: List the 10 most recent messages from a channel in descending creation order
-
-Internal Functions:
-
-- generateResponse:
-  - file path: convex/index.ts
-  - arguments: {channelId: v.id("channels")}
-  - returns: v.null()
-  - purpose: Generate a response from the AI for a given channel
-- loadContext:
-  - file path: convex/index.ts
-  - arguments: {channelId: v.id("channels")}
-  - returns: v.array(v.object({
-    \_id: v.id("messages"),
-    \_creationTime: v.number(),
-    channelId: v.id("channels"),
-    authorId: v.optional(v.id("users")),
-    content: v.string(),
-    }))
-- writeAgentResponse:
-  - file path: convex/index.ts
-  - arguments: {channelId: v.id("channels"), content: v.string()}
-  - returns: v.null()
-  - purpose: Write an AI response to a given channel
-
-4. Schema Design:
-
-- users
-  - validator: { name: v.string() }
-  - indexes: <none>
-- channels
-  - validator: { name: v.string() }
-  - indexes: <none>
-- messages
-  - validator: { channelId: v.id("channels"), authorId: v.optional(v.id("users")), content: v.string() }
-  - indexes
-    - by_channel: ["channelId"]
-
-5. Background Processing:
-
-- AI response generation runs asynchronously after each user message
-- Uses OpenAI's GPT-4 to generate contextual responses
-- Maintains conversation context using recent message history
-
-### Implementation
-
-#### package.json
-
-```typescript
-{
-  "name": "chat-app",
-  "description": "This example shows how to build a chat app without authentication.",
-  "version": "1.0.0",
-  "dependencies": {
-    "convex": "^1.17.4",
-    "openai": "^4.79.0"
-  },
-  "devDependencies": {
-    "typescript": "^5.7.3"
-  }
-}
-```
-
-#### tsconfig.json
-
-```typescript
-{
-  "compilerOptions": {
-    "target": "ESNext",
-    "lib": ["DOM", "DOM.Iterable", "ESNext"],
-    "skipLibCheck": true,
-    "allowSyntheticDefaultImports": true,
-    "strict": true,
-    "forceConsistentCasingInFileNames": true,
-    "module": "ESNext",
-    "moduleResolution": "Bundler",
-    "resolveJsonModule": true,
-    "isolatedModules": true,
-    "allowImportingTsExtensions": true,
-    "noEmit": true,
-    "jsx": "react-jsx"
-  },
-  "exclude": ["convex"],
-  "include": ["**/src/**/*.tsx", "**/src/**/*.ts", "vite.config.ts"]
-}
-```
-
-#### convex/index.ts
-
-```typescript
-import {
-  query,
-  mutation,
-  internalQuery,
-  internalMutation,
-  internalAction,
-} from './_generated/server';
-import { v } from 'convex/values';
-import OpenAI from 'openai';
-import { internal } from './_generated/api';
-
-/**
- * Create a user with a given name.
- */
-export const createUser = mutation({
-  args: {
-    name: v.string(),
-  },
-  returns: v.id('users'),
-  handler: async (ctx, args) => {
-    return await ctx.db.insert('users', { name: args.name });
-  },
-});
-
-/**
- * Create a channel with a given name.
- */
-export const createChannel = mutation({
-  args: {
-    name: v.string(),
-  },
-  returns: v.id('channels'),
-  handler: async (ctx, args) => {
-    return await ctx.db.insert('channels', { name: args.name });
-  },
-});
-
-/**
- * List the 10 most recent messages from a channel in descending creation order.
- */
-export const listMessages = query({
-  args: {
-    channelId: v.id('channels'),
-  },
-  returns: v.array(
-    v.object({
-      _id: v.id('messages'),
-      _creationTime: v.number(),
-      channelId: v.id('channels'),
-      authorId: v.optional(v.id('users')),
-      content: v.string(),
-    }),
-  ),
-  handler: async (ctx, args) => {
-    const messages = await ctx.db
-      .query('messages')
-      .withIndex('by_channel', (q) => q.eq('channelId', args.channelId))
-      .order('desc')
-      .take(10);
-    return messages;
-  },
-});
-
-/**
- * Send a message to a channel and schedule a response from the AI.
- */
-export const sendMessage = mutation({
-  args: {
-    channelId: v.id('channels'),
-    authorId: v.id('users'),
-    content: v.string(),
-  },
-  returns: v.null(),
-  handler: async (ctx, args) => {
-    const channel = await ctx.db.get(args.channelId);
-    if (!channel) {
-      throw new Error('Channel not found');
-    }
-    const user = await ctx.db.get(args.authorId);
-    if (!user) {
-      throw new Error('User not found');
-    }
-    await ctx.db.insert('messages', {
-      channelId: args.channelId,
-      authorId: args.authorId,
-      content: args.content,
-    });
-    await ctx.scheduler.runAfter(0, internal.index.generateResponse, {
-      channelId: args.channelId,
-    });
-    return null;
-  },
-});
-
-const openai = new OpenAI();
-
-export const generateResponse = internalAction({
-  args: {
-    channelId: v.id('channels'),
-  },
-  returns: v.null(),
-  handler: async (ctx, args) => {
-    const context = await ctx.runQuery(internal.index.loadContext, {
-      channelId: args.channelId,
-    });
-    const response = await openai.chat.completions.create({
-      model: 'gpt-4.1-nano',
-      messages: context,
-    });
-    const content = response.choices[0].message.content;
-    if (!content) {
-      throw new Error('No content in response');
-    }
-    await ctx.runMutation(internal.index.writeAgentResponse, {
-      channelId: args.channelId,
-      content,
-    });
-    return null;
-  },
-});
-
-export const loadContext = internalQuery({
-  args: {
-    channelId: v.id('channels'),
-  },
-  returns: v.array(
-    v.object({
-      role: v.union(v.literal('user'), v.literal('assistant')),
-      content: v.string(),
-    }),
-  ),
-  handler: async (ctx, args) => {
-    const channel = await ctx.db.get(args.channelId);
-    if (!channel) {
-      throw new Error('Channel not found');
-    }
-    const messages = await ctx.db
-      .query('messages')
-      .withIndex('by_channel', (q) => q.eq('channelId', args.channelId))
-      .order('desc')
-      .take(10);
-
-    const result = [];
-    for (const message of messages) {
-      if (message.authorId) {
-        const user = await ctx.db.get(message.authorId);
-        if (!user) {
-          throw new Error('User not found');
-        }
-        result.push({
-          role: 'user' as const,
-          content: `${user.name}: ${message.content}`,
-        });
-      } else {
-        result.push({ role: 'assistant' as const, content: message.content });
-      }
-    }
-    return result;
-  },
-});
-
-export const writeAgentResponse = internalMutation({
-  args: {
-    channelId: v.id('channels'),
-    content: v.string(),
-  },
-  returns: v.null(),
-  handler: async (ctx, args) => {
-    await ctx.db.insert('messages', {
-      channelId: args.channelId,
-      content: args.content,
-    });
-    return null;
-  },
-});
-```
-
-#### convex/schema.ts
-
-```typescript
-import { defineSchema, defineTable } from 'convex/server';
-import { v } from 'convex/values';
-
-export default defineSchema({
-  channels: defineTable({
-    name: v.string(),
-  }),
-
-  users: defineTable({
-    name: v.string(),
-  }),
-
-  messages: defineTable({
-    channelId: v.id('channels'),
-    authorId: v.optional(v.id('users')),
-    content: v.string(),
-  }).index('by_channel', ['channelId']),
-});
-```
-
-**Some more rule:**
-
-**1. Regarding Convex Function Environments:**
-
-```markdown
-### Convex Function Environments and Node.js Dependencies (`"use node";`)
-
-- Convex `queries` and `mutations` execute in a secure V8 isolate environment with access to a limited set of Node.js APIs and only those npm packages that are compatible with this environment.
-- Convex `actions` can optionally run in a full Node.js environment by including the directive `"use node";` as the absolute first line of the file. This is essential when an action needs to:
-  - Utilize npm packages that have deep Node.js system dependencies (e.g., native file system access, certain crypto libraries not available in the V8 isolate, complex image/video processing libraries).
-  - Perform long-running operations or tasks that might exceed the typical V8 isolate limits.
-- **Carefully evaluate if `"use node";` is necessary.** While it provides greater flexibility, it may also have implications for cold start times compared to standard actions. Prefer the standard V8 action environment if your dependencies and logic are compatible.
-- **HTTP Actions (`httpAction`):** These run in the standard Vercel V8 isolate environment and **CANNOT** use the `"use node";` directive. If an `httpAction` needs to execute logic requiring a full Node.js environment, it MUST delegate that specific part of the work by calling a separate, regular `action` (which _can_ be marked with `"use node";`).
-```
-
-**2. Implementing Streaming HTTP Actions in Convex (Generic Pattern):**
-
-```markdown
-### Implementing Streaming HTTP Actions in Convex
-
-- To return a streaming response from a Convex `httpAction` (e.g., for Server-Sent Events, chunked JSON, or text streams):
-  1.  The `httpAction` handler function (`async (ctx, request) => { ... }`) MUST return a standard `Response` object.
-  2.  The `body` of this `Response` object MUST be a `ReadableStream`.
-  3.  Within the `ReadableStream`'s `start(controller)` method:
-      - Iterate over your source of data chunks (e.g., from an internal process, another stream, or a generator function).
-      - For each data chunk, use `controller.enqueue(encoder.encode(chunk))` to send it to the client. An appropriate `TextEncoder` should be used for text-based streams. For binary streams, enqueue `Uint8Array` chunks directly.
-      - Call `controller.close()` when all data has been sent.
-      - Implement robust error handling within the stream's `start` method, calling `controller.error(e)` if an issue occurs during streaming.
-  4.  Set appropriate HTTP headers on the `Response` object, such as `Content-Type` (e.g., `text/event-stream`, `application/octet-stream`, `text/plain; charset=utf-8`) and `Transfer-Encoding: chunked` (though `Transfer-Encoding` is often handled by the environment if a `ReadableStream` body is used).
-- **Important:** Do NOT use `ctx.stream.write()` or `ctx.stream.close()` (which are for regular `action` streaming context) within an `httpAction` handler that returns a `Response` object with a `ReadableStream` body.
-```
-
-**3. Authentication for Convex HTTP Actions (Generic):**
-
-```markdown
-### Authentication in Convex HTTP Actions
-
-- All Convex `httpAction`s that require user authentication MUST validate the session or incoming credentials.
-- **Session-Based (Recommended for User-Facing Endpoints):**
-  - The client application SHOULD fetch the current Convex session token (e.g., `await convex.session?.getToken()`) and send it in the `Authorization: Bearer <TOKEN>` HTTP header.
-  - Inside the `httpAction` handler, use `const identity = await ctx.auth.getUserIdentity();` to verify the session based on the token automatically processed by Convex from the header/cookie.
-  - If `identity` is `null`, the user is unauthenticated. The `httpAction` MUST return an appropriate error `Response` (e.g., status 401 Unauthorized).
-- **API Key Based (For Server-to-Server or Controlled Access):**
-  - If using API keys, the client MUST send the key in a designated header (e.g., `X-API-Key`).
-  - The `httpAction` MUST retrieve this header (e.g., `request.headers.get("X-API-Key")`) and validate it against securely stored API keys (e.g., in Convex environment variables).
-  - Return an appropriate error `Response` (e.g., status 403 Forbidden) if the API key is invalid or missing.
-```
-
-**4. Testing Convex HTTP Actions (Generic Strategy):**
-
-```markdown
-### Testing Convex HTTP Actions
-
-- Direct unit testing of Convex `httpAction` handlers using `convexTest` can be challenging due to their raw `Request`/`Response` object interface and the specifics of their execution context.
-- **Recommended Strategy:**
-  a. **Minimize Logic in Handler:** Keep the `httpAction` handler itself as thin as possible. Its primary responsibilities should be: parsing the `Request`, performing authentication/authorization checks, calling other testable Convex functions (regular `actions`, `mutations`, or `queries`) to perform the core work, and formatting the `Response` (including constructing `ReadableStream` if streaming).
-  b. **Unit Test Core Logic:** Extract all significant business logic, data processing, and interactions with external services into separate, regular Convex `actions`, `mutations`, or `queries`. Write thorough unit tests for these extracted functions using the `convexTest` framework.
-  c. **Manual/Integration Testing for HTTP Endpoint:** For the `httpAction` endpoint itself, perform manual testing using tools like `curl`, Postman, or an HTTP client library from a test script. Verify:
-  _ Correct request handling and parsing.
-  _ Authentication and authorization enforcement.
-  _ Expected response headers and status codes.
-  _ Correctness and format of the response body (including streamed content, if applicable).
-  d. **Document Manual Test Steps:** Include example `curl` commands or Postman collection details in the "Manual Verification Steps" section of the User Story that defines the `httpAction`.
-```
-
-**5. Convex Test Runner & Syntax (Clarification/Reinforcement):**
-
-```markdown
-### Convex Backend Function Testing (General)
-
-- All Convex backend tests (typically files named `*.test.ts` within the `convex/` directory) MUST be written using **Vitest** syntax (e.g., `import { describe, test, expect, vi } from 'vitest';`).
-- Utilize the `convexTest` utility from `convex/testing` (or the `convex-test` package if used directly by the project) to set up the Convex test environment for each test or suite. Example: `const t = convexTest(schema);`.
-- Invoke Convex functions (queries, mutations, actions) within tests using the test environment object: `await t.mutation(api.module.myMutation, args)` or `await t.query(api.module.myQuery, args)`. For internal functions, use the `internal` API object: `await t.mutation(internal.module.myInternalMutation, args)`.
-- The designated script for running these backend tests (e.g., `npx convex test`) MUST pass before code is considered complete.
-- **Mocking Dependencies:** Use `vi.mock()` from Vitest for mocking module dependencies (e.g., external API client libraries, helper modules). Mocks should generally be defined at the top of the test file, before any imports of the modules that use them.
-```
-
-**6. Filename Conventions for Convex (Reinforcement):**
-
-```markdown
-### Filename Conventions (Convex Directory)
-
-- All TypeScript files (`.ts`) located directly within the `convex/` directory (and its subdirectories, such as `convex/lib/`) MUST use **`camelCase`** naming (e.g., `myConvexFunction.ts`, `userProfileMutations.ts`).
-- This convention is critical for Convex's file-based routing and its API generation system (`convex/_generated/api.js`).
-- The project's ESLint configuration (`.eslintrc.js`) includes an override to enforce `camelCase` specifically for files within `convex/`, differing from the general project-wide `kebab-case` rule.
-```