convex-create-component

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

Updated Apr 3, 2026

Search Tags:#architecture #component #auth #bindings #convex #app-wrappers

Ready to run

npx skills add https://github.com/ScriptKitKat/TamaGoosie --skill convex-create-component-scriptkitkat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/ScriptKitKat/TamaGoosie/tree/main/convex/.agents/skills/convex-create-component
Command: npx skills add https://github.com/ScriptKitKat/TamaGoosie --skill convex-create-component-scriptkitkat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing Convex components that encapsulate backend logic with isolated tables and a well-defined app-facing API simplifies reuse and enforces clean architectural boundaries.

Core Features & Use Cases

Isolated component scope with its own tables and functions to prevent leakage into the host app.
Clear wrapper APIs exposed to the host app for queries, mutations, and actions, plus guidance for auth/env handling.
End-to-end workflow from planning to deployment, including wiring into the host app with app.use and code generation.

Quick Start

Define the component with defineComponent, then wire it into the host app using app.use and run the codegen/dev workflow to generate its server and API stubs.

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?▼

Defining the component with defineComponent creates an isolated scope with its own tables and functions. This encapsulates backend logic and prevents data from leaking into the host application, simplifying reuse.

How does authentication work when extracting backend logic into a Convex component?▼

Extracting backend logic into a Convex component enforces app-level authentication and environment handling. The host app manages auth, passing context across the boundary via boundary-walking calls.

What is the best way to expose a wrapper API from a Convex component to a host app?▼

The best way to expose a wrapper API is to define clear boundaries for queries, mutations, and actions. The host app accesses these through boundary-walking calls via app.use and the component API.

Can I package Convex functionality for reuse across multiple applications?▼

Yes, you can package Convex functionality for reuse by building a component with an isolated scope and a well-defined app-facing API. Multiple host apps can wire into the same logic using app.use.

Do I need to run codegen after wiring a Convex component with app.use?▼

Yes, you need to run the codegen or dev workflow after wiring a Convex component with app.use. This generates the server and API stubs required for the host app to communicate across the component boundary.