convex-create-component

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

3|Updated May 23, 2026
One-click install
npx skills add https://github.com/waynesutton/finder9 --skill convex-create-component-waynesutton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/waynesutton/finder9/tree/main/.codex/skills/convex-create-component
Command: npx skills add https://github.com/waynesutton/finder9 --skill convex-create-component-waynesutton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.

Core Features & Use Cases

  • Encapsulates component-owned tables and unique API surfaces for each component.
  • Provides a standardized workflow for scaffolding convex.config.ts, schema.ts, and server code.
  • Enables app-level wiring via app.use(...) and clear separation between component and host app.

Quick Start

Create a new local Convex component by scaffolding its files, wiring it into the app, and validating with codegen.

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, you scaffold files like schema.ts and convex.config.ts, then wire them into the host app using app.use() to encapsulate component-owned tables and unique API surfaces.

What is the best way to scaffold a Convex backend module for reuse across multiple apps?

Scaffolding a reusable backend module involves generating standardized server code and configuration files, satisfying explicit contracts for auth and env handling, and packaging the component for app wiring across multiple apps.

How does app wiring work for Convex components?

App wiring connects encapsulated components to the host application via the app.use() method, establishing clear separation between component and host app while maintaining explicit contracts for boundary crossings and component exports.

Can I use this approach to build local components within my existing app?

Yes, this framework applies to building local components within an app by scaffolding component-owned tables and defining app-facing APIs, ensuring proper isolation and boundary management within your existing architecture.

What contracts must be satisfied when packaging Convex components?

Packaging Convex components requires satisfying explicit contracts for auth and env handling, boundary crossings, and documentation of component exports to ensure standardized integration and reuse.

Do I need codegen to validate my Convex component setup?

Yes, codegen is used to validate the component setup after scaffolding the files and wiring the component into the app, ensuring the isolated tables and app-facing APIs function correctly.