convex-schema-validators
Guide for Convex schema design, validators, and TypeScript types. Use when defining database schemas, creating validators for function arguments/returns, working with document types, or ensuring type safety. Activates for schema.ts creation, validator usage, Id/Doc type handling, or TypeScript integration tasks.
What this skill does
# Convex Schema & Validators Guide
## Overview
Convex uses a schema-first approach with built-in validators for type safety. This skill covers schema design, validator patterns, TypeScript type integration, and best practices for type-safe Convex development.
## TypeScript: NEVER Use `any` Type
**CRITICAL RULE:** This codebase has `@typescript-eslint/no-explicit-any` enabled. Using `any` will cause build failures.
**❌ WRONG:**
```typescript
const data: any = await ctx.db.get(id);
function process(items: any[]) { ... }
```
**✅ CORRECT:**
```typescript
const data: Doc<"users"> | null = await ctx.db.get(id);
function process(items: Doc<"items">[]) { ... }
```
## When to Use This Skill
Use this skill when:
- Creating or modifying `convex/schema.ts`
- Defining validators for function arguments and returns
- Working with document IDs and types
- Setting up indexes for efficient queries
- Handling optional fields and unions
- Integrating Convex types with TypeScript
## Schema Definition
### Basic Schema Structure
```typescript
// convex/schema.ts
import { defineSchema, defineTable } from "convex/server";
import { v } from "convex/values";
export default defineSchema({
users: defineTable({
name: v.string(),
email: v.string(),
avatarUrl: v.optional(v.string()),
role: v.union(v.literal("admin"), v.literal("user")),
createdAt: v.number(),
})
.index("by_email", ["email"])
.index("by_role", ["role"]),
messages: defineTable({
authorId: v.id("users"),
channelId: v.id("channels"),
content: v.string(),
isDeleted: v.boolean(),
})
.index("by_channel", ["channelId"])
.index("by_author", ["authorId"])
.index("by_channel_author", ["channelId", "authorId"]),
channels: defineTable({
name: v.string(),
members: v.array(v.id("users")),
isPrivate: v.boolean(),
}),
});
```
### Table Definition Patterns
```typescript
// defineTable takes a validator object
defineTable({
field1: v.string(),
field2: v.number(),
});
// Chain indexes after defineTable
defineTable({
userId: v.id("users"),
status: v.string(),
})
.index("by_user", ["userId"])
.index("by_status", ["status"])
.index("by_user_status", ["userId", "status"]);
// Search indexes for full-text search
defineTable({
title: v.string(),
body: v.string(),
}).searchIndex("search_body", {
searchField: "body",
filterFields: ["title"],
});
```
## Validator Reference
### Primitive Validators
```typescript
import { v } from "convex/values";
v.string(); // string
v.number(); // number (float64)
v.boolean(); // boolean
v.null(); // null literal
v.int64(); // 64-bit integer (NOT v.bigint() - deprecated!)
v.bytes(); // ArrayBuffer
```
### Complex Validators
```typescript
// Document IDs
v.id("tableName"); // Id<"tableName">
// Arrays
v.array(v.string()); // string[]
v.array(v.id("users")); // Id<"users">[]
v.array(v.object({ x: v.number() })); // { x: number }[]
// Objects
v.object({
name: v.string(),
age: v.number(),
email: v.optional(v.string()),
});
// Records (string keys, typed values)
v.record(v.string(), v.number()); // Record<string, number>
v.record(v.id("users"), v.string()); // Record<Id<"users">, string>
// Unions (OR types)
v.union(v.string(), v.null()); // string | null
v.union(v.literal("a"), v.literal("b")); // "a" | "b"
// Optionals (field may be missing)
v.optional(v.string()); // string | undefined
// Literals (exact values)
v.literal("active"); // "active" literal type
v.literal(42); // 42 literal type
v.literal(true); // true literal type
// Any (escape hatch - avoid if possible)
v.any(); // any (use sparingly!)
```
### Common Validator Patterns
```typescript
// Nullable field (can be null)
status: v.union(v.string(), v.null());
// Optional field (may not exist)
nickname: v.optional(v.string());
// Optional AND nullable
deletedAt: v.optional(v.union(v.number(), v.null()));
// Enum-like unions
role: v.union(v.literal("admin"), v.literal("moderator"), v.literal("user"));
// Nested objects
settings: v.object({
theme: v.union(v.literal("light"), v.literal("dark")),
notifications: v.object({
email: v.boolean(),
push: v.boolean(),
}),
});
// Array of objects
members: v.array(
v.object({
userId: v.id("users"),
role: v.string(),
joinedAt: v.number(),
})
);
```
## Function Validators
### CRITICAL: Every Function MUST Have `returns` Validator
```typescript
// ❌ WRONG: Missing returns
export const foo = mutation({
args: {},
handler: async (ctx) => {
// implicitly returns undefined
},
});
// ✅ CORRECT: Explicit v.null()
export const foo = mutation({
args: {},
returns: v.null(),
handler: async (ctx) => {
return null;
},
});
```
### Query with Validators
```typescript
import { query } from "./_generated/server";
import { v } from "convex/values";
export const getUser = query({
args: {
userId: v.id("users"),
},
returns: v.union(
v.object({
_id: v.id("users"),
_creationTime: v.number(),
name: v.string(),
email: v.string(),
role: v.string(),
}),
v.null()
),
handler: async (ctx, args) => {
return await ctx.db.get(args.userId);
},
});
```
### Mutation with Validators
```typescript
import { mutation } from "./_generated/server";
import { v } from "convex/values";
export const createUser = mutation({
args: {
name: v.string(),
email: v.string(),
role: v.optional(v.union(v.literal("admin"), v.literal("user"))),
},
returns: v.id("users"),
handler: async (ctx, args) => {
return await ctx.db.insert("users", {
name: args.name,
email: args.email,
role: args.role ?? "user",
createdAt: Date.now(),
});
},
});
```
### Action with Validators
```typescript
import { action } from "./_generated/server";
import { v } from "convex/values";
export const processImage = action({
args: {
imageUrl: v.string(),
options: v.object({
width: v.number(),
height: v.number(),
format: v.union(v.literal("png"), v.literal("jpeg")),
}),
},
returns: v.object({
processedUrl: v.string(),
size: v.number(),
}),
handler: async (ctx, args) => {
// Process image...
return {
processedUrl: "https://...",
size: 1024,
};
},
});
```
## TypeScript Types
### Importing Types
```typescript
import { Doc, Id } from "./_generated/dataModel";
// Document type for a table
type User = Doc<"users">;
// {
// _id: Id<"users">;
// _creationTime: number;
// name: string;
// email: string;
// ...
// }
// ID type for a table
type UserId = Id<"users">;
```
### Using Types in Code
```typescript
import { Doc, Id } from "./_generated/dataModel";
// Function parameter types
async function getUserName(
ctx: QueryCtx,
userId: Id<"users">
): Promise<string | null> {
const user = await ctx.db.get(userId);
return user?.name ?? null;
}
// Variable types
const users: Doc<"users">[] = await ctx.db.query("users").collect();
// Record with Id keys
const userMap: Record<Id<"users">, string> = {};
for (const user of users) {
userMap[user._id] = user.name;
}
```
### Context Types
```typescript
import { QueryCtx, MutationCtx, ActionCtx } from "./_generated/server";
// Query context - read-only
async function readUser(ctx: QueryCtx, id: Id<"users">) {
return await ctx.db.get(id);
}
// Mutation context - read and write
async function createUser(ctx: MutationCtx, name: string) {
return await ctx.db.insert("users", { name, createdAt: Date.now() });
}
// Action context - no db, uses runQuery/runMutation
async function processUser(ctx: ActionCtx, id: Id<"users">) {
const user = await ctx.runQuery(internal.users.getById, { id });
// ...
}
```
## Index Design
### Index Naming Convention
Include all fields in the index name: `by_field1_and_field2_and_field3`
```typescript
// Schema
export default defineSchema({
messages: defineTable({
channelId: v.id("channels"),
authorId: v.idRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.