get-convex/agent-skills▌

Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers. \n \n Supports three component shapes: local (single-app), packaged (npm), and hybrid (both), with a decision tree to choose the right fit \n Enforces architectural boundaries: components own their tables and functions, while the app handles authentication, environment access, and client-facing wrappers \n Provides a complete workflow from planning (tables, public API, data flow) through

Battle-tested utilities for Convex backends covering relationships, authentication, filtering, sessions, and data migrations. \n \n Relationship helpers ( getOneFrom , getManyFrom , getManyVia ) simplify loading related data across tables with type safety \n Custom functions provide TypeScript-based data protection and access control as an alternative to row-level security, with automatic auth injection and role-based access patterns \n Additional utilities include filtering for complex logic, s

Convex authentication setup with provider selection, user management, and access control patterns. \n \n Supports multiple auth providers: Convex Auth, Clerk, WorkOS AuthKit, Auth0, and custom JWT, with provider detection from repo signals before setup \n Guides identity mapping to a users table, getCurrentUser helpers, and authorization patterns for ownership, admin, and team access checks \n Includes provider-specific reference files for package installation, environment variables, client wiri

Plan and execute Convex schema migrations safely with zero-downtime data transformations. \n \n Covers safe additive changes (optional fields, new tables, indexes) that require no migration code, and breaking changes (required fields, type changes, renames) that need custom migration functions \n Provides patterns for batch processing, scheduled migrations via cron jobs, and dual-write strategies to maintain app availability during transitions \n Includes complete examples for common scenarios:

Self-contained mini-backends that bundle schema, functions, and data with clear API boundaries. \n \n Components encapsulate features like storage, payments, and notifications as reusable backend modules, reducing monolithic code and improving maintainability \n Sibling components pattern allows multiple components to work together at the same level, with the main app orchestrating calls across them \n Official component library includes authentication, storage, payments, AI, and utility compone

Generate type-safe Convex queries, mutations, and actions with built-in validation, authentication, and error handling. \n \n Supports three function types: queries (read-only, cached), mutations (transactional writes with automatic retries), and actions (external APIs, long-running tasks) \n Enforces argument and return type validation via Convex validators; includes authentication checks and authorization patterns for ownership verification \n Actions requiring Node.js APIs (SDKs, crypto) must

Design and generate Convex database schemas with proper validation, indexes, and relationships. \n \n Provides schema templates and patterns for one-to-many, many-to-many, and hierarchical relationships using ID references instead of nesting \n Includes validator reference for all Convex types ( v.string() , v.id() , v.union() , etc.) and guidance on when to use arrays versus relational structures \n Covers index strategy with single-field and compound index examples for common query patterns \n

Scaffold a new Convex project or integrate Convex into an existing frontend app. \n \n Supports two paths: scaffolding from templates (React + Vite, Next.js, Vue, Svelte, or bare backend) or adding Convex to an existing app with manual provider setup \n Templates include pre-configured frontend frameworks, Tailwind, shadcn/ui, and optional auth (Clerk, Convex Auth, Lucia) \n Requires running npx convex dev as a long-running process to sync backend code and manage deployments; cloud agents can us

Plan and execute Convex schema migrations safely with multi-deploy workflows and data transformation. \n \n Follows a predictable three-step pattern: widen schema, migrate data, narrow schema; handles online migrations where the app continues serving requests during async data updates \n Provides the @convex-dev/migrations component for batched, cursor-based pagination with state tracking, dry-run testing, progress monitoring, and automatic resume from failure \n Covers common patterns including

Set up Convex authentication with the right provider, user management, and access control patterns. \n \n Supports multiple auth providers: Convex Auth, Clerk, WorkOS AuthKit, Auth0, and custom JWT, with provider detection from repo signals \n Guides you through choosing a provider, configuring client and backend wiring, environment variables, and convex/auth.config.ts setup \n Covers authentication checks in protected functions, optional app-level user storage, and authorization patterns for ow

Diagnose and resolve Convex performance issues across reads, writes, subscriptions, and function limits. \n \n Covers four problem classes: hot-path reads and data amplification, OCC write conflicts and contention, subscription cost and reactivity overhead, and function execution or transaction size limits \n Starts with signal gathering from deployment health insights or CLI tools, then routes to the relevant reference guide based on the problem type \n Emphasizes tracing full read and write se