convex-create-component

To scaffold a Convex component, you define its isolated tables, expose an app-facing API, and wire it into the host app using app.use and component wrappers. The workflow generates a component skeleton, validates codegen, and ensures clear boundaries for auth and env handling.

The best way to structure a Convex component for distribution is deciding between Local, Packaged, or Hybrid shapes. This structured workflow scaffolds the component with Convex config, schema, and library modules while enforcing frontmatter-driven entry points and required SKILL.md name and description metadata.

Handling authentication and environment variables across Convex component boundaries requires defining clear boundary rules for auth, env, and ID handling. The component design enforces an app-facing API surface and app wrappers to properly manage cross-boundary data without leaking internal implementation details.

Yes, this workflow supports local app integration for Convex components. The scope includes local app integration alongside optional packaged distribution, allowing you to wire the component into the host app using app.use and component wrappers while maintaining isolated table boundaries.

You should not use isolated Convex components when your backend logic requires tightly coupled shared tables or extensive cross-boundary data dependencies. The component architecture enforces isolated table boundaries and defined API surfaces, which adds overhead for logic that does not benefit from modular separation.