convex-create-component

Create reusable Convex components with isolated tables and app-facing wrappers.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/tacticus-tools/tp2-reset --skill convex-create-component-tacticus-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/tacticus-tools/tp2-reset/tree/main/.agents/skills/convex-create-component
Command: npx skills add https://github.com/tacticus-tools/tp2-reset --skill convex-create-component-tacticus-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs and builds Convex components with isolated tables, clear boundaries, and app-facing wrappers. Use this skill when creating a new Convex component, extracting reusable backend logic into a component, building a third-party integration that owns its own tables, packaging Convex functionality for reuse, or when the user mentions defineComponent, app.use, ComponentApi, ctx.runQuery/runMutation across component boundaries, or wants to separate concerns into isolated Convex modules.

Core Features & Use Cases

  • Create a local, self-contained Convex component with its own schema, server logic, and wrappers.
  • Extract reusable backend logic into a component for reuse across apps.
  • Package Convex functionality for distribution across teams or multiple apps.

Quick Start

Define the component with defineComponent, initialize its convex.config.ts, and wire it into the app with app.use(...).

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 a reusable Convex component with isolated tables?

A Convex component is a self-contained module with its own schema, server logic, and app-facing wrappers. It allows you to separate concerns into isolated modules, owning its own tables and enforcing explicit app-side auth and environment wiring for predictable integration.

When should I extract backend logic into a Convex component?

Use a Convex component when creating a new component, extracting reusable backend logic, building third-party integrations that own their own tables, or packaging functionality for distribution across teams and multiple apps.

How do I wire auth and environment variables into a Convex component?

Wire auth and environment variables into a Convex component by defining explicit app-side auth and env wiring. The skill enforces component boundary rules to ensure predictable and testable integration between the isolated component and the main application.

Can I run queries and mutations across Convex component boundaries?

Yes, you can execute queries and mutations across Convex component boundaries using ComponentApi and ctx.runQuery or ctx.runMutation. This allows the main application to interact with the isolated component's server logic safely through app-facing wrappers.

What boilerplate files are required for a Convex component?

A standard Convex component requires convex.config.ts for configuration, schema.ts for defining isolated tables, and lib.ts for reusable backend logic. These files ensure predictable, testable integration and clear component boundaries.