convex-create-component

Design and implement reusable Convex components with isolated tables and app-facing APIs.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/zuzu59/z-skills --skill convex-create-component-zuzu59
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/zuzu59/z-skills/tree/main/skills/convex-create-component
Command: npx skills add https://github.com/zuzu59/z-skills --skill convex-create-component-zuzu59

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and implement reusable Convex components with isolated tables and app-facing APIs, reducing duplication and improving maintainability for large apps.

Core Features & Use Cases

  • Define component boundaries with per-component schemas and isolated data tables.
  • Provide a clean app-facing API via wrappers to enforce authentication and environment handling.
  • Support local components inside a single app, or packaged components for cross-app reuse, with clear guidance on codegen and testing.

Quick Start

Create a new local Convex component following the recommended layout and run codegen to bootstrap it.

Frequently Asked Questions about convex-create-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create reusable Convex components with isolated tables?

To create reusable Convex components, define per-component schemas with isolated data tables and provide clean app-facing APIs via wrappers. This approach reduces duplication and improves maintainability for large web apps.

What is the best way to structure backend logic for cross-app sharing in Convex?

The best way to share backend logic across apps is packaging it as a reusable Convex component. This isolates data tables and exposes a clean API, ensuring consistent environment handling and authentication across different web apps.

How do I enforce authentication boundaries in a Convex backend component?

You enforce authentication boundaries by providing a clean app-facing API via wrapper functions. These wrappers manage app-auth and environment handling, ensuring proper boundary rules for your reusable Convex components.

Can I extract reusable backend logic from an existing Convex web app?

Yes, you can extract reusable backend logic from an existing Convex web app by defining clear component boundaries. This involves isolating tables and creating app-facing APIs to package the functionality for local or cross-app reuse.

Do I need to run codegen when building a new local Convex component?

Yes, you need to run codegen to bootstrap a new local Convex component. Following the recommended layout and running codegen ensures proper schema validation and boundary rules are established during implementation.

When should I not use isolated Convex components for backend architecture?

You should avoid isolated Convex components when your backend architecture is simple enough that boundary rules and isolated tables add unnecessary complexity, making codegen and wrapper maintenance outweigh maintainability benefits for small web apps.