convex-create-component

Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers. Create reusable Convex components with clear boundaries and a small app-facing API. Ask the user, then pick one path: Read exactly one reference file before proceeding. Unless the user explicitly wants an npm package, default to a local component: A minimal local component with a table and two functions, plus the app wiring. Note the reference path shape: a function in convex/components/notifications/lib.ts is called as components.notifications.lib.send from the app. For additional patterns including function handles for callbacks, deriving validators from schema, static configuration with a globals table, and class-based client wrappers, see references/advanced-patterns.md . Try validation in this order: Important: Read exactly one of these after the user confirms the goal: Official docs: Authoring Components - Supports three component shapes: local (single-app), packaged (npm), and hybrid (both), with a decision tree to choose the right fit - Enforces architectural boundaries: components own their tables and functions, while the app handles authentication, environment access, and client-facing wrappers - Provides a complete workflow from planning (tables, public API, data flow) through implementation, wiring with app.use(...) , and validation via npx convex dev -...