convex-create-component

Scaffold Convex components with isolated tables and app-facing APIs.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/RestartDK/project-europe --skill convex-create-component-restartdk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/RestartDK/project-europe/tree/main/.agents/skills/convex-create-component
Command: npx skills add https://github.com/RestartDK/project-europe --skill convex-create-component-restartdk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convex developers need a clean boundary to create modular components that own their own data, expose a safe app-facing API, and can be reused across apps without leaking internal state.

Core Features & Use Cases

  • Define a new Convex component with isolated tables and a clear boundary.
  • Expose a minimal app-facing API via wrappers, while keeping auth/env handling in the app.
  • Scaffold the standard component layout (convex.config.ts, schema.ts, lib.ts) and wire into the app using app.use.

Quick Start

Describe the component you want, and I will generate the plan and skeleton (convex.config.ts, schema.ts, and lib.ts) and show how to wire it into your app.

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

To create a modular Convex component, you define it using defineComponent with isolated tables and a clear app-facing API. This generates a standard skeleton including convex.config.ts, schema.ts, and lib.ts to ensure proper boundary isolation.

What is the best way to extract reusable backend logic in Convex?

Extracting reusable backend logic in Convex involves packaging it into a component using defineComponent. This enforces a clean boundary with its own schema and tables, preventing internal state leakage while exposing a safe app-facing API.

How does app.use work when integrating Convex components?

The app.use function wires a Convex component into your application. App-side wrappers handle auth and environment variables, while the component exposes its API through ComponentApi, allowing cross-boundary queries and mutations via ctx.runQuery or ctx.runMutation.

Do I need convex.config.ts and schema.ts to build a Convex component?

Yes, convex.config.ts and schema.ts are required files for the standard Convex component skeleton. Alongside lib.ts, they define the component configuration, isolate data tables, and establish the boundary needed for safe reuse across apps.

Can I keep auth and environment handling in the app when using Convex components?

Yes, you keep auth and environment handling in the app using app-side wrappers. The Convex component itself exposes a minimal app-facing API, ensuring internal state remains isolated while the app securely manages authentication context.