convex-best-practices

Build production-ready Convex applications by following established patterns for function organization, query optimization, validation, TypeScript usage, and error handling. All patterns in this skill comply with @convex-dev/eslint-plugin . Install it for build-time validation: The plugin enforces four rules: Docs: Before implementing, do not assume; fetch the latest documentation: Organize your Convex functions by domain: Always define validators for arguments AND return types: Use indexes instead of filters for efficient queries: Use ConvexError for user-facing errors: Convex uses OCC. Follow these patterns to minimize conflicts: - Primary: - Error Handling: - Write Conflicts: - For broader context: - Convex manages the hard parts - Let Convex handle caching, real-time sync, and consistency - Functions are the API - Design your functions as your application's interface - Schema is truth - Define your data model explicitly in schema.ts - TypeScript everywhere - Leverage end-to-end type safety - Queries are reactive - Think in terms of subscriptions, not requests - Never run npx convex deploy unless explicitly instructed - Never run any git commands unless explicitly instructed - Always define return validators for functions - Use indexes for all queries that filter data - Make mutations idempotent to handle retries gracefully - Use ConvexError for user-facing error messages -...