convex-create-component

Define your component structure under convex/components/<name>/ with convex.config.ts, schema.ts, and lib.ts files, then wire it into your app via convex.config.ts and app.use(...). This enforces isolated tables and bounded APIs for each component.

App-level wrappers are required for client access and proper auth/env handling. They minimize cross-boundary coupling by providing a fine-grained boundary between your reusable component logic and your application code.

Use reusable patterns for local vs packaged components to support growth across apps. Define isolated tables and bounded APIs for each component, maintaining clear ownership boundaries between app code and reusable modules.

Yes, Convex components can be built as reusable modules within a single app or across multiple apps. The skeleton includes convex.config.ts, schema.ts, and lib.ts, enforcing component boundaries for clean data and logic separation.

A new Convex component requires a convex.config.ts, schema.ts, and lib.ts file. These files form the component skeleton, defining isolated tables, bounded APIs, and clear ownership boundaries.

Avoid packaged Convex components if your feature module cannot be isolated into bounded APIs with clear ownership boundaries. Components require app-level wrappers for client access, so tightly coupled app logic may not benefit from this modular structure.