home / skills / cloudai-x / claude-workflow-v2 / convex-backend

convex-backend skill

/skills/convex-backend

This skill helps you write Convex backend code by applying comprehensive guidelines for functions, schemas, queries, mutations, actions, and storage.

npx playbooks add skill cloudai-x/claude-workflow-v2 --skill convex-backend

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.0 KB
---
name: convex-backend
description: Convex backend development guidelines. Use when writing Convex functions, schemas, queries, mutations, actions, or any backend code in a Convex project. Triggers on tasks involving Convex database operations, real-time subscriptions, file storage, or serverless functions.
---

# Convex Backend Guidelines

Comprehensive guide for building Convex backends with TypeScript. Covers function syntax, validators, schemas, queries, mutations, actions, scheduling, and file storage.

## When to Apply

Reference these guidelines when:

- Writing new Convex functions (queries, mutations, actions)
- Defining database schemas and validators
- Implementing real-time data fetching
- Setting up cron jobs or scheduled functions
- Working with file storage
- Designing API structure

## Rule Categories

| Category          | Impact   | Description                                   |
| ----------------- | -------- | --------------------------------------------- |
| Function Syntax   | CRITICAL | New function syntax with args/returns/handler |
| Validators        | CRITICAL | Type-safe argument and return validation      |
| Schema Design     | HIGH     | Table definitions, indexes, system fields     |
| Query Patterns    | HIGH     | Efficient data fetching with indexes          |
| Mutation Patterns | MEDIUM   | Database writes, patch vs replace             |
| Action Patterns   | MEDIUM   | External API calls, Node.js runtime           |
| Scheduling        | MEDIUM   | Crons and delayed function execution          |
| File Storage      | LOW      | Blob storage and metadata                     |

## Quick Reference

### Function Registration

```typescript
// Public functions (exposed to clients)
import { query, mutation, action } from "./_generated/server";

// Internal functions (only callable from other Convex functions)
import {
  internalQuery,
  internalMutation,
  internalAction,
} from "./_generated/server";
```

### Function Syntax (Always Use This)

```typescript
export const myFunction = query({
  args: { name: v.string() },
  returns: v.string(),
  handler: async (ctx, args) => {
    return "Hello " + args.name;
  },
});
```

### Common Validators

| Type     | Validator                         | Example       |
| -------- | --------------------------------- | ------------- |
| String   | `v.string()`                      | `"hello"`     |
| Number   | `v.number()`                      | `3.14`        |
| Boolean  | `v.boolean()`                     | `true`        |
| ID       | `v.id("tableName")`               | `doc._id`     |
| Array    | `v.array(v.string())`             | `["a", "b"]`  |
| Object   | `v.object({...})`                 | `{name: "x"}` |
| Optional | `v.optional(v.string())`          | `undefined`   |
| Union    | `v.union(v.string(), v.number())` | `"x"` or `1`  |
| Literal  | `v.literal("status")`             | `"status"`    |
| Null     | `v.null()`                        | `null`        |

### Function References

```typescript
// Public functions
import { api } from "./_generated/api";
api.example.myQuery; // convex/example.ts → myQuery

// Internal functions
import { internal } from "./_generated/api";
internal.example.myInternalMutation;
```

### Query with Index

```typescript
// Schema
messages: defineTable({...}).index("by_channel", ["channelId"])

// Query
await ctx.db
  .query("messages")
  .withIndex("by_channel", (q) => q.eq("channelId", channelId))
  .order("desc")
  .take(10);
```

### Key Rules

1. **Always include `args` and `returns` validators** on all functions
2. **Use `v.null()` for void returns** - never omit return validator
3. **Use `withIndex()` not `filter()`** - define indexes in schema
4. **Use `internalQuery/Mutation/Action`** for private functions
5. **Actions cannot access `ctx.db`** - use runQuery/runMutation instead
6. **Include type annotations** when calling functions in same file

## Full Compiled Document

For the complete guide with all rules and detailed code examples, see: `AGENTS.md`

Overview

This skill codifies Convex backend development guidelines for writing functions, schemas, queries, mutations, actions, scheduling, and file storage. It applies when authoring server-side code in a Convex project and enforces type-safe validators, index-driven queries, and standardized function syntax. Use it to ensure consistent, efficient, and secure backend patterns across projects.

How this skill works

The skill inspects tasks that involve Convex database operations, real-time subscriptions, file blobs, or serverless functions and suggests concrete implementations aligned with best practices. It checks for required validators on function arguments and returns, recommends index usage for queries, and directs use of internal vs public function registration. It also provides patterns for actions, cron scheduling, and file storage usage so implementations remain predictable and type-safe.

When to use it

  • Creating new Convex functions (query, mutation, action) or updating existing ones
  • Designing or changing database schemas, indexes, and validators
  • Implementing real-time subscriptions and efficient data fetching
  • Adding scheduled jobs, cron-like tasks, or delayed execution
  • Working with file storage, blob metadata, or external API calls from actions

Best practices

  • Always declare args and returns validators for every function; use v.null() for void returns
  • Prefer withIndex() queries and define indexes in schema instead of client-side filters
  • Use internalQuery/internalMutation/internalAction for private functions and api.* for public ones
  • Keep actions free of direct ctx.db access; call runQuery/runMutation when interacting with the DB
  • Annotate types when invoking functions in the same file to preserve type safety and clarity

Example use cases

  • Implementing a paginated message feed using a table index and withIndex() for efficient queries
  • Creating a scheduled cleanup action that runs via cron and calls internal mutations to remove stale records
  • Writing a mutation with v.object() and v.id() validators to enforce correct input shapes on writes
  • Building an action that stores files in blob storage and records metadata in a Convex table
  • Refactoring public/private functions to use api.* for client access and internal.* for backend-only calls

FAQ

What validator should I use for a function that returns nothing?

Use v.null() as the returns validator; never omit the return validator.

How should I query by a frequently filtered field?

Define an index on that field in the schema and use withIndex() in queries instead of filter().